Ho presentato la mia candidatura tramite un'altra fonte. La procedura ha richiesto 2 settimane. Ho sostenuto un colloquio presso AppFolio (Santa Barbara, CA) nel mese di giu 2018
Colloquio
They called me in for two interviews which went well - one whiteboarding and one coding one on the computer. Looks like first interviewer was looking for me to code in certain way (for vs while loop).
I thought I did great, but the recruiter never got back to me for more than a week. After I followed up, I heard that they moved on with other candidates.
Domande di colloquio [2]
Domanda 1
Write an algorithm to find out trailing zeros in fib(n)?
The process consisted of a recruiter phone screen, followed by two technical interviews and a final panel interview with the hiring manager and team members. The entire process took about three weeks. Communication was clear throughout, and the team was responsive and professional.
Domande di colloquio [1]
Domanda 1
Tell me about a time you had to deal with a difficult stakeholder and how you handled it.
Ho presentato la mia candidatura tramite un selezionatore. La procedura ha richiesto una settimana. Ho sostenuto un colloquio presso AppFolio (Denver, CO) nel mese di ott 2025
Colloquio
I recently completed a 75-minute screening that included:
2–3 behavioral questions
5 rapid-fire system-design questions
a 45-minute coding round
and a short window for me to ask questions
The technical questions were fairly straightforward, and I felt confident in my responses — clear, structured, and technically sound.
While I haven’t received feedback yet, my best guess is that my rejection may have stemmed from the Q&A portion. I asked a few candid questions about the product vision, team culture, and growth opportunities — the kind of questions I believe any thoughtful engineer should ask when evaluating a team. Some of these seemed to catch the interviewers off guard, which might have left a mixed impression.
Still, the engineers were pleasant, and the overall experience was positive. The only downside is the lack of feedback — something that always makes it difficult to learn what truly went wrong. Sometimes, teams might already have an internal candidate or be interviewing for formality’s sake — though that may not be the case here, the absence of closure leaves room for guesswork.
Domande di colloquio [3]
Domanda 1
Behavioral
What is a complex project you worked on?
What is your team composition and what is your role?
Questions:
1. A few hot properties are fetched 10k times/sec from the database — what will you do to withstand load?
2. A report runs complex SQL queries and is straining the production database.
3. How do you provide secure communication between two messaging clients?
4. Your app server is throttling on CPU and memory — what will you do?
Ho presentato la mia candidatura online. La procedura ha richiesto 3 settimane. Ho sostenuto un colloquio presso AppFolio (Santa Barbara, CA) nel mese di ott 2025
Colloquio
The interview process has 5 steps. The first step of the interview process is with the recruiter. If this goes well you will have to schedule a technical assessment with engineers in the company. I was only able to get to the technical interview phase of which I thought went decently well. The interview was will ask you a series of systems interview questions and then you have to solve up a coding problem. I did solve the coding problem and the interviewer close the call. I waited over a week to hear back from my results and j never received a follow up from the recruiter. I reached out via email to follow up with the recruiters and still no response. I then decide to call the recruiter and it seems like she forgot about me. For other developers who are applying for this company, be careful as it seems like they like to ghost people during the process. I wouldn’t waste my time.
Domande di colloquio [1]
Domanda 1
Basic system design questions were asked even though it was for a mobile role. Coding questions consisted of parsing out strings to simulate command line instructions.