Real, anonymous reports from people who interviewed for Software Engineer at Appfolio, newest first and distilled into what to expect across the loop.
After a recruiter call, my process moved quickly into back-to-back technical interviews. Over roughly three weeks, I did two technical rounds plus a final panel-style interview with leadership/hiring-manager involvement. The technical portion leaned heavily on live coding and coding problem solving, and it was also where system thinking showed up—one round had system design expectations alongside the coding. In total, I ended up talking with several interviewers, each of them professional and engaged, and the interviews felt structured in a way that matched what the role actually needed.
My interview journey started with a short call and then moved into a small loop. First I had an initial conversation, then I met with a senior engineer for the technical portion. After that, I had two back-to-back sessions with hiring managers—one technical and one behavioral—followed by an HR offer discussion. Even with multiple people involved, the whole thing felt pretty chill and manageable.
The interview process typically starts with a recruiter call followed by a series of technical interviews, often including both coding and system design components, and sometimes a behavioral round. The overall timeline is generally around two to three weeks, with some candidates experiencing delays due to scheduling conflicts.
Candidates can expect a mix of live coding exercises and problem-solving questions, often modeled after LeetCode-style problems, with an emphasis on clear communication and reasoning during the coding process. Interviewers are generally supportive, focusing on how candidates approach problems rather than just the final output.
Some interviews include system design questions alongside coding challenges, where candidates are expected to demonstrate their understanding of system architecture and object-oriented principles. The questions often require candidates to think critically and articulate their design choices.
Behavioral interviews focus on collaboration, communication, and cultural fit within the team, allowing candidates to discuss their experiences and how they work with others. These rounds are generally conversational and aim to gauge interpersonal skills rather than just technical ability.
While initial stages of the interview process are often well-communicated, some candidates report a breakdown in communication regarding follow-up and feedback after technical rounds, leading to feelings of uncertainty. Clear and timely communication is valued, but can vary significantly across experiences.
Candidates generally describe the interview experience as structured and supportive, with a focus on evaluating thought processes rather than just technical prowess. However, some report feeling pressure during timed coding exercises, and the difficulty level can vary based on the specific interviewers and their expectations.