Creating first table stakes for AI development and then creating what comes next is the most exciting opportunity in product development today. At Onebrief, we’re already building using LLMs and agents to accelerate development and to make military command superhuman.

We are actively hiring for critical infrastructure engineering, software engineering, design, game engine, and product roles, and today we are exploring something new — identifying what it means to be an outcome engineer and mapping that complex and evolving skillset to both senior and early career job openings. So we’ve added two new job openings:

Job requirements in emerging fields

Hunter Walk recently posted

Looking to hire engineers ASAP. Must have 5+ years of Clawdbot experience.

which reminds me of hiring in 2010, when everyone was suddenly looking for 5+ years of iOS experience.

Today, nobody has 5 years of agentic development experience. And, really, nobody has 5 months, because the capability of the tools is moving so quickly. What we do have is a lot of change, a lot of layoffs, and a lot of concerns about what it means to hire engineers early in their careers.

Part of my goal in reframing software engineering into outcome engineering was to create space to explore during this period. Because, junior or senior, what I know is that for passionate infrastructure and product builders, the capacity to build has just increased wildly.

While slop will grow exponentially, our capacity to build tests, o11y, and verification is growing just as quickly. Every developer has the opportunity — and the need — to significantly raise the bar for the quality and predictability of what we deliver to our customers.

To know what we intended and to be able to prove the impact of what we delivered.

To be focused on outcomes. Hence, outcome engineering.

Come join our incredible group of people building the future of both command and engineering.