Outcome Engineer - Salt Lake City, UT
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: navigation, cookie, legal, EEO, etc. The posting includes "Notice to Third Party Recruitment Agencies" which is boilerplate; we should remove that. Also "Consequential Work. Dedicated People. About Onebrief ..." includes company description; that might be considered part of About the role? The instruction: "About The Role" heading we should use for section heading. The preceding company description could be considered part of About the role? But we need to preserve all substantive information. The company description is substantive about Onebrief. Should we include it? It is not under a heading but we can include as prose under About the role section. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should have an About the role
and then include the company description and role description as prose.
Then Responsibilities: from "What You'll Do". That's a list of bullet points (each line starts with a bold phrase?). We need to convert to - . Preserve all detail.
Then Requirements/Qualifications/Skills: The posting has "What We Look For" with categories: Software Engineer, AI Researcher, Game Engineer, Product Manager, Platform/SRE Engineer, Designers, Agentic Pioneer. Then "The Non-Negotiables: How We Work" with bullet points. Also "Core Tech We Use (and You Will Build)" with list.
We need to decide how to split into sections: Requirements, Qualifications, Skills. The instruction says prefer a few substantive sections over many thin ones. Could combine Requirements and Qualifications into one section? But we have headings list; we can include sections that have real content. We could have:
- About the role
- Responsibilities
- Qualifications (maybe combine What We Look For + Non-Negotiables + Core Tech)
- Skills (maybe not needed if we put tech in Qualifications). But we need to avoid thin sections. Could make one section "Requirements & Qualifications" but we must use exact heading names from list? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use those for section headings. Likely we should only use those exact headings. So we need to map content to those headings.
Thus we need to decide which headings have content.
- About the role: yes.
- Responsibilities: yes (What You'll Do).
- Requirements: maybe the Non-Negotiables (must be a product builder, active agentic builder, etc.) could be Requirements.
- Qualifications: maybe the "What We Look For" categories (Software Engineer, AI Researcher, etc.) could be Qualifications.
- Skills: maybe Core Tech We Use (Agentic Stack, Foundational Stack) could be Skills.
- Benefits, Pay, Schedule: none -> omit.
We must not create sections with filler. So we will include About the role, Responsibilities, Requirements, Qualifications, Skills.
Now we need to format.
Inside each section, we need to use
for prose,
- for lists.
For About the role: we have company description paragraph(s) plus role description paragraph "You’re a world-class software engineer..." etc. We'll combine into prose paragraphs. Could split into multiple
but okay.
We need to preserve all substantive information: ensure we don't lose any details.
Let's extract content.
Company description:
"Consequential Work. Dedicated People. About Onebrief 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."
That's a lot. We'll keep as prose.
Then role description:
"About The Role 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. As an Outcome Engineer at Onebrief, you’ll join the team inventing our AI Engineering Platform. This is neither just prompt building nor model development. You will be part of a team building the factory that builds the software. You will help move us from a world of managed backlogs to a world of infinite execution, creating the foundation of what product development becomes in an agentic world. We are looking for pioneers."
We'll combine into paragraphs.
Now Responsibilities: "What You'll Do" list:
- 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 need to keep each bullet as
- .
Now Qualifications: "What We Look For" includes categories with descriptions. We'll need to preserve each bullet? It's a list of roles with descriptions. Could treat each category as
- with its description inside. Let's extract:
"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."
Then bullet-like sections:
- 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.
We'll keep as
- each.
Now Requirements: "The Non-Negotiables: How We Work" includes:
- 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.
We'll keep as
- .
Now Skills: "Core Tech We Use (and You Will Build)" includes:
- Agentic Stack: Large Language Models, Vector Databases, the usual suspects.
- Foundational Stack: Node.js, TypeScript, PostgreSQL, Redis, Kubernetes, AWS.
We could make each as
- . Or we could keep as prose. Better as list.
Now we need to output HTML fragment only.
We'll structure:
About the role
...company description...
...role description...
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- ...
...
Skills
- ...
...
Make sure no extra whitespace? It's fine.
Now ensure we didn't include any boilerplate like "Notice to Third Party Recruitment Agencies". Remove.
Also remove duplicated lines: none.
Check for any mention of Pay/Ben
for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: navigation, cookie, legal, EEO, etc. The posting includes "Notice to Third Party Recruitment Agencies" which is boilerplate; we should remove that. Also "Consequential Work. Dedicated People. About Onebrief ..." includes company description; that might be considered part of About the role? The instruction: "About The Role" heading we should use for section heading. The preceding company description could be considered part of About the role? But we need to preserve all substantive information. The company description is substantive about Onebrief. Should we include it? It is not under a heading but we can include as prose under About the role section. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should have an About the role
and then include the company description and role description as prose.
Then Responsibilities: from "What You'll Do". That's a list of bullet points (each line starts with a bold phrase?). We need to convert to - . Preserve all detail.
Then Requirements/Qualifications/Skills: The posting has "What We Look For" with categories: Software Engineer, AI Researcher, Game Engineer, Product Manager, Platform/SRE Engineer, Designers, Agentic Pioneer. Then "The Non-Negotiables: How We Work" with bullet points. Also "Core Tech We Use (and You Will Build)" with list.
We need to decide how to split into sections: Requirements, Qualifications, Skills. The instruction says prefer a few substantive sections over many thin ones. Could combine Requirements and Qualifications into one section? But we have headings list; we can include sections that have real content. We could have:
- About the role
- Responsibilities
- Qualifications (maybe combine What We Look For + Non-Negotiables + Core Tech)
- Skills (maybe not needed if we put tech in Qualifications). But we need to avoid thin sections. Could make one section "Requirements & Qualifications" but we must use exact heading names from list? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use those for section headings. Likely we should only use those exact headings. So we need to map content to those headings.
Thus we need to decide which headings have content.
- About the role: yes.
- Responsibilities: yes (What You'll Do).
- Requirements: maybe the Non-Negotiables (must be a product builder, active agentic builder, etc.) could be Requirements.
- Qualifications: maybe the "What We Look For" categories (Software Engineer, AI Researcher, etc.) could be Qualifications.
- Skills: maybe Core Tech We Use (Agentic Stack, Foundational Stack) could be Skills.
- Benefits, Pay, Schedule: none -> omit.
We must not create sections with filler. So we will include About the role, Responsibilities, Requirements, Qualifications, Skills.
Now we need to format.
Inside each section, we need to use
for prose,
- for lists.
For About the role: we have company description paragraph(s) plus role description paragraph "You’re a world-class software engineer..." etc. We'll combine into prose paragraphs. Could split into multiple
but okay.
We need to preserve all substantive information: ensure we don't lose any details.
Let's extract content.
Company description:
"Consequential Work. Dedicated People. About Onebrief 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."
That's a lot. We'll keep as prose.
Then role description:
"About The Role 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. As an Outcome Engineer at Onebrief, you’ll join the team inventing our AI Engineering Platform. This is neither just prompt building nor model development. You will be part of a team building the factory that builds the software. You will help move us from a world of managed backlogs to a world of infinite execution, creating the foundation of what product development becomes in an agentic world. We are looking for pioneers."
We'll combine into paragraphs.
Now Responsibilities: "What You'll Do" list:
- 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 need to keep each bullet as
- .
Now Qualifications: "What We Look For" includes categories with descriptions. We'll need to preserve each bullet? It's a list of roles with descriptions. Could treat each category as
- with its description inside. Let's extract:
"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."
Then bullet-like sections:
- 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.
We'll keep as
- each.
Now Requirements: "The Non-Negotiables: How We Work" includes:
- 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.
We'll keep as
- .
Now Skills: "Core Tech We Use (and You Will Build)" includes:
- Agentic Stack: Large Language Models, Vector Databases, the usual suspects.
- Foundational Stack: Node.js, TypeScript, PostgreSQL, Redis, Kubernetes, AWS.
We could make each as
- . Or we could keep as prose. Better as list.
Now we need to output HTML fragment only.
We'll structure:
About the role
...company description...
...role description...
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- ...
...
Skills
- ...
...
Make sure no extra whitespace? It's fine.
Now ensure we didn't include any boilerplate like "Notice to Third Party Recruitment Agencies". Remove.
Also remove duplicated lines: none.
Check for any mention of Pay/Ben
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use those for section headings. Likely we should only use those exact headings. So we need to map content to those headings. Thus we need to decide which headings have content. - About the role: yes. - Responsibilities: yes (What You'll Do). - Requirements: maybe the Non-Negotiables (must be a product builder, active agentic builder, etc.) could be Requirements. - Qualifications: maybe the "What We Look For" categories (Software Engineer, AI Researcher, etc.) could be Qualifications. - Skills: maybe Core Tech We Use (Agentic Stack, Foundational Stack) could be Skills. - Benefits, Pay, Schedule: none -> omit. We must not create sections with filler. So we will include About the role, Responsibilities, Requirements, Qualifications, Skills. Now we need to format. Inside each section, we need to use
for prose,
- for lists.
For About the role: we have company description paragraph(s) plus role description paragraph "You’re a world-class software engineer..." etc. We'll combine into prose paragraphs. Could split into multiple
but okay. We need to preserve all substantive information: ensure we don't lose any details. Let's extract content. Company description: "Consequential Work. Dedicated People. About Onebrief 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." That's a lot. We'll keep as prose. Then role description: "About The Role 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. As an Outcome Engineer at Onebrief, you’ll join the team inventing our AI Engineering Platform. This is neither just prompt building nor model development. You will be part of a team building the factory that builds the software. You will help move us from a world of managed backlogs to a world of infinite execution, creating the foundation of what product development becomes in an agentic world. We are looking for pioneers." We'll combine into paragraphs. Now Responsibilities: "What You'll Do" list: - 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 need to keep each bullet as
- . Now Qualifications: "What We Look For" includes categories with descriptions. We'll need to preserve each bullet? It's a list of roles with descriptions. Could treat each category as
- with its description inside. Let's extract: "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." Then bullet-like sections: - 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. We'll keep as
- each. Now Requirements: "The Non-Negotiables: How We Work" includes: - 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. We'll keep as
- . Now Skills: "Core Tech We Use (and You Will Build)" includes: - Agentic Stack: Large Language Models, Vector Databases, the usual suspects. - Foundational Stack: Node.js, TypeScript, PostgreSQL, Redis, Kubernetes, AWS. We could make each as
- . Or we could keep as prose. Better as list.
Now we need to output HTML fragment only.
We'll structure:
About the role
...company description...
...role description...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Skills
- ... ...