Build the browser that users deserve.
We’re a small team working on a hard problem: making sovereignty the default in the agentic web. If you want your work to matter to millions of people who will never learn your name, this is a good place to be.
Nine people. One browser.
Five in engineering and design, four in the research group, and no layer of management between you and the decision. That is the appeal and the cost of a team this size, and we would rather you know both before you apply.
Engineers decide
Everyone owns a meaningful slice of the product. There are no hands-off product managers. You make the call, you ship it, and you answer for how it went.
Meetings are the exception
Decisions get written down where anyone can find them later. One 30-minute sync a day across the founding team; almost everything else happens in text, on your own clock.
Competitive base, real equity
Market-rate salary benchmarked to your location, plus equity that is worth something if this works. We tell you the numbers in the first conversation, not the fifth.
What we’re hiring for.
We hire slowly and deliberately, and every person here shapes both the product and the culture. If none of these fit but you think you belong here, write to careers@dartbrowser.com and tell us why.
Senior Browser Engineer
Chromium core. Own the browser layer: the Chromium fork, the surveillance infrastructure we remove, and the seams where the identity layer and agent runtime attach. You have shipped a non-trivial Chromium patch before and know what that costs.
Senior Browser Engineer
What you’d do
- Maintain our Chromium fork and the rebase cadence against upstream
- Remove and replace Google service integrations without breaking web compatibility
- Build the process-model boundaries the agent runs inside
- Own performance and memory budgets across macOS, Windows, and Linux
What we’re looking for
- Several years in a large C++ codebase, ideally a browser engine
- Comfort reading and writing Chromium’s IPC and sandbox code
- A track record of landing patches upstream or maintaining a fork in production
Cryptography Engineer
Identity and key management. Design and implement the hardware-attested identity layer: TPM integration, Secure Enclave APIs, post-quantum algorithm selection, and the key lifecycle around all of it. You already understand why harvest-now-decrypt-later is a present-tense problem.
Cryptography Engineer
What you’d do
- Implement key generation and attestation against TPM 2.0 and the Secure Enclave
- Select, integrate, and keep current our ML-KEM and ML-DSA implementations
- Design recovery and rotation flows that stay usable for non-experts
- Work with external auditors on the annual review
What we’re looking for
- Production experience with applied cryptography, not just theory
- Familiarity with hardware security modules and platform key stores
- The judgement to say no to a clever scheme that cannot be audited
AI Engineer
Local inference and agents. Build the local agent runtime: model integration across Ollama, llama.cpp, and CoreML, the semantic index, retrieval, and the task execution layer. You have shipped something non-trivial that ran an LLM on someone else’s laptop.
AI Engineer
What you’d do
- Integrate local runtimes and keep them fast on ordinary consumer hardware
- Build and maintain the on-device semantic index over tabs, history, and files
- Design the agent’s tool-use loop and its permission boundaries
- Benchmark honestly and publish the numbers, including the bad ones
What we’re looking for
- Hands-on experience with local inference, quantisation, and memory budgets
- Retrieval systems built for correctness rather than demo quality
- A healthy suspicion of benchmarks, including your own
Founding Designer
Product and brand. Own the whole design practice: browser UI, agent interaction patterns, this website, and the brand. The hardest problem in browsers is making privacy and capability feel ordinary rather than technical. That is the brief.
Founding Designer
What you’d do
- Design the agent surface: how people grant, review, and revoke what it can touch
- Own the browser chrome, settings, and the permission model’s visual language
- Run the design system across product and marketing
- Prototype in code, or close enough that engineers can read it
What we’re looking for
- A portfolio with at least one dense, technical product you shipped end to end
- Comfort designing for people who will not read documentation
- An opinion about what should not be in the interface
Pitch us yourself.
If you care about browser privacy, local AI, or cryptographic identity and don't see a role that fits — write to us anyway. Tell us what you'd build.