
Calendly Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 12 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Calendly.
Software Engineer
The interview process wasn't too long and the team was nice. There were a few minor issues, but overall it went quite well. The coding part of the interview was very direct and related to the actual code; no tricky puzzles or riddles.
- When creating code, what factors do you take into account?
- What's your approach to prioritizing tasks and features?
Senior Software Engineer
I applied on a Sunday night and Monday morning I got an email from a recruiter via Calendly to set up a phone screen. The recruiter was nice and knew their stuff, they were clear about the job and what they were looking for. After that, I had a brief phone screen with the Director of Engineering. He asked some good questions and told me a lot about the team and the position. Then, they asked me to do a small project and simultaneously set up an onsite interview. I got an email with a full schedule for the onsite, detailing what they might discuss or ask in each part. There were 5 sessions: one for system design, one to go over the project and add to it, a pair coding session fixing a real Calendly bug, a culture chat, and then a final chat with the hiring manager. It's obvious Calendly put a lot of thought and work into their interview process. Everything was super organized and I was really impressed throughout!
- Could you tell me about a recent system you developed, what insights you gained, and what you'd change if you were to do it again?
- Please present the project you developed and then extend it with a minor feature during our conversation.
Software Engineer
My interview with Calendly began with a recruiter I'd spoken to before. After that, I had a phone screen with an HR person, then a few days later, I spoke with a lead developer. They mentioned a coding assessment, and I expressed my hesitation because companies don't usually pay or respect you when you're not an employee. They promised it would be short, and I could even submit an old project as a code sample. The project requirements were really unclear, and I only had an internal API that sent updates about calendar events for a user to work with. I never heard back from Calendly about why I wasn't a good fit. If you're interviewing for a software developer role at Calendly, expect a coding assessment that takes hours, but don't expect any feedback. I learned from this not to do coding assessments or take-home projects for companies I'm interviewing with.
- Build a Rails app using Calendly's developer API.
Calendly Software Engineer Interview Questions
Quoted word for word from Calendly interview reports.
“Build a Rails app using Calendly's developer API.”
Read reports →“Build a React UI that interacts with the Calendly API to customize its features.”
Read reports →“Can you design a notification system that handles messages and subscriptions?”
Read reports →“Given a project, build an app or use their API, or alternatively, use something else you have previously built.”
Read reports →“Could you extend a Rails and React application, integrating the Calendly API?”
Read report →“When creating code, what factors do you take into account?”
Read report →“Can you further extend the take-home assignment?”
Read report →“Tell me about a mistake you've made and what you learned from it.”
Read report →“How would you design the system?”
Read report →Formats, difficulty and experience
Across all 12 Calendly interview reports.