Takeover logo
Takeover

CAREERS · FOUNDING TEAM · 3 OPEN

Help us build the
operating system for the company.

Most software is built for a single workflow. We're building for the whole shape of running a company — books, code, hiring, contracts, comms, compliance — in one window, driven by an on-call agent that takes the action. It's the kind of thing most people say can't be built. That's why we're building it.

WHY JOIN NOW

Pre-seed. Pre-revenue at scale. Two founders, one sales engineer. The product works and customers want it. You will be employee #4 through #8. Your fingerprints will be on every surface, forever.

Equity-meaningful, salary-honest. We'll show you the cap table on the first call.

§01

How we work.

Operators, not abstractions.

We're building this because we needed it. Every product call gets stress-tested against 'would I, an actual operator, use this on Monday morning?' If the answer's no, the call gets rolled back.

Taste is a budget line item.

Most B2B software looks like B2B software because nobody on the team gave a shit. We do. Design isn't decoration here — it's how customers know we're serious.

Cadence over consensus.

We ship weekly, sometimes daily. We debate the call once, ship the call, learn from the call. Strong opinions are welcome, gridlock isn't.

Show, don't memo.

When you have a take, build the demo or the doc that proves it. Internal meetings tend to be short because the work is already on the screen.

§02

Open roles.

Founding Engineer · Desktop

Own the native desktop runtime. Tauri shell, Rust core, native OS integrations (screen capture, accessibility tree, system audio, notification routing). You're the person who makes Takeover feel like a real Mac app, not a webview wrapped in chrome.

Engineering Full-time · Founding Remote (US / EU) · CA HQ optional

What you'll own

  • Architect and ship the Tauri / Rust runtime that hosts AXON and every module
  • Build native OS integrations: screen vision, accessibility tree, audio capture, file-system primitives
  • Own the desktop release pipeline (notarization, code signing, auto-update, crash reporting)
  • Partner with the AI engineer to expose runtime capabilities to AXON cleanly
  • Be the technical voice in conversations with security-conscious customers (on-prem, SOC 2)

You are

  • Shipped a non-trivial desktop app before (Tauri / Electron / native), bonus for cross-platform
  • Comfortable in Rust and TypeScript; willing to drop into Swift / Objective-C when needed
  • Think in terms of process boundaries, IPC, and what the OS lets you do vs. what it doesn't
  • Have a strong opinion on why native > web for this category of product

Bonus

  • Open-source maintainer (Tauri, Bun, Deno, Wasmtime, etc.)
  • Worked on a screen-recording or accessibility-tree product
  • Built something agentic that interacts with the OS, not just the browser
Apply

Founding Engineer · Applied AI

Own AXON. Agent orchestration, ensemble reasoning, tool calling via MCP, memory layer, voice loop. You decide how AXON plans, what it asks before acting, and how it recovers from its own mistakes. This is the brain.

Engineering Full-time · Founding Remote (US / EU) · CA HQ optional

What you'll own

  • Design and ship the AXON agent loop: planner, executor, critic, memory, verifier
  • Wire 500+ tool integrations via the Model Context Protocol cleanly and safely
  • Own the voice surface (real-time STT, intent routing, voice-led confirmations)
  • Build the evaluation harness — how do we know AXON is getting better, not worse?
  • Define what AXON refuses to do (and why) so users trust the system

You are

  • Shipped a real agentic product, not just a tools-around-an-LLM demo
  • Have strong opinions on planning, reflection, tool-calling reliability, and memory
  • Can write a clean evaluation: not vibes, not benchmarks-for-the-tweet, real measurement
  • Comfortable saying 'this is the wrong model choice here' and switching providers in a day

Bonus

  • Built something with MCP, AutoGPT-class scaffolding, or LangGraph in production
  • Have worked on agent-safety, prompt-injection defense, or autonomy guardrails
  • Open-source contributor to an AI tooling project
Apply

Founding Designer

Own the visual and interaction system for both the desktop app and the marketing surfaces. You're the reason Takeover looks like it cost $20M to build when it cost almost nothing. Product, brand, marketing, motion — one person for now, your team later.

Design Full-time · Founding Remote (US / EU) · CA HQ optional

What you'll own

  • Own the design system for the desktop app (components, motion, typography, iconography)
  • Design every new module from the first pixel — bookkeeping, contracts, hiring, comms
  • Lead the marketing site, the pitch deck, the keynote, the demo videos
  • Set and enforce the bar: editorial, calm, dense, opinionated, never generic
  • Hire the next two designers when the time comes

You are

  • Have shipped a real product (not just dribbble-class work, real users)
  • Equally comfortable in Figma, Framer, and front-end code (you can ship your own ideas)
  • Have a portfolio that includes both product UI and editorial / brand work
  • Can defend a design decision without invoking 'best practices'

Bonus

  • Have shipped a desktop product (different constraints than web)
  • Have written about design publicly — essays, talks, podcast appearances
  • Have any motion-design background (After Effects, Lottie, Rive)
Apply

Operations & Customer Success

OPENS Q3 2026

Run the operator-onboarding loop end-to-end. You're the first call after a customer signs, the person who turns 'I bought this' into 'this is how I work now,' and the loudest internal voice for what we should build next.

GTM Full-time · Opens Q3 2026 Remote (US) · CA HQ optional

What you'll own

  • Own customer onboarding: stack audit, MCP setup, AXON personalization, success criteria
  • Run weekly office hours for new customers, debrief sessions for veterans
  • Translate every customer signal into product input — feature requests, bug repros, churn risks
  • Build the playbooks, the help docs, the recorded walkthroughs
  • Define and track the success metrics that prove Takeover earned its keep

You are

  • Have run customer success or implementation for a B2B SaaS / vertical product
  • Operator-adjacent — you've actually run a team, a P&L, or a fundraise yourself
  • Comfortable with technical context (you can debug an MCP config, read a JSON log)
  • Care about the difference between 'happy customer' and 'changed-their-work customer'
§03

How we hire.

STEP 01

Intro call · 30 min

Ali or Hanif on Zoom. We tell you the unvarnished truth about the company, you tell us what you've actually shipped. No coding, no whiteboarding. Just talk.

STEP 02

Take-home or pairing · 2–4 hrs

One scoped problem. You can do it solo and we review it, or pair with us live for an hour and we co-build it. Your call. We pay for take-home time at a fair rate.

STEP 03

Team day · 4 hrs

Half a day on Zoom or in CA with the whole team. Two technical conversations, one product-judgment conversation, lunch (we'll buy).

STEP 04

References + offer · 1 week

We call 3 people you've shipped with. We make the offer. We share the cap table. Total time from first call to signed offer: usually 2 weeks, can be 1 if everyone moves.

DON'T SEE YOUR ROLE?

Tell us what you should be doing here.

If you're excellent and the shape of your role would be obvious to us once we read about you — write to us. Ali responds to every email.

unfold@codewithali.com