I applied online. The process took 1 day.
I applied for a Backend Engineer role and received a rejection less than 12 hours after submitting my application. The disappointing part was not the rejection itself, but how little confidence the process gave me that the application had received meaningful consideration. The role appeared closely aligned with my background in backend engineering, PostgreSQL, cloud infrastructure, DevOps, and data-heavy systems, yet the rejection came extremely quickly and without any useful feedback. The company presents itself as one that values transparency, autonomy, engineering quality, and a thoughtful hiring process. From a candidate perspective, my experience did not really reflect those values. When an applicant spends time tailoring an application to a role, an almost immediate generic rejection can make the process feel transactional, particularly when there is no indication of where the mismatch was. I fully understand that companies receive large numbers of applications and cannot provide detailed feedback to everyone. However, for a company that places such a strong emphasis on transparency in its public culture, I expected a little more from the recruitment experience. Overall, the experience left me significantly less interested in applying again.
The following metrics were computed from 1 interview experience for the PostHog Backend Engineer role.
PostHog's interview process for their Backend Engineer roles is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for PostHog's Backend Engineer interview process.