Engineering Generalist - Product Impact (Full Stack)

Description

About Pocket

At Pocket, we’re building the future of human memory.

Some of the most valuable information in our lives disappears when a conversation ends: an idea, a decision, a detail we wish we could remember. Pocket helps us hold onto it.

We’ve built an AI-powered device that captures real-world conversations and turns them into searchable transcripts, summaries and next steps. Backed by Accel and Y Combinator (W26), we’ve already sold 500,000 devices.

Our ambition goes beyond recording. We believe the things you learn, discuss and experience can become useful context for the AI tools you already use, and for products that don’t exist yet.

About the Role

Sometimes the most useful thing to build is a better onboarding flow. Sometimes it is a backend service, a faster API or the instrumentation that explains why customers leave.

We’re looking for an engineer who can follow the problem across those boundaries. You’ll work across backend and frontend, ship changes end to end and measure whether they made the product better. You’ll work closely with product, design, marketing and support, without needing every task to fit one narrow specialty.

What You’ll Own

Projects from instrumentation and data models through services, user interfaces, rollout and iteration.

Features and experiments that improve activation, retention, paid conversion and the core experience.

Backend APIs, pipelines, jobs and systems that stay reliable as usage grows.

Frontend improvements across the web product, internal tools, landing pages and onboarding.

Clear hypotheses and measurement, followed by the work needed to make successful experiments production-ready.

Requirements

• 6–10+ years shipping production software, ideally in a startup environment.
• Strong backend fundamentals: APIs, databases, asynchronous jobs, caching, performance and reliability.
• The ability to ship frontend changes in React/TypeScript or a comparable stack.
• Product judgment: you can turn an unclear problem into useful work and explain the result.
• Performance and reliability habits, including profiling, latency budgets, observability and graceful degradation.
• A preference for simple systems, fast learning and responsible delivery over unnecessary complexity.
• Bonus Points
• Experience with experiments, analytics instrumentation, funnels or cohorts; internal tools; or building products from zero to one.
• Our Stack
• Flutter for mobile; React and TypeScript on the frontend; Go and Node on the backend; Postgres and Redis for data.
• What Success Looks Like
• Shipped work improves activation, retention or revenue. Production systems are observable and reliable. The architecture remains simple enough for the team to keep moving.

Benefits

• You’ll work close to the product and the people building the company. Your scope follows the problem, so you can connect a technical change to a customer or business result instead of handing it off at the edge of one codebase.