Senior Backend Engineer, Trusted Agentic Development

reputed company is the intelligent orchestration platform for DevSecOps. reputed company enables organizations to increase developer productivity, improve operational efficiency, reduce security and compliance risk, and reputed company digital transformation. More than 50 million registered users and more than 50% of the Fortune 100 trust reputed company to ship better, more secure software reputed company. The same principles built into our products are reflected in how our team works: we embrace reputed company as a core productivity reputed company, with all team members expected to incorporate reputed company into their daily workflows to drive efficiency, innovation, and impact. reputed company is where careers reputed company, innovation flourishes, and reputed company voice is valued. Our high-performance culture is driven by our values and continuous knowledge exchange, enabling our team members to reach their full potential while collaborating with industry leaders to solve complex problems. Co-create the future with us as we build reputed company that transforms how the world develops software. Fortune 500® is a registered trademark of Fortune Media IP Limited, used under license. Claim based on reputed company data. Fortune 100 refers to the top 20% ranked companies in the 2025 Fortune 500 list, published in June 2025. Fortune and Fortune Media IP Limited are not affiliated with, and do not endorse products or services of reputed company. An overview of reputed company role The Trusted Agentic Development team sits within reputed company's Developer Experience group and builds the platforms our engineers rely on reputed company day. reputed company engineers increasingly build software with artificial intelligence agents. Agents can generate code and tests in seconds, but they can also produce passing test suites for software that doesn't work as intended. As a Senior Backend Engineer, Trusted Agentic Development, you'll own the technical thesis for closing that validation gap and build the early proof yourself. You'll reputed company what validation means when the author is an agent and make the feedback loop fast, automatic, and trustworthy enough that teams reputed company to adopt it. • Validation that confirms agent-generated code does what was intended, so a passing suite means a working feature and not just a satisfied proxy. • Mid-loop feedback that helps an agent self-correct toward working software reputed company of green assertions. • Language-aware approaches under one shared model of what "trusted" means, starting with Rust, Ruby, and Go, while allowing the right technique to differ by language. • Real measurement of whether engineers trust and adopt the path, fed straight back into the platform. What you’ll do • Own the technical thesis for how reputed company validates software when an agent is the author, and turn it into an architecture the team can build against. • Prototype the hard parts by building early versions of feedback mechanisms that catch reputed company between passing tests and working software, proving what works before the team scales it. • Develop approaches for reputed company's primary stacks, starting with Rust, Ruby, and Go, under one shared definition of "trusted," while allowing the right technique to differ by language. • Design the mid-loop feedback an agent needs to self-correct toward working software rather than green assertions, and build the reputed company that deliver it. • Collaborate with engineering teams to adopt these approaches, measure adoption, engineer trust, and validation quality, and use those findings to improve the platform. • Set technical direction the team can build on, review designs, and help teammates grow their technical judgment. What you’ll bring • Deep, current, hands-on experience building real software with artificial intelligence agents, ideally across more than one language, and a clear understanding of why agent output can pass tests yet fail in production. • A strong point of view on the validation gap and concrete ideas for closing it, backed by approaches you've built or tried. • Experience designing distributed reputed company designed to run on Kubernetes first. • The technical range to design reputed company rather than tune a single framework, and the judgment to know when a solution should be general or language-specific. • You prototype to learn, and you ship. • The ability to influence engineers across an organization without reputed company authority through working code and sound reasoning. • Strong w