Remix clone Hacker News

new | show | ask | jobs Github

▲

rickpm 3 days ago

I’m really impressed by the interesting work you’re doing.

Could you share more about the interview process?

I just applied and believe the role is an excellent fit for my experience and my passion for learning new things.

▲

aloof8723 2 days ago | parent | next [-]

They are picky, I haven't heard of my peers who applied landing an interview.

	▲	rickpm a day ago \| parent \| next [-]
		They seem pretty efficient to me. I got the first round of interviews scheduled the same day I applied. I'm used to being on the other side of the table, and in my experience, as long as you have strong relevant experience for what they need and put effort into the application, companies tend to move quite fast. I also only apply to a few companies for positions that I find interesting and where I know I can bring value. My response rate has always been 90%+, even when I don’t know anybody there or have a referral. Meanwhile, most people nowadays apply to anything with 'software' in the title and are surprised when they don’t hear back.
	▲	deaddodo 2 days ago \| parent \| prev [-]
		Yup, same.

▲

jaredsilver 3 days ago | parent | prev [-]

Thanks for the kind words!

Our interview process is as follows:

* 30 min Zoom call with me

* Technical take home assessment (paid, designed to be reasonably close to the job)

* Panel interview with two engineering leaders

* Virtual onsite

Looking forward to reviewing your application!

▲

rickpm a day ago | parent [-]

Awesome. I appreciate the answer.

As far as technical interviews go, are there any leetcode style questions involved, or are they more practical, like the take-home assessment you mentioned?

	▲	jaredsilver a day ago \| parent [-]
		No leetcode. One interview during the onsite is vaguely algorithmic, but the process is designed to feel relatively close to the work you'd do on the job. For example, our web take-home assessment includes tasks like reviewing a colleague's pull request and tracking down a bug in response to a customer support ticket.