Real, anonymous reports from people who interviewed for Software Engineer at Patreon, newest first and distilled into what to expect across the loop.
After a recruiter call, I moved into a multi-round technical process that felt pretty structured and usually showed up on a weekly rhythm. The first coding-style stage was a LeetCode-flavored question where I ended up working through something like nested data—more about reasoning through the problem than memorizing tricks. After that, I got pulled into an onsite-style loop with a mix of implementation and frontend-ish work, where the tasks revolved around building UI behavior tied to a search flow.
My process started with a recruiter screen that felt friendly and low-friction. The overall shape was standard: a recruiter call followed by a coding interview that looked like a LeetCode-style problem, then a behavioral-style conversation. I remember being nervous and “freezing” during the initial part of the technical screen, and I didn’t end up progressing all the way through the interview session. Even though I struggled, the interviewer stayed patient and the interaction itself didn’t feel hostile.
The interview process typically begins with a friendly recruiter call to discuss the role and set expectations, followed by a technical screening that often includes a LeetCode-style coding question. Candidates should prepare to articulate their thought process clearly during this initial stage.
Candidates can expect multiple technical interviews focused on coding challenges that may include practical problems and require clear communication of thought processes. Emphasis is placed on correctness and methodical problem-solving rather than just speed.
Later stages of the interview process often include system design discussions where candidates must explain their reasoning and trade-offs in design choices. These rounds assess both technical knowledge and the ability to communicate effectively under pressure.
Behavioral interviews focus on interpersonal skills, team collaboration, and handling management scenarios, often using a structured format like STAR to evaluate responses. Candidates should prepare to discuss their experiences in these areas thoughtfully.
Candidates reported mixed experiences regarding the consistency of the interview process and communication from the company, with some experiencing delays and a lack of feedback post-interview. It's important to be prepared for potential logistical challenges and to follow up for clarity.
While many candidates found the interviews engaging, the overall experience could be impacted by factors like interviewer engagement and the clarity of questions. Candidates should be prepared for a demanding process and may wish to reflect on their performance and communication style after each round.