The majority of teammates were good. The paycheck was received on time.
This company operates in a way that’s hard to define as typical for an organization. As an engineer, you might spend six months or more building a feature that will eventually be released to just 5% of users, only to be left in limbo afterward.
There’s also minimal focus on prioritizing or allocating time to address technical debt. Throughout the process, priorities are often shifted, with decisions driven more by the leadership team’s fluctuating preferences than by data or user research.
Once a project is completed, leadership tends to express frustration over timelines, without recognizing that the delays were a direct result of their own decisions or lack of clear direction. This would be more manageable if it seemed leadership had the competence to effectively guide the organization. They need to trust the people they hire to do the jobs they were brought on to do.
There was a time when this company was a great place to work, but that was over two years ago. While the tech industry as a whole faces challenges, joining Calendly now would be akin to catching a falling knife. The product has managed to stay afloat and even thrive for years despite the leadership, but now the market has caught up with it.
If you’re a user, consider switching to one of the many other alternatives. If you’re a prospective engineer, look elsewhere—somewhere that values individual contributors and engineering in general.
Maybe stop watching HBO's Silicon Valley?
Not a long, drawn-out process, and the team was friendly throughout. There were some hiccups, but the overall process went pretty smoothly. The coding portion of the interview process was very straightforward and relevant to the actual codebase; no p
Interview with hiring manager, asking basic questions. Then, a take-home project to build an integration with Contentful. They wanted to see the full app architecture. It was a pretty involved project.
1. HR screen: ~40 minutes 2. Screening with hiring manager: ~1 hour 3. Take-home exam: ~4-5 hours to expand on a Ruby on Rails and Node.js app. 4. Virtual on-site: ~4 hours
Not a long, drawn-out process, and the team was friendly throughout. There were some hiccups, but the overall process went pretty smoothly. The coding portion of the interview process was very straightforward and relevant to the actual codebase; no p
Interview with hiring manager, asking basic questions. Then, a take-home project to build an integration with Contentful. They wanted to see the full app architecture. It was a pretty involved project.
1. HR screen: ~40 minutes 2. Screening with hiring manager: ~1 hour 3. Take-home exam: ~4-5 hours to expand on a Ruby on Rails and Node.js app. 4. Virtual on-site: ~4 hours