Taro Logo

Great product and talent, but understaffed engineering

Senior Software Engineer
Current Employee
Has worked at Iterable for 2 years
January 23, 2020
3.0
Doesn't RecommendPositive OutlookNo CEO Opinion
Pros
  • I love the people I'm working with
  • Using some of the best-in-class technology in the stack, great exposure to big-data tooling and functional programming
  • I have an overall positive outlook for the future of the company
Cons

The platform follows a pretty regular cycle:

  1. Performance degrades to everything-is-on-fire status
  2. Everyone scrambles to bring the platform back from the brink of destruction under the threat of all our huge customers churning
  3. Just as soon as the platform is no longer considered "on fire", most everyone gets shifted back to feature work
  4. Return to step 1

The reasons I see this happening are:

  • The product is actually really useful, so existing customers keep using it more and more, and sales is able to bring on more and more customers
  • Iterable keeps signing contracts with new and existing customers that mandate new features and work
  • The sales and customer support departments grow at a disproportionate rate to engineering capacity

This all manifests as the engineering department being directed by a schizophrenic amalgamation of priorities. One minute you're doing all you can to write a feature to get a huge customer contract, the next you're trying to get 10% more scale to handle increased load that is threatening to collapse the system, the next you're fixing one of the hundred #1 priority customer reported bugs.

Since you often only get a few days at a time to focus on any given thing, you're constantly context switching between one thing and another, often before you even finished the last thing you were working on. This effectively reduces the problem-solving capacity of the engineers even further.

Advice to Management

Look, I don't have access to all the numbers management does. For all I know they're pursuing what really is the optimal long-term strategy to grow the company. What I see as a rank-and-file engineer though is that the demand for increased scale and features is increasing at a much greater pace than engineering capacity.

Something has got to give, and at the current rate I expect that to manifest as continued talent churn, unfulfilled feature contracts, and regular system failure. But I guess if you can successfully portray the system as "everything is just fine", you can potentially keep up the facade until profitability and then go back and fix the carnage.

Was this helpful?

Iterable Interview Experiences