Back to jobs

Member of Technical Staff

Berkeley

Member of Technical Staff (0→1 Product Engineering)

About the Role
We’re looking for a Member of Technical Staff to help build from zero to one, turning ambiguous ideas into real, working systems. This role is for someone who thrives in early-stage environments, moves quickly with incomplete information, and takes ownership from concept to production.

You won’t be handed fully defined problems. You’ll help define them.

What You’ll Do

  • Build and ship core product systems from scratch

  • Translate ambiguous ideas into scoped, testable, and shippable solutions

  • Work closely with research, product, and leadership to shape product direction

  • Design systems for reliability, speed, and iteration 

  • Own outcomes end-to-end: architecture, implementation, and deployment

  • Continuously refine systems based on real-world usage and feedback

What We’re Looking For

  • Proven ability to operate in 0→1 environments (startup, new team, or new product lines)

  • Strong backend or systems engineering fundamentals

  • Ability to make decisions with incomplete information and move forward

  • High ownership mindset — you don’t wait, you drive

  • Clear, structured thinking when solving complex problems

  • Comfort working across the stack when needed

Attributes That Matter

  • Builder Mentality: you ship, not just design

  • Judgment Under Ambiguity: you make sound calls without perfect data

  • Velocity with Intent: you move fast, but with direction

  • Systems Thinking: you understand how components connect and scale

  • Accountability: you own outcomes, not just tasks

Nice to Have

  • Experience building production systems used by real customers

  • Background in ML/AI systems, data-intensive applications, or infrastructure

  • Experience at early-stage startups (Seed–Series B)

Why This Role

  • Direct impact on product direction and company trajectory

  • Work on problems that don’t have predefined answers

  • Small, high-caliber team with high ownership

  • Opportunity to define how things are built; not just build them

 

Interview Process 

1 — Intro (Written)
Prompt: What is the hardest thing you’ve built?

  • We assess ownership, execution, and ability to ship real systems.

2 — Product Call (30 min)

  • Align on what you’ll build. We evaluate product thinking, scoping, and prioritization.

3 — Build + Demo (~2 hrs, onsite)

  • Live working session where you build and present a solution.
  • We assess execution, system design, and clarity of thought.

4 — Final with CEO

  • Focused conversation on decision-making, ownership, and alignment.

Decision is made immediately after final round.

What to expect:
Fast process. Real problems. High ownership. No busywork.

 

 

Apply for this job

*

indicates a required field

Phone
Resume/CV*

Accepted file types: pdf, doc, docx, txt, rtf


What is the hardest system you’ve built end-to-end?

Please be specific. We are looking for:

  • Your personal ownership (what you actually built, not just the team)
  • The constraints or tradeoffs you faced
  • What made it difficult to get to production
  • What you learned from the experience

Focus on a real system that was shipped, not a theoretical or team-level overview.