Composio
Growth and Data Engineer
About this role
Composio seeks a Growth Engineer to drive product adoption and retention by shipping rapid experiments across the full stack. You'll own activation problems end-to-end, combining data analysis with product building to identify and execute high-impact growth opportunities.
What you'll do
- Ship growth experiments spanning landing pages, onboarding, backend services, and dashboards
- Instrument product funnels, write SQL queries, and build dashboards to guide investment decisions
- Own activation and retention problems independently without relying on product tickets
- Collaborate with marketing, product, and engineering to convert distribution ideas into shipped features
- Scope experiments ruthlessly to validate ideas quickly before full builds
- Use AI agents and Composio's platform to optimize personal workflows
What they're looking for
- Full-stack engineering (frontend and backend)
- SQL and data analysis
- Product sense and rapid experimentation
- AI/LLM development experience
- Analytics and tracking implementation
- Context-switching across codebases
- Product ownership mindset
- Communication and transparency
Benefits
- $25M Series A funded by Lightspeed
- 3x ARR growth with enterprise customers (Zoom, Glean, Wabi)
- Small team of talented engineers
- Autonomy to own growth problems end-to-end
- Access to AI infrastructure tools
- San Francisco location
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Composio
Composio builds agent-to-tools infrastructure that enables AI agents to interact with external systems and APIs. The company is hiring AI engineers, deployment specialists, growth engineers, and customer-focused research engineers to expand its platform, improve production deployments, drive adoption, and work directly with enterprise customers.
- Website
- composio.dev
Likely interview questions
- Walk us through a growth experiment you shipped end-to-end—from hypothesis to measurement. How did you decide what to build versus what to skip?
- Tell us about a time you had to ship something quickly to get signal. How did you balance speed with not cutting corners on product quality?