This will set you up for the rest of your career.
Team leads and managers encourage taking breaks and not working 12 hours a day or weekends.
Communication is non-confrontational, and I have not yet run into "personality issues".
Engineering talent is not only top-notch but also diverse (including people with families and people with decades of experience).
As long as you are fulfilling expectations, you are not pushed to work extra hours and can remain employed indefinitely.
You can optionally sign up for additional responsibilities should you feel ambitious and want to have a broad impact.
There's a culture of appreciation and giving credit.
Your name will typically be mentioned in feature announcements and project updates. Managers and colleagues will typically show appreciation for your work in meetings and online channels.
There's an abundance of Asana projects where you can ask questions, report issues, or post feedback. Anyone can thumbs up or chime in.
It's the opposite of the sweatshop "hustle culture" that's all too common in the startup world.
There are scaling challenges relating to developer tooling, and new best practices and patterns are constantly being discovered.
Legacy code can slow you down if you happen to hit them.
The compensation is well above average, though not as high as FAANG.
Great job creating and maintaining a sustainable culture. I look forward to seeing more of that.
Consider placing more investment in "engineering quality of life" areas like documentation and testing infrastructure.
Recruiter call followed by a technical screen. Then onsite. Onsite was nice and there was a break for lunch too. Overall a pretty smooth process though they did kind of lag in between the screen and onsite.
Gave a simple 90-minute interview with discussion afterwards. The question was easy, and the discussion was smooth. Have a good understanding of your code and be prepared to explain all of your design decisions.
This was a discussion about some algorithm. It was an open-ended question about how I would solve the problem, essentially a proxy for remembering graph algorithms. I didn't pass, primarily because I wasn't familiar with the specific technique for f
Recruiter call followed by a technical screen. Then onsite. Onsite was nice and there was a break for lunch too. Overall a pretty smooth process though they did kind of lag in between the screen and onsite.
Gave a simple 90-minute interview with discussion afterwards. The question was easy, and the discussion was smooth. Have a good understanding of your code and be prepared to explain all of your design decisions.
This was a discussion about some algorithm. It was an open-ended question about how I would solve the problem, essentially a proxy for remembering graph algorithms. I didn't pass, primarily because I wasn't familiar with the specific technique for f