If there was a 2.5, that would have been my rating, but I figured I'd be nice because it wasn't totally terrible.
Morale is low; I mean, it feels like defeat.
There is a general absence of engineering culture. It was bizarre. I read an earlier review about Calendly being a "strange place," and it definitely is.
There are many groups that operate in basically silos, where workloads are vastly different (too much in some, too little in others). The communication between groups is crap. By communication, I mean sharing how they are building things, asking opinions about design/architecture, etc.
There is a disproportionate emphasis put on the new product features that are a small subset of users. It still has questionable product-market fit, so it's not even clear if all this work ends up helping. Yet, they seem to freak out when there are bugs or incidents affecting that part of the product.
They use Agile, but not really. It's Waterfall mashed into Agile, which doesn't work. Might as well just make a task board; you're not iterating.
It feels like the exec team have their heads in the sand.
Turnover is high. For how reasonable the work-life balance is, it's surprising it is that high. But this is because the morale is in the toilet and the direction of the company is... who knows.
Stop chasing the additional growth s-curves. Fix up your main product, lean out operating costs, and try to get acquired.
That, or get serious about prioritization, and then trust and empower your teams to do it.
The c-suite and VP levels need to get honest as a group as to what is needed to operate together. Actually do the "mandatory reading" and have those frank discussions with each other.
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