Moving to a Growth Engineering Role

Question

In all my previous roles, I've been a Software Engineer. My day-to-day in these roles mostly consisted of designing systems, implementing new features, and fixing bugs.

I now have an offer to join a company as a Growth Engineer. This role sounds much more oriented around running engineering experiments (i.e. A/B Testing) to increase the company's user base, paying customers, etc.

I'm interested in hearing from people who have switched to a Growth Engineering role. Do you like this role compared to being a more "traditional" Software Engineer? Would you recommend a Growth Engineering role to others?

madscience · Accepted Answer

My role is pretty similar to your other roles, pretty low key software engineering and I've always been curious about that type of 'growth engineering' also. I've had some friends in similar roles and they said they've liked it a lot, but it can be tough trying to navigate the corporate politics sometimes. Just having to manage expectations with so many different parties that don't always understand what's going on.

19g615kyuumk7e · Answer

I’m not sure what you mean by traditional. Code is code. It’s just the problem space that different. I don’t care about coding products anymore. So I usually take backend infrastructure focused roles

Moving to a Growth Engineering Role

About

Software Engineer

Members