Back in 2018-2019, we had management who frankly showed little empathy to engineers and never understood what his engineers were going through. They pushed on us near-impossible deadlines to build new features to grow the business while we were drowning in tech debt and scalability issues. When systems went down because no one had time to fix them because of impossible deadlines, they blamed the engineers for not writing scalable code. When we engineers asked for compensation for the tough on-call schedule, they responded that it was the engineers' basic job to own their code and be on-call for it. When we complained that we couldn't both push out new features and improve scalability/tech debt without being overworked, they replied that didn't see why we couldn't balance those two things. Well, due to a change up in leadership plus new directions set by Justin, that has all changed!
We've seriously done something close to a 180. We're finally tackling tech debt instead of endlessly building flimsy features! Things look much, much brighter now, though many engineers still are emotionally recovering from 2019.
Other pro no one has mentioned: Iterable is very, very much a meritocracy. Work hard and you'll be sure to be promoted. I know of two people who started off inexperienced, fresh, junior, but man did they work hard! They put in 60+ hour weeks and were promoted twice in 3 years. That's quite motivating for me, at least!
Also, all the managers I've had and worked with have been doing their jobs well in my opinion. No micromanaging, care about you as a person, just want to see you succeed.
There's still tons of scalability issues that resulted from building more flimsy features while letting the system burn in 2019, but I am hopeful we'll be past this in a year.
Base salary seems to be below market though HR likes to claim we're in 75% according to Radford. Equity is almost for sure lacking, but HR has admitted their mistake and are changing this one.
Please please remember the lessons of 2019, how we lost valuable engineers and customers because of underestimating our tech debt again and again.
Iterable reached out to me on Hired.com, and set up an initial video interview with live coding, which was followed by another technical video interview. Next up came the onsite interview, which was about 5 hours and included meeting with multiple en
I had a call with a member of their recruiting team first. They asked me a ton of questions, starting from why I got into computer science. After that, I got a phone interview with an engineer. Then they told me I got positive feedback from the codi
I was approached by a recruiter from the company, the entire interview process consisted of seven rounds. The first round was a technical phone screen. The virtual onsite consisted of 5 rounds (4 rounds on the 1st day and 1 round on the 2nd day Th
Iterable reached out to me on Hired.com, and set up an initial video interview with live coding, which was followed by another technical video interview. Next up came the onsite interview, which was about 5 hours and included meeting with multiple en
I had a call with a member of their recruiting team first. They asked me a ton of questions, starting from why I got into computer science. After that, I got a phone interview with an engineer. Then they told me I got positive feedback from the codi
I was approached by a recruiter from the company, the entire interview process consisted of seven rounds. The first round was a technical phone screen. The virtual onsite consisted of 5 rounds (4 rounds on the 1st day and 1 round on the 2nd day Th