Free food.
Possibility to get rich when IPO (if you don’t mind waiting).
People are nice. Besides one or two people I had to deal with, the rest of the community was pleasant to work with.
Since it’s a startup in an interesting domain, many things are new to explore and solve.
Low engineering level. Many underqualified people were found for their level, and a few were overqualified for what their level was.
Some interviewers are not able to pass their own questions (from what I saw as a shadow), which impacts the hiring bar. Either they pick the easiest questions, or they can’t judge the candidate’s real level.
Teams have no clear domain ownership. Different teams could be working in a component which should be owned by your team.
No 401k.
Development environments fail too often, resulting in people spending a lot of time troubleshooting (0-2 days) because either no one knows the issue/solution, or restarting the environment takes forever.
Suggest to improve tech interview questions, hiring bar, and make sure interviewers can solve their questions.
Define clear boundaries among different domain teams.
Spend some time to improve the development environment; all engineers will appreciate it.
LeetCode questions typical for an SWE1 interview level. Study from NeetCode to help. Questions are on a case-by-case basis. Hope this helps you in your interview process. These are very reasonable questions.
I went through the standard "apply through LinkedIn" route and had a phone call with the recruiter. Ten minutes after a seemingly good interview (I solved the problem and believe I did a good job), I received a rejection letter. I emailed the recruit
The interview process began with a chat with HR, followed by a first-round interview that included a coding challenge. The final round was a virtual onsite composed of four interviews. * The first interview was a deep dive into one of my projects,
LeetCode questions typical for an SWE1 interview level. Study from NeetCode to help. Questions are on a case-by-case basis. Hope this helps you in your interview process. These are very reasonable questions.
I went through the standard "apply through LinkedIn" route and had a phone call with the recruiter. Ten minutes after a seemingly good interview (I solved the problem and believe I did a good job), I received a rejection letter. I emailed the recruit
The interview process began with a chat with HR, followed by a first-round interview that included a coding challenge. The final round was a virtual onsite composed of four interviews. * The first interview was a deep dive into one of my projects,