0to1 Engineer

Mozilla is building a position in open source AI through research, community, tooling, and public advocacy. They are seeking a 0to1 Engineer to build working prototypes of developer surfaces and applications on top of open source AI infrastructure, fostering engagement and conversation within the developer community.

Responsibilities:

• Build working prototypes of developer surfaces, tooling integrations, and applications on top of open source AI infrastructure — with a bias toward shipping something real in days, not weeks
• Work with coding agents and AI-assisted development tools as a core part of your workflow — not as a novelty, but as the way you operate
• Translate concepts, framing documents, and strategy ideas into demonstrations that can anchor a conversation, a community event, or a piece of content
• Collaborate closely with the social media and community team so that what you build is legible and shareable — demos that developers can understand and react to, not just screenshot
• Contribute to Mozilla's open source repositories and work in the open; your code should be something the community can fork, extend, and learn from
• Stay close to the open source AI ecosystem — know what's being built, what's broken, and where a working prototype can surface a real gap or opportunity
• Help evaluate and opine on open source AI tools, stacks, and developer surfaces through the lens of someone who's actually tried to build on them

Requirements:

• Solid software engineering fundamentals — you write code that others can read, and you know the difference between a prototype and production
• Demonstrated comfort working with coding agents and AI-assisted development tools (Cursor, Claude Code, or equivalent) as a force multiplier, not a crutch
• Experience with the open source AI stack: inference, orchestration, evaluation, or adjacent layers — you've built something real on top of open models
• Fluency in Python and/or TypeScript, with enough range to pick up whatever the project needs
• Experience building APIs, developer-facing tools, or integrations — you understand what it means to build for other builders
• A strong sense of what makes a prototype useful for a conversation, not just technically functional
• Comfort working in public — open repos, community feedback, building in the open
• Strong written communication; you can explain what you built and why, to a technical audience, without over-engineering the explanation