Product Engineering, Not Feature Factories

We're a Product Engineering team. That means engineers are involved in all phases — ideation, research, analytics, planning, prototyping, validation, delivery, and launch. You won't be handed a fully specced ticket and told to implement it. You'll be in the room (or the thread) when the problem is being defined.

Shape Up

We loosely follow Basecamp's Shape Up methodology, but tailored to meet our unique needs. We only like to enforce just enough process to keep us super productive. Projects start as fat marker sketches — crude, intentional UI/UX concepts that communicate the core value proposition. If you think of a better way to present things while achieving the same outcome, you run with it.

This means less time in planning ceremonies and more time building. Less rigidity and more autonomy.

How Work Flows

We use Linear for issue tracking. Work typically flows like this:

• Shaping: Product and engineering collaborate to define the problem and scope the solution. Engineers are involved from the start; you're not handed a fully-specced ticket.
• Betting: We bet on shaped work for the cycle. Not everything gets bet on, and that's the point. Focus beats throughput.
• Building: Engineers own their work end-to-end within the cycle. You break down your own tasks, make your own technical decisions, and ship.
• Cooldown: Between cycles, we handle bugs, tech debt, and exploration. This is where the "less glamorous but critical" work lives, and it matters.

AI-Forward Development

We're not just "open to AI". We've built our entire development workflow around it. Our engineers use Claude Code, Codex, Cursor, GitHub Copilot, and Claude Desktop daily — five approved, enterprise-managed tools. We've developed custom AI skills, workflows, and automation that make our team punch well above its weight.

We believe AI tools are productivity multipliers, not replacements. We want engineers who are excited about pushing these tools to their limits.

Design Thinking

We bias our process toward iterative design, rapid prototyping, and early course correction. We do early and frequent demos, WIP and feedback sessions. Engineering and Product collaborate continuously rather than throwing requirements over the wall.