Skip to main content

OneBrief

Outcome Engineer - Seattle, WA

Seattle, WA (Remote)$200k–$320kfulltimemidAdded today

About this role

Onebrief seeks an Outcome Engineer to build an AI Engineering Platform that moves software development beyond human bandwidth constraints. You'll architect multi-agent systems, implement governance frameworks, and design autonomous workflows that enable rapid, reliable execution—shifting from traditional backlogs to agentic product development.

What you'll do

  • Design orchestration layers for multi-agent collaboration and complex task execution
  • Build governance and policy engines enabling autonomous systems to operate safely
  • Engineer semantic infrastructure (knowledge graphs, vector stores) for agent context and memory
  • Develop rigorous evaluation frameworks with formal specifications and automated metrics
  • Connect observability to agent actions for self-healing autonomous systems
  • Rapidly prototype and deploy agentic tools for internal teams and customers

What they're looking for

  • Software engineering and systems design
  • Multi-agent AI systems and orchestration
  • Knowledge graphs and vector databases
  • Testing frameworks and formal validation
  • Production deployment and DevOps
  • Observable systems and monitoring
  • AI model understanding and applications
  • Rapid prototyping and experimentation
Apply with Autofill

Opens the application — the Jobs AI extension fills it for you. Set up autofill

Opens the official application on the employer’s site. No login required.

OneBrief

OneBrief builds AtomEngine, an AI-powered cloud-based simulation platform designed for military training and operational exercises in classified and live environments. The company is hiring Software Development Engineers in Test, Gameplay Engineers, and Customer Success Engineers to support quality assurance, platform development, and direct customer deployment and support.

View all jobs at OneBrief

Likely interview questions

  • Describe a complex system you've designed—how would you evolve it to use autonomous agents instead of manual orchestration?
  • How do you think about testing and validating behavior in multi-agent systems where outcomes aren't deterministic?