Outcome Engineer

You’re a world-class software engineer who excelled at the “old version” of software development, and are reinventing yourself right here, right now. You see the promise and pitfalls of a world unconstrained by human bandwidth, and are ready to fully embrace the super-powered creation that AI unlocks., * Architect Multi-Agent Systems: Design the orchestration layers that enable multiple specialized agents to collaborate, debate, and execute complex tasks reliably. You will move us from simple prompts to robust, stateful agentic workflows.

• Implement Automated Governance: Create the “guardrails” and policy engines that allow autonomous systems to operate safely at speed. You will build the infrastructure that replaces manual review with programmatic constraints.
• Engineer Context and Memory: Build the semantic infrastructure (knowledge graphs, vector stores) that provides agents with deep, structural understanding of our codebase and business intent. You will solve the “blank slate” problem for autonomous workers.
• Build Rigorous Evaluation Frameworks: Develop the testing harness that defines success. You will move us beyond “vibes” to deterministic validation of agentic outputs using formal specifications and automated metrics.
• Design Self-Healing Loops: Connect observability data directly to agent actions, enabling systems that not only detect failures but autonomously analyze and remediate them.
• Prototype and Deploy: We prove success by shipping. You will rapidly prototype new agentic tools and deploy them to production for both our internal teams and customers. This is a creation role; we learn by building.
• Experiment and Learn: This is a new field. You will be experimenting with new models, new orchestration techniques, and new ways of validating agent behavior every day., We are casting a wide net. While strong software engineering skills are valuable, we believe the best Outcome Engineers might come from diverse backgrounds, that interdisciplinary backgrounds and an embrace of ego-free collaboration is key to inventing the future.
• Software Engineer: You are a coder who is ready to automate your own job. You see code as a liability and outcomes as the asset. You love building products, tools, platforms, and force multipliers.
• AI Researcher: You understand the models at a deep level but want to apply them to messy, real-world production systems. You care about emergent behavior and multi-agent coordination. You have strong opinions about world models.
• Game Engineer: You have experience building complex simulations or games. You understand how to define rules, entities, and validation logic for autonomous agents.
• Product Manager: You are obsessive about products. You excel at translating ambiguous user needs into rigorous deliverables, managing complexity, and unknown unknowns.
• Platform/SRE Engineer: You view infrastructure as a product. You are expert in observability, reliability, and automation. You want to apply o11y to the new world of probabilistic AI systems.
• Designers: You’re not afraid to create with technology. You care deeply about building agentics systems that make more humane products and decisions.
• Agentic Pioneer: Regardless of your title, you have already built your own agents. You’ve hit the limits of frameworks like LangChain or AutoGen and have strong opinions on how to orchestrate reliable reasoning.

• You Must Be a Product Builder: Whether your background is code, design, or leadership, you must have a history of shipping. We don’t just theorize; we deploy. You need to understand the visceral difference between a prototype and a product that users rely on.
• You Must Be an Active Agentic Builder: This isn’t something you read about on Twitter. You built with an agent last week. You’re building with one right now. You know the frustration of a prompt that worked yesterday failing today.
• You Must Love Intense Collaboration: We are all-remote but high-bandwidth. We leave video links open while we eat lunch. Our pets and kids know our coworkers. If you prefer to go dark for three weeks and emerge with a PR, this is not the team for you. We think, debate, and build together, often synchronously.
• You Respect Expertise, But Don’t Gatekeep: We are bringing together radically different disciplines. We value deep expertise, but we value the willingness to share it and empower others even more. No silos.
• You Must Write to Think: In a distributed, asynchronous, fast-moving environment, clarity of thought is demonstrated through clarity of writing. You share bad ideas to get to good ones. You document your experiments, your architectural decisions, and your failures.

Core Tech We Use (and You Will Build)

• Agentic Stack: Large Language Models, Vector Databases, the usual suspects.
• Foundational Stack: Node.js, TypeScript, PostgreSQL, Redis, Kubernetes, AWS.

Onebrief builds collaboration and AI-powered workflow software for military planning and operational coordination.

Military planning is complex by nature, requiring teams to coordinate information, people, and decisions across systems and locations. Onebrief brings planning, collaboration, simulation, and AI into one connected environment, helping teams test strategies, adapt to changing conditions, and make decisions with greater clarity when the stakes are real.

We are a distributed team of builders from military, operational, and technology backgrounds who care deeply about improving how important work gets done. Some team members work remotely, while others work directly alongside customers in operational environments around the world.

Founded in 2019, Onebrief is backed by leading investors including General Catalyst, Battery Ventures, Insight Partners, Sapphire Ventures, and Human Capital. Valued at more than $2 billion, we continue to invest in product innovation, AI capabilities, and team growth.

We are also defining the future of software development. We believe the era of “human bandwidth” as the primary constraint on software delivery is ending. We are building a dedicated team to transition our organization from Software Engineering to Outcome Engineering.