How we work
- Remote-first, with office days in Jakarta and Singapore for those who want them.
- Async by default. Two synchronous meetings per week tops. The rest is a thoughtful pull request.
- Two-week shipping cadence. Every release goes to /changelog.
- Open-core values. The agent runtime is Apache-2.0. We make decisions in public on GitHub Discussions.
- Comp: competitive base + meaningful equity. We publish bands inside the company and disclose them in the first conversation.
Open roles
Founding engineer · full-stack
Hiring· Remote (UTC+7 ± 3)Own a slice of the platform end to end — Next.js + Prisma + Vercel AI SDK on the cloud side, Node + the daemon on the local side. You ship two weeks at a time, comment your code generously, and care about the user-facing details.
Founding engineer · ML / agents
Hiring· Remote (UTC+7 ± 3)Make missions actually good. Tool-call planning, multi-step verification, evals harness for the agent loop. Bonus if you've built tool-using agents in production and have opinions about when to stop adding tools.
Designer · product
Open to chats· RemoteBring craft to a product currently designed by an engineer with strong taste but limited Figma talent. Mission Control, the chat surface, and the bridges admin are all areas with room to grow.
Developer relations / community
Open to chats· RemoteRun the GitHub Discussions, write quickstart videos, talk at community events. Half evangelist, half technical writer.
How to apply
Email hi@openbee.ai with the role you're interested in and a few links to things you're proud of (code, designs, posts, deals — whatever's relevant). No cover letter needed; we'd rather read your work.
Don't see a fit but think there should be one? Tell us what you'd build. We've made offers before for roles that didn't exist on this page.