• Superb product with a lot of growth potential and a well-thought-out company mission/vision • Competitive pay and great benefits • Healthy, people-oriented culture • A lot of opportunities for personal growth • Leadership cares about diversity • Good support for remote engineers
• Keeping a good work/life balance can be difficult. • Processes and organizational structure tend to change very fast. • Missing alignment on technical strategy between pillars leads to suboptimal decisions.
Standard questions that are available online, finding bugs, making HTTP calls, and handling the response. You need to prepare those settings beforehand so you don't lose time, and should be able to check out code from their repo.
A recruiter reached out on LinkedIn. I scheduled a 1-hour technical screen on Zoom. This consisted of: * 45 minutes for a coding exercise with a Software Engineer * 15 minutes to ask them questions about the company I received a rejection email a
You only get standard LeetCode-type questions for a round or two. The remaining 2-3 rounds are system design and debugging. The latter can be very overwhelming since the interviewer will remain silent for the most part. There will likely be logical e
Standard questions that are available online, finding bugs, making HTTP calls, and handling the response. You need to prepare those settings beforehand so you don't lose time, and should be able to check out code from their repo.
A recruiter reached out on LinkedIn. I scheduled a 1-hour technical screen on Zoom. This consisted of: * 45 minutes for a coding exercise with a Software Engineer * 15 minutes to ask them questions about the company I received a rejection email a
You only get standard LeetCode-type questions for a round or two. The remaining 2-3 rounds are system design and debugging. The latter can be very overwhelming since the interviewer will remain silent for the most part. There will likely be logical e