> Markdown version of [/jobs/ext/2720863-software-engineer-ai-native-full-stack](https://www.wearedevelopers.com/jobs/ext/2720863-software-engineer-ai-native-full-stack). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Software Engineer - AI-Native Full Stack - **Company:** YOLO BOLO AI, LLC - **Location:** Salt Lake City, UT, United States - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, Business Logic, Cursor (Graphical User Interface Elements), Software Debugging, Fault Tolerance, Code Inspection - **Published:** September 4, 2026 - **Apply:** https://startup.jobs/software-engineer-ai-native-full-stack-bolo-ai-8128617 ## About the Role 7+ years of engineering experience, applied at a higher altitude. You need years of building and debugging production systems. Not because you'll write every line, but because you can't design a harness that catches real failures, write a spec that anticipates edge cases, or diagnose a broken feature across the full stack without that foundation. The depth serves the abstraction. Systems thinking over code fluency. How components interact. Where failures cascade. What breaks when requirements change. What to anticipate before it happens. This is what agents are worst at and what matters most. An agent-driven workflow. You already direct AI agents (Claude Code, Codex, Cursor, or similar) to handle implementation while you focus on architecture, specification, and validation. Or you have the engineering judgment to make that transition and the motivation to do it now. Experience building the infrastructure around agents. CI enforcement, scenario-based testing, documentation systems agents can consume, structured knowledge bases - you've built some of this, or you have specific ideas about how and why. Comfort making decisions with incomplete information. Startup. Requirements shift. The right approach isn't always obvious. You move forward, and you know when to ask versus when to make a call. Direct communication. You give and receive honest feedback. You can disagree with a decision, say so clearly, and still commit to the outcome. We care about getting it right more than being right. Enthusiasm for a field that reinvents itself quarterly. Tools change. Workflows get replaced. Best practices from three months ago become obsolete. You're energized by that. You see this as the most interesting period in the history of software. ## Description * Specifications. You write behavioral specs, architectural constraints, and feature requirements that agents implement against. When agent output misses the mark, you tighten the spec. Not by adding more words, but by being more precise about what "correct" means. This requires understanding the system deeply enough to define its behavior at every layer. * Harness. You build and maintain the infrastructure that keeps agents producing reliable code. Structural tests that enforce architectural boundaries. Linting rules where every failure message teaches the agent what went wrong. CI gates that reject drift. Structured knowledge bases agents can navigate. The principle: every class of agent mistake gets a mechanical fix so it never recurs. * Validation. Agents write the code. Agents write the tests. You verify that features work from the user's perspective, under real deployment conditions, against edge cases that matter in production. You define scenarios and acceptance criteria. You build the end-to-end checks, behavioral verification, and automation that make this trustworthy at scale. When something breaks, your job is diagnosing whether the failure is in the spec, the harness, or the agent's implementation, and fixing the right layer. * Architecture and operations. Our systems run across cloud providers and on-premises environments. You design modular abstractions, clean interfaces where deployment targets don't leak into application logic. You own production systems used by energy companies in regulated environments where failures have real consequences. Reliability, observability, and graceful degradation matter here. ## Related Videos - [The AI-Native Engineering Org: What’s Real, What’s Hype, What’s Next](https://www.wearedevelopers.com/videos/100004-the-ai-native-engineering-org-what-s-real-what-s-hype-what-s-next) - [The Algorithm That Nearly Killed Me: When Testing Isn't Enough](https://www.wearedevelopers.com/videos/2110-the-algorithm-that-nearly-killed-me-when-testing-isn-t-enough) - [System Resilience: Surviving the Software Storm](https://www.wearedevelopers.com/videos/874-system-resilience-surviving-the-software-storm) - [Automated Code Quality Checks with Custom SonarQube Rules](https://www.wearedevelopers.com/videos/428-automated-code-quality-checks-with-custom-sonarqube-rules) - [Are We All Prompt Engineers? How AI Changed What It Means to Build Software](https://www.wearedevelopers.com/videos/1980-are-we-all-prompt-engineers-how-ai-changed-what-it-means-to-build-software) - [Where we're going we don't need JavaScript - Programming with Type Annotations](https://www.wearedevelopers.com/videos/455-where-we-re-going-we-don-t-need-javascript-programming-with-type-annotations) ## Related Articles - [Never delegate the understanding](https://www.wearedevelopers.com/magazine/749-never-delegate-the-understanding) - [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift) - [MLOps And AI Driven Development](https://www.wearedevelopers.com/magazine/82-mlops-and-ai-driven-development) - [What is Software Engineering in the Age of AI?](https://www.wearedevelopers.com/magazine/640-what-is-software-engineering-in-the-age-of-ai) - [How to Become an AI Engineer](https://www.wearedevelopers.com/magazine/331-how-to-become-an-ai-engineer) - [What is Agentic Programming and Why Should Developers Care?](https://www.wearedevelopers.com/magazine/625-what-is-agentic-programming-and-why-should-developers-care)