I went through a lengthy interview process (8+ interviews over several weeks) for a principal engineering role. This included a case study presentation that required a lot of advanced preparation, meeting with the CTO, and your standard coding and system design interviews, among other things.
After finishing this process, I was told I’d hear back within a week. A week later, the recruiter told me they hadn’t made a decision and we’d touch base in a week. This happened on a loop for a month, every week being told they hadn’t made a decision.
Then finally I was told they realized they weren’t actually going to hire for this role at all, so the job I was interviewing for didn’t even exist. I was told I could put my name in the running for some less senior engineering positions that would also pay significantly less, though. Needless to say I removed myself from consideration.
Clearly a chaotic organization that doesn’t know what it wants and doesn’t respect candidates’ time. Save yourself the headache and avoid interviewing here. As much as I want to believe in the mission, I’m confident I dodged a bullet.
Walk us through a past project that you led.
The following metrics were computed from 1 interview experience for the Cityblock Health Principal Software Engineer role in New York, New York.
Cityblock Health's interview process for their Principal Software Engineer roles in New York, New York is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Cityblock Health's Principal Software Engineer interview process in New York, New York.