First off, I'm kind of surprised by the low ratings here. I realize I say "genuinely" a lot, but I'm not sure how to stress how much I feel what I'm saying. It's a pretty in-depth review, but I want to give prospective people insight into the company. From day one, it's been one of my favorite places to work, and it's shocking that the overall rating is about the same as my previous companies. Anyways, the pros are in order for me:
Compared to the cons at other companies, these feel pretty tame. They're also in order of how I care about them:
I think middle leadership, i.e. directors, are good people, but they seem kind of confused about their role. They should be focused on setting roadmap direction, culture, and strategic investments, but a lot of them are way too in the execution weeds. I don't get a micromanager energy from them; I think many of them are newer to the role and are still operating with the mindset of a previous level of being more tactical over strategic.
We need a bit less sbwh and a bit more bff. They're not completely mutually exclusive, but they are often at odds with each other. We can yap all we want, but we need to have a bff ambassador per effort or area that synthesizes all the input and has the authority to make a decision.
The first round is easy LeetCode intervals, the second is project experience. Onsite is the usual system design suspects. Know REST, specifically FastAPI, for the coding round, even if the job you're interviewing for is completely unrelated. At th
Had a brief system design decision + coding interview through Karat. System design interview was more of what you would decide to use in this situation, and coding interview was similar to design problems in LeetCode.
I received an email from a recruiter at Headway and went through the whole process, which took about 2-3 weeks from initial contact to an offer. The whole process was pretty standard: * Initial screen with a recruiter; basic questions about the r
The first round is easy LeetCode intervals, the second is project experience. Onsite is the usual system design suspects. Know REST, specifically FastAPI, for the coding round, even if the job you're interviewing for is completely unrelated. At th
Had a brief system design decision + coding interview through Karat. System design interview was more of what you would decide to use in this situation, and coding interview was similar to design problems in LeetCode.
I received an email from a recruiter at Headway and went through the whole process, which took about 2-3 weeks from initial contact to an offer. The whole process was pretty standard: * Initial screen with a recruiter; basic questions about the r