Growth Engineer

About Revley

Autonomous commerce starts here.

A merchant should be able to describe a store and have it exist — landing page, product pages, cart, checkout — then have the money layer underneath it run without a team watching it. Routing, tokenization, subscriptions, disputes. Agents do the work. The operator signs off on anything that moves money.

We start at the foundation, payments and tokenization, and build up: checkout, subscriptions, multi-processor routing, dispute prevention, and the agents that operate all of it. Not a collection of integrations. One system.

The Role

Our promise is that a merchant can launch a full store in minutes. The engineering behind that promise is real; the path a merchant takes to discover it is not yet as good.

You will own that path. This is a build role, not a reporting role — you ship the landing pages, the onboarding flow, the activation instrumentation, and the experiments that tell us which changes actually moved a merchant from curious to live. You will write production code and you will decide what to test.

Responsibilities

• Own activation end to end: define what a live merchant means, instrument it, and move the number
• Build and ship landing pages, onboarding flows, and in-product prompts that get a merchant to a working storefront
• Design and run experiments with enough statistical care that we believe the result
• Build the analytics layer — event schema, funnels, cohort retention — so decisions are grounded in behavior rather than opinion
• Instrument and improve checkout conversion for merchants on our rails, and turn what we learn into product defaults
• Own lifecycle messaging and the triggers behind it, working with the agents that already watch merchant state
• Work directly with the founders on positioning, pricing experiments, and which segments to pursue

Required Qualifications

• Three or more years building user-facing product with measurable growth outcomes you owned
• Strong frontend engineering — TypeScript, modern React, and the craft to make a page feel fast and finished
• Comfort in the backend when an experiment needs it: APIs, data models, event pipelines
• Fluency with product analytics and experiment design, including when a result is not significant
• Demonstrated ability to pick your own priorities from a messy funnel and defend the choice
• Strong written communication — you will be writing the copy you test

Preferred Qualifications

• Experience at an early-stage B2B or commerce company through a real activation push
• Experience with self-serve onboarding for a technical product
• Background in e-commerce, subscriptions, or payments
• Design sensibility strong enough to ship a page without a designer

Our Stack