Backend Engineer (Golang)

About This Role We're standing up a dedicated Growth Squad: a small team whose entire job is to move our key metrics by experimenting in production, fast. Activation, conversion, retention, expansion — we have ideas for all of them, and the only way to know which ones work is to ship and measure. This isn't a roadmap-and-specs team. It's high tempo. We run several experiments a week, sometimes more, straight into production. Some of them work and we keep them; most don't and we kill them. The point is to learn quickly which levers actually move the business, then go back and harden the ones that earned their place. You'll be the backend half of this squad, working closely with a frontend engineer, and coordinating with people in Europe and on the US West Coast. What You'll Work On Ship experiments fast. Build and launch backend changes that test a hypothesis — a new pricing nudge, a credit-pack variation, an onboarding tweak, a flow that touches how enrichment results are delivered. Get it live, instrument it, read the numbers. Work inside the existing system. These experiments don't live on a greenfield. You'll be making targeted changes across an existing Go codebase — including, sometimes, the billing and credit system. Not rewriting it, but reaching into it confidently and safely to test something, then backing it out cleanly if it doesn't pan out. Promote what works. When an experiment proves its worth, you come back and do it properly — clean up the V1, add the tests, make it production-grade. Knowing what to harden and what to throw away is most of the skill. Measure everything. An experiment without instrumentation is a guess. You'll wire in the tracking that tells us whether a change actually moved the metric it was supposed to.