Yay! thanks for the feedback, Boris, glad you enjoyed chatting with Bunchee!

That's cool :-)

What is your tech stack now?

Do you already have ideas on how to evolve your tech stack when introducing the Android version in the future?

Current tech stack is:

The iOS-Frontend is UIKit and RxSwift. The backend is pretty lean — TypeScript, Firestore with the beginnings of PostgreSQL (with Prisma!). The recommender piece for the daily tips is Python. We also use cloud functions to run async updates (e.g. for daily updates and migrations).

Otherwise — lots of hosted services in the mix (Brave, Circle/Github, HoneyComb to name a few).

As for the future, we're exploring Flutter and a few other options to provide different experiences.

Wow, you are right - we have a very stupid usability problem/bug! We validate the URI by the "http" part, and not the "www" etc. Thank you very much for writing!

I'm a bit shocked that we didn't notice this until now!

P.S. It's now fixed, we will deploy it with the next release in a few days.

Hi Community!

Exactly one year ago, I posted in HN that we had just released RemoteMore. We have made a lot of progress since then.

Now we are a company with 7 employees and investors! There are 3700+ developers on our marketplace, and about 300+ companies that are hiring remotely.

Find a remote developer job through our website:

https://join.remotemore.com/hackernews

Feedback is more than welcome!

I hope you like what we have built :-)

Definitely www.remotemore.com/candidates

I'm sorry to hear! Could you email me more details to boris.borisov@remotemore.com so we can fix it faster?

If you have a suggestion for alternative ways to evaluate: - English skills - Communication skills - Independent problem-solving skills

Of course, we are against discrimination. Just the opposite, we want a more connected world where people have easy access to job opportunities regardless of where they live.

I am very interested to hear!

All three metrics you mentioned can be evaluated using writing. In fact, writing makes up most of the communication in a remote environment.

I will think in this direction, thank you for putting some more arguments towards that!

My main concern with this direction is whether we should evaluate for language speaking skills. Second concern is cheating. Third concern, it's more difficult to build.

It's actually easier. Cheating can be discouraged via real-time chat sessions, while async communication like emails or essay-style discussions can be scored via an NLP library like spaCy. If a machine can understand and parse the candidate's writing, chances are it's valid English.

That's an awesome idea! Thank you! I'll talk with some users about it to hear their feedback.

Yes, you should target the more mature remote companies. There are even fully remote companies (Zapier, GitLab and so on), so it's definitely possible.

The companies that are very early on their remote capabilities typically avoid hiring remote juniors, and remote higher-level management positions. The reason is that those levels require communication with more stakeholders which means more mature remote practices. Project management type of positions are typically not too difficult to have remote.

That's interesting feedback, thanks for sharing!

With the rest of my team, we do daily stand-up on a video call - just to know each other more, and to understand each other better. Probably we will switch to fewer video calls as the team becomes more mature (e.g. once a week).

If others have feedback on this topic, it would be helpful to read it.

Yep, we like this name for multiple reasons. It is a palindrome. Also, it repeats the same sounds in two words, which typically make the words sound better. It's easy to pronounce, and spell, etc.

But most of all, it shows what we stand for: More Remote work :-)