The process to interview at Calendly started with a recruiter I had spoken to prior. I had a phone screen with an HR representative first, and then a lead developer a few days later. I was told I was expected to do a coding assessment, and I expressed my wariness to do so. The reason being that there is no obligation from a company to pay or even respect you for your time if you aren't employed by them. They assured me that the assessment was short and that I could even submit an old project simply as a code sample. The requirements for the project were extremely vague, and all I was given to work with was an internal API that emitted updates to calendar events for a given user. I ended up getting absolutely no response from Calendly as to why they didn't feel I was a fit for the company.
If you're going to interview as a software developer for Calendly, expect to have to do a coding assessment that will take you several hours to complete, but don't expect any kind of evaluation or response in return.
This experience has taught me not to do coding assessments or take-home projects for companies I'm interviewing for.
Create a Rails application that utilizes Calendly's developer API.
The following metrics were computed from 2 interview experiences for the Calendly Software Engineer role in Atlanta, Georgia.
Calendly's interview process for their Software Engineer roles in Atlanta, Georgia is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Calendly's Software Engineer interview process in Atlanta, Georgia.