Growth Engineer (Global)
Beehiiv, Remote
Overview
beehiiv is where the world's best newsletters, podcasts, and digital products are built, grown, and distributed. The platform combines email, podcast hosting, websites, community, and digital products — connected to a single audience and a single set of tools to publish, grow, and monetize. As we approach $50M in annualized revenue and continue to grow almost 100% YoY, our rapidly growing product suite and incredibly strong brand position us for the next stage of hypergrowth.
The engineering team is small, senior, and ambitious. In the age of AI, the quantity of code someone can produce means very little. We care about end-to-end quality, architectural soundness, and people who own outcomes, not tickets.
Growth Engineering at beehiiv sits at the seam between marketing, product and engineering. The team owns the surfaces where someone first meets beehiiv and decides whether to start, create a habit, and pay. We are hiring a full stack Growth Engineer to join that team, reporting to our Lead Engineer, Growth, and working day to day with the marketing, product, paid acquisition, analytics, and lifecycle teams. You are technically talented, but as importantly have an eye for good design and interactions, can comfortably put yourself in the shoes of prospects and users, and understand experiment design and analysis.
As a team, we are focused on moving numbers across the funnel. Some of what you ship will be rolled back after a week because the data said so, other work will single handedly deliver months of revenue growth.
To apply, you must complete our Values Assessment Questionnaire here. We will consider your responses alongside your qualifications and experience as part of our overall hiring process.
Nice to have
Ideally, you'll have
- A strong full stack engineer. Rails (or an equivalent backend framework) plus React and TypeScript.
- You have shipped experiments in a high-traffic production funnel and can point to a result you drove, with the number.
- Analytical enough to run your own tests without a data team: you can write SQL, define the metric, size the opportunity, and call a result honestly, including when it loses.
- Fast and comfortable with ambiguity. A Slack message on Monday can be a live test by Thursday.
- Taste for landing pages and onboarding UX. You notice when a flow is bad and you can fix it without a designer holding your hand.
- Ownership from idea to deploy to readout. You communicate early and often and think about the success of the project beyond the ticket: comprehensive QA, documentation, and monitoring.
- Experience with Amplitude (or similar experimentation platforms like Statsig or Eppo)