> Markdown version of [/jobs/ext/4759725-software-engineer-4-ai-native](https://www.wearedevelopers.com/jobs/ext/4759725-software-engineer-4-ai-native). 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 4 - AI Native - **Company:** Granicus, LLC - **Location:** Saint Paul, MN, United States (Remote available) - **Experience:** Expert - **Salary:** $180,000 - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, Automation of Tests, Code Review, Data Structures, Web Content Accessibility Guidelines, AI Coding Agents - **Published:** November 17, 2026 - **Apply:** https://www.juju.com/job/21_01a1df66-98b8-7a54-b6fd-00df95027080 ## About the Role * Strong engineering fundamentals. Data structures, systems design, and testing, with the ability to read unfamiliar code quickly and assess it accurately. Agents amplify engineering judgment; they do not substitute for it. * A record of shipping production software you owned the quality of, including responsibility for diagnosis and remediation when it failed. * Hands-on experience directing coding agents on production work, including their failure modes and the practice of reviewing agent-generated code critically rather than approving it by default. * Demonstrated code-review competence. You identify defects that automated tests do not catch, provide actionable feedback, and maintain a high bar without becoming a bottleneck. * High autonomy. You advance work without step-by-step direction and escalate issues proactively. Preferred * High-assurance or regulated experience. Shipping within FedRAMP, defense, financial services, healthcare, or another NIST 800-53 / SOC 2 / HIPAA-bound environment. * Depth in evaluation authoring or test-first development within a rigorous engineering culture. * Full-stack range, sufficient to review front-end and back-end agent output with equal confidence. * Public-sector or govtech experience and familiarity with the relevant end users. Indicators of a strong fit * You deliver more effectively by directing multiple agents than by authoring code directly, while retaining a precise understanding of the intended implementation. * You regard rigorous code review as a core engineering competency. * You prefer to establish quality through evaluation suites rather than through discussion. * You treat the agent array as leverage and reliably identify when its output is incorrect. * You want to contribute to how engineering is practiced here, not only to apply new tooling. ## Description Direct the agent array on production workstreams - decompose problems into tasks suitable for agent execution, dispatch them, and integrate the output into shipped software. * Review agent-generated pull requests at volume and at depth - identify correctness, security, and accessibility defects that automated tests do not catch, while maintaining review throughput and a consistent quality bar. * Author evaluation suites that make quality measurable - define criteria under which the pipeline validates correctness rather than relying on subjective assessment. Eval-driven development is your standard practice. * Own quality end to end - correctness, performance, security posture, and WCAG accessibility of the software your team ships, irrespective of which component or agent produced the initial implementation. * Advance workstreams along the autonomy ladder on the basis of evidence - move work from supervised to autonomous execution when measured reliability supports it, and revert promptly when it does not. * Strengthen the development lifecycle itself - identify where patterns, prompts, or pipeline components degrade at volume and work with the lead architect to remediate them. * Maintain agent operations within the security boundary - branch-only execution, vaulted credentials, sandboxed actions, and in-VPC inference. Throughput does not justify exceptions. * OWNERSHIP FROM DAY ONE + An active workstream directed through the agent array + Agent pull-request review as a core, high-signal responsibility + Evaluation suites authored and owned for your team's deliverables + End-to-end quality ownership within the FedRAMP-authorized environment * * SCOPE YOU WILL GROW INTO + Higher autonomy ratios substantiated by reliability data + Reusable prompt and evaluation patterns adopted by other engineers + Contribution to the lifecycle standards as a co-author, not only a user + Mentorship of engineers transitioning to agent-directed delivery