Back to careers

Product engineering

Member of Technical Staff

This is a broad product-engineering role for someone who wants to work close to the product itself. The work spans frontend systems, backend flows, data quality, internal tooling, and the discipline needed to keep a fast-moving product coherent.

Applications opening soon

Role summary

Build the product, infrastructure, and internal systems that turn AI search activity into a reliable operating surface for marketing teams.

Why this role exists

The product surface is expanding quickly, and the cost of weak architecture compounds fast. We need someone who can ship broadly while improving system shape instead of adding more glue.

First 90 days

Ship meaningful improvements to at least one major product surface.

Why this role exists

The product surface is expanding quickly, and the cost of weak architecture compounds fast. We need someone who can ship broadly while improving system shape instead of adding more glue.

What you will work on

  • Build and refine core product surfaces across the marketing site, dashboard, reporting, and supporting internal workflows.
  • Own end-to-end feature slices across UX, backend contracts, and data flow instead of stopping at one layer.
  • Improve the maintainability of the system as new analyses, templates, and reporting use cases are added.
  • Work directly with founders to turn product direction into fast, defensible execution.

What a strong fit looks like

  • Strong full-stack engineering judgment and the ability to improve abstractions, not just add code.
  • Experience shipping product features where data contracts, UX, and system behavior all matter.
  • A bias toward readable systems, explicit contracts, and architecture that survives iteration.
  • Comfort working in a small team where ownership is broad and expectations are high.

What will excite you here

  • Building a product in a category that still has room for sharp product and technical decisions.
  • Owning real product slices instead of being boxed into a narrow component lane.
  • Turning messy workflows into clear, high-signal software.

First 90 days

  1. 01Ship meaningful improvements to at least one major product surface.
  2. 02Remove at least one architectural bottleneck or brittle implementation pattern from the current system.
  3. 03Raise the bar on quality in a way other contributors can feel immediately.

Hiring process

The process is intentionally short, direct, and anchored in the real work.

  1. 1

    Apply

    Send us your background, relevant work, and why this role makes sense for you.

  2. 2

    Foundational conversation

    A focused conversation about your work, your judgment, and the role itself.

  3. 3

    Role-specific deep dive

    A discussion or exercise that looks like the actual work more than a generic interview loop.

  4. 4

    Founder conversation

    A final conversation on standards, ambition, and what success would look like here.

  5. 5

    Decision

    We close the loop clearly and move quickly once there is conviction.

Need context before you apply? [email protected]

Member of Technical Staff

We are not taking applications for this role yet. We will update this page when it opens.

Questions in the meantime? Email [email protected].