The product can do a lot, there's a lot of money in the space, and the company has been growing quickly.
Leadership seems open to feedback.
Managers seem interested in the personal and career growth of their reports.
There's a strong focus on work/life balance.
There are many opportunities to have an impact and solve interesting technical problems.
Years of the founders and early engineers shipping prototype-quality code have led to high technical debt and a brittle codebase which few people understand. There are few limits on customers' usage of the product, which is used as a selling point but also causes endless reliability problems.
Because engineers are busy fighting fires and paying down technical debt, they have trouble keeping up with new features which were promised in order to close deals. Rather than find ways to help their engineering teams scale better, the founders have recently announced that they'll return to writing one-off features as a new separate team, and transfer those features to other teams to maintain.
Keep up the positive and transparent culture. Consider focusing less on short-term growth at all costs, and more on stabilizing the product and building a better foundation for future growth. Writing the code yourself might not be a sustainable solution to the current challenges.
Overall, I was unimpressed with their people. They seem to pride themselves on their interview experience, but the two people I spoke with (a recruiter and a manager) did not seem to follow this goal. The manager was condescending and dismissed me
I had a call with a member of their recruiting team first. They asked me a ton of questions, starting from why I got into computer science. After that, I got a phone interview with an engineer. Then they told me I got positive feedback from the codi
Typical 3-step process of recruiter interview, tech exercise, then a virtual onsite. The recruiter interview is just making sure you're a good fit for the company and position. The tech exercise was a 1 hour LeetCode test with a difficulty in the low
Overall, I was unimpressed with their people. They seem to pride themselves on their interview experience, but the two people I spoke with (a recruiter and a manager) did not seem to follow this goal. The manager was condescending and dismissed me
I had a call with a member of their recruiting team first. They asked me a ton of questions, starting from why I got into computer science. After that, I got a phone interview with an engineer. Then they told me I got positive feedback from the codi
Typical 3-step process of recruiter interview, tech exercise, then a virtual onsite. The recruiter interview is just making sure you're a good fit for the company and position. The tech exercise was a 1 hour LeetCode test with a difficulty in the low