Member of Technical Staff, Founding Engineer
$240,000 - $340,000 per year
Apply (opens in a new tab)Member of Technical Staff, Founding Engineer
Posted yesterday
SENIORITY
Lead
SALARY
$240,000 - $340,000 per year
About the role
- Own the design, architecture, and implementation of the Private Agent One core platform: agent runtime and orchestration, memory, tool use, and the consent layer (PCHP) that governs every movement of a person's information.
- Build the platform services the product runs on — identity, delegation and permissions, encrypted data planes, sync across devices and cloud — designed for billion-user scale from the first line, not retrofitted later.
- Embed with users and partners to scope and deliver deployments: discovery, technical design, hands-on build at their side, production rollout, and operation after go-live.
- Build the internal tooling that makes the whole lab faster: eval harnesses, deployment automation, observability, and the paved roads every engineer here ships on.
- Turn field findings into platform abstractions and product feedback that visibly change the roadmap.
- Set the engineering bar by example: design reviews, code reviews, tests green and a real human walkthrough of every flow. Never tests alone. Expectations
- You ship. Working software in front of real users, on a cadence measured in days, not quarters.
- You are an engineer first and a trusted advisor second — in that order, and both for real. Users trust you because your systems work.
- You write clearly. Scopes, design docs, and field reports that a product team can act on without a follow-up meeting.
- You treat sales, customer service, engagement, and empathy as engineering requirements. A deployment the user doesn't love is a failed deployment, whatever the code did.
- You will generate outcomes worth 100× your pay. That is the founding bar, stated plainly.
- 10+ years of professional software engineering experience, building and operating production systems.
- The last 5 years building AI products — and product depth in at least one of: personal information systems, subscriptions, ads, or relevance/ranking. You understand how these systems make money and how they fail the user.
- A track record of building for very large scale: systems serving millions of users, or platform infrastructure that does. Billion-user scale is the design bar here; your experience must be on that trajectory and you must be able to prove it in numbers — load, failure modes, tail latency.
- Production depth across the stack: backend services, data systems, and at least one native client platform. You debug across boundaries instead of escalating at the edge of your layer.
- Customer-facing engineering experience: you have scoped, built, and shipped with real customers in the room, and owned the result after launch.
- Bachelor's degree in computer science, engineering, mathematics, or a related field — or equivalent experience demonstrated in shipped systems. Technical requirements
- Languages: expert in at least two of Python, TypeScript, Go, Rust — and able to read and ship Swift and Kotlin.
- Client platforms: native building across iOS and macOS (Swift/SwiftUI), Android (Kotlin/Jetpack Compose), web (React/TypeScript), Chrome extensions, and Windows. Our agent lives on every surface the user does.
- Backend and data: distributed services (gRPC/REST), PostgreSQL, Redis, Kafka or equivalent streaming; data modeling for consent-scoped, encrypted, per-user data planes; end-to-end encryption and key management.
- Agent systems: LLM APIs and on-device inference (llama.cpp, MLX, Core ML, ONNX Runtime); tool use and function calling; retrieval (embeddings, pgvector/Qdrant-class vector stores); agent evaluation harnesses and regression testing of model behavior.
- Cloud and infrastructure: production systems on at least one hyperscaler (AWS, GCP, or Azure); Kubernetes, Terraform, Docker; CI/CD (GitHub Actions or equivalent); observability with OpenTelemetry, Prometheus/Grafana, Sentry-class tooling.
- Security: OAuth 2.0/OIDC, SSO/SCIM integrations, least-privilege design, threat modeling for systems that hold a person's entire information life. Compensation
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.
