The engineers here are all at the top of their field. They could work anywhere.
Everyone I've worked with has all the magic engineer powers: really smart, good at getting stuff done, and fun to be around.
The company knows it, and so there's not much red tape on the engineering side. It's up to each person not to break the push or launch a feature too fast.
It's refreshing.
Not a small company anymore.
The hiring bar has been very high as long as I've been around. Let's keep it there.
Prior to a coding interview, you are given access to a preparation hub. It contains videos from the author of "Cracking the Coding Interview," which are poorly produced. They can be meandering and are not edited well. They play in low resolution with
The interview process was structured and straightforward. It started with a recruiter screen, followed by a technical round with LeetCode style problems. Later rounds focused on system design, problem solving, and behavioral questions about previous
3 rounds of interview. 2 coding and 1 behavioral. Round 1: 2 Meta-tagged LeetCode questions (high-frequency) (linked-list + tree). Round 2: Interviewee-designed questions (greedy) + Meta-tagged LeetCode (binary search tree LCA).
Prior to a coding interview, you are given access to a preparation hub. It contains videos from the author of "Cracking the Coding Interview," which are poorly produced. They can be meandering and are not edited well. They play in low resolution with
The interview process was structured and straightforward. It started with a recruiter screen, followed by a technical round with LeetCode style problems. Later rounds focused on system design, problem solving, and behavioral questions about previous
3 rounds of interview. 2 coding and 1 behavioral. Round 1: 2 Meta-tagged LeetCode questions (high-frequency) (linked-list + tree). Round 2: Interviewee-designed questions (greedy) + Meta-tagged LeetCode (binary search tree LCA).