I gave Iterable 3-stars nearly 2 years ago, now upgrading to 4-star.
I've been here more than 3 years now and I have a very positive outlook for the company. Working here has its challenges, but I'm long on Iterable.
Iterable's values are Trust, Humility, Growth Mindset, and Balance and the company succeeds at embedding these systematically in most processes. If you share these values then this will – realistically – affect you positively when you work here.
Lots of growth opportunity: customer-base is growing rapidly, engineering headcount is growing, and the product is scaling. And correspondingly, Iterable is very talent-hungry.
The company is very introspective; they regularly measure and reflect on what is working and what isn't, and processes change and grow to adapt to the changing environment.
Internal technology is excellent. Scala is a joy to work with, plenty of exposure to various queueing, caching, and storage technologies. Forward thinking.
On-call has gotten WAY better. Still has things I'd like to improve but it is by far the best on-call of any company I've worked at and the load is spread evenly across an ever growing engineering team. You have carte blanche approval on fixing most on-call issues.
As I mentioned above the company is very introspective about discovering and fixing issues as they arise, which is absolutely necessary because even with that process in place it's hard to keep up with the difficulties that growing brings.
As such, most of my cons are directly tied to growing pains.
Team-building and connection
My biggest con right now is the lack of connection with my team.
The causes here are twofold: COVID travel restrictions and the pace of headcount growth.
COVID: Iterable has not sponsored in-person team gatherings for a long time now, and I think they really really need to start bending on this hard-line policy and allowing safe and consensual gatherings of vaccinated colleagues.
Team-building over Zoom is 10x less effective than in-person, and the lack of connection with my colleagues significantly affects my motivation and productivity.
My advice: Trust your employees to make their own health decisions and resume sponsoring in-person team gatherings.
Headcount growth: After you've spent months struggling to build some connection with your teammates, your team splits and new faces are hired and you have to restart.
This has happened to me several times since I've been here and I'm running out of motivation to re-boot new connections with my new colleagues.
My advice: Stop splitting teams in half by mitosis – particularly my own team ;) – and instead bud new teams with small seeds from other teams.
Engineering resource allocation
Engineering resource allocation has NOT achieved Balance (one of our core values!) the entire time I've been here; I've seen it swing from feature development to on-call to reliability to product to security.
The pattern is always the same: one group gets an outsized proportion of resources, other groups suffer until they make noise and the pendulum swings the other way, lather, rinse, repeat.
I am not an executive, but my advice: set a fixed percentage to each, leave 20% "flex" that can be assigned ad-hoc.
Either separate the Product backlog from Security, Reliability, Engineering, etc or grant the job of backlog prioritization to an independent arbiter.
Lack of investment in engineering quality-of-life
There is a category of issues with dispersed cost that require concentrated medium-term effort to resolve.
Everyone knows what I'm talking about; CI is slow, staging is down (or not effective), compile times are too long, dev environment setup is complicated.
Every engineer pays the price of the fatigue each of these causes.
Highly motivated individuals may be able to convince their manager to give them time to fix ONE of these things, but this work needs to become systematized because our ad-hoc approach is highly ineffective.
My advice: measure impact, make KRs to improve, and assign a minimum of 2-3 engineers to work on this for 3-4 quarters.
Persistent and sticky on-call issues
There are a few incidents that recur over and over which match this pattern:
They are inevitable given the fundamental design of the system
They require moderate investment and diversion of resources to fix
They have a high long-term cost to engineering (they ARE incidents)
Since there is no short-term quick fix, so we never address the root cause
The last two bullet points I think have a COMMON CAUSE: a reluctance to invest in long-term projects that benefit ourselves internally and which only benefit the customer in an indirect manner.
The Product org can and does engage in long-term planning that benefits them, and Engineering can get priority for on-fire issues that directly affect the customer (PG upgrade, Pulsar migration), but when the front-line ICs are paying the price we end up holding the bag.
I trust you. Y'all work extremely hard and I appreciate the herculean efforts you put in every day. Thank you.
Keep doing what you're doing: listen to your employees and don't be afraid to change things.
Biggest thing ask I have: increase your long-term investments in eng happiness & productivity, I really believe it will pay dividends in both retention and productive output.
The recruiting staff reached out to me via LinkedIn. They are very nice people and were extremely helpful during the interview process. The interview was very thorough, which has its pros and cons as an interviewee. I believe I had 5 technical inter
I had an initial call with the recruiter, a technical phone screen, followed by 2 rounds of tech interviews, a project presentation, and 2 behavioral rounds. Make sure that you are well prepared for the technical and behavioral rounds.
I would call Iterable's process just right. The technical rounds were enough to assess my core competencies. The soft skill rounds were interesting and aligned to the role. All in all a great experience.
The recruiting staff reached out to me via LinkedIn. They are very nice people and were extremely helpful during the interview process. The interview was very thorough, which has its pros and cons as an interviewee. I believe I had 5 technical inter
I had an initial call with the recruiter, a technical phone screen, followed by 2 rounds of tech interviews, a project presentation, and 2 behavioral rounds. Make sure that you are well prepared for the technical and behavioral rounds.
I would call Iterable's process just right. The technical rounds were enough to assess my core competencies. The soft skill rounds were interesting and aligned to the role. All in all a great experience.