The process felt disorganized and slow. I applied for a more frontend role and was redirected to a systems role. After the initial phone screen there were 8 days of silence, then a manager call, then another week before a technical screen that was 45 minutes. I’m sure the full loop would have stretched into a month or two.
What worried me more was the way the team talked about their challenges. They openly described ongoing issues with impersonation and extremist content on the platform, but didn’t sound like they had a clear strategy or ownership across engineering. It made the technical work feel reactive and firefighting-heavy rather than planned.
Overall the people were polite, but the interview process and product signals didn’t give me confidence in the org’s readiness or direction.
I ran out of time, but the technical screen itself was a small grid-matching puzzle: given a few rows of characters (x, s, p), match up the s characters with the closest p characters while avoiding conflicts. The problem was fine on its own, but in context it reinforced the sense that the process was more about puzzles than about the real problems they said they were facing.
The following metrics were computed from 7 interview experiences for the Substack Software Engineer role in United States.
Substack's interview process for their Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Substack's Software Engineer interview process in United States.