Agentic Software Engineer (.NET, Azure, Full-Stack)
architectnowSacramento, CA
$120,000 to $150,000
Apply now (opens in a new tab)Agentic Software Engineer (.NET, Azure, Full-Stack)
L6
architectnowSacramento, CAtoday
$120,000 to $150,000
ArchitectNow | Remote (US) | $120,000 to $150,000 base + benefits
About this role:
ArchitectNow builds software through a spec driven, agentic process. Every feature begins as a specification with defined acceptance criteria and architectural constraints; AI agents generate most of the code from it, and the developer who owns the specification reviews, tests, and delivers the result. The primary output of this role is requirements, specifications, and architecture rather than hand-written code. This approach depends on real engineering depth. Several years of delivering production .NET and Angular, React, or Blazor applications on Azure are required, because that experience is what makes specifications implementable, architecture sound, and review of generated code reliable. Candidates should already be working this way in production. We are not able to train for agentic, spec driven development in this role. This practice is further along at ArchitectNow than at most organizations. Every developer on our team works this way today: spec driven development with agentic implementation is the standard on every project, not a pilot. It is also still evolving, here and across the industry, and we learn, optimize, and pivot quickly to keep the quality of what we deliver extremely high. We are looking for someone who wants to work at the leading edge of software development and to help shape how we do it: evaluating new tools as they arrive, improving our spec templates, skills, and agents, and contributing to the processes the rest of the team adopts.
About Architect:
NowFor 18 years, ArchitectNow has helped businesses ship software that does the work. We are a Microsoft Solutions Partner with active designations in Digital & App Innovation (Azure), Data & AI (Azure), and Infrastructure (Azure). Across cloud-native applications, AI, data platforms, the Power Platform, and the managed cloud services that keep production running, our focus has always been getting hard things built, well, and on time. What has changed is how we build. We have moved our delivery practice to spec driven development (currently GitHub Spec Kit) and agentic implementation. Our team standardizes on Claude Code, but the skill we hire for is agentic development itself, whatever framework or model you have practiced it with. Our engineers spend their time on requirements, specifications, architecture, review, and client outcomes, and let agents do the typing. The work itself is varied: polished, UI-heavy web applications; agents and AI features built into client systems; and data and AI platform projects on Microsoft Fabric, Purview, and AI Foundry. We are fully remote across 14 states, small enough that your work is visible to leadership the same week you do it, and there are no layers between an engineer and the client by design. How we build Specifications drive everything. You own the spec and the architecture for the features you deliver, coding agents build from them, and you review every line that comes back, judge whether the tests prove the spec, and ship to Azure. We use GitHub Spec Kit and Claude Code today, and the practice is still evolving as the tools do. You are responsible for whether the result is correct, secure, maintainable, and what the client needed, regardless of which agent wrote it.
The role:
You will deliver a mix of three kinds of work, all spec driven and agent built. Application and UI work. Line-of-business and customer-facing web applications where the front end matters: component architecture, state management, accessibility, responsive layouts, and the design patterns that make an Angular, React, or Blazor application maintainable at scale. You specify these patterns and hold the agent to them. Agents and MCP servers. Agentic workflows, AI capabilities, and the MCP servers that expose client systems and data to them, built with Azure OpenAI, Microsoft AI Foundry, Semantic Kernel, and Microsoft Agent Framework: retrieval over client data, tool calling, structured outputs, multi-step agents, evaluation, and the human-in-the-loop controls that make them safe to ship. Data and AI platform projects. Heavy data and AI engagements on Microsoft Fabric (lakehouse, pipelines, notebooks, semantic models), Microsoft Purview (governance, lineage, classification), and AI Foundry, where the application is one part of a larger platform and the spec has to cover data architecture, governance, and integration, not just screens and APIs. Most of our code is still C# and TypeScript; Python shows up increasingly on the data analytics side of these projects, which run on Fabric or Databricks depending on the client. As an Agentic Software Engineer you sit on a delivery pod with a Tech Lead, a Delivery Lead, and two or three other developers, delivering .NET and Angular, React, or Blazor applications on Azure. The shape of the work varies. Some engagements are long-term partnerships with a single client where you know the system and the stakeholders well; at other times you will balance a few simultaneous deliverables across clients, along with support and enhancement requests on applications we have already shipped. Managing that mix within a week, and being clear with your Delivery Lead about what is on your plate, is part of the role. Your value is not typing speed. It is the quality of your specs and architecture, the sharpness of your review, and your judgment about when the agent is right, when it is wrong, and when to throw its output away. Who we are looking for This role writes little code directly, but it is not a hands-off role. You will spec, direct, review, test, and ship software every week, and the quality of what ships is yours. We care less about years with a particular framework and more about whether you have shipped production software through a spec driven, agentic workflow and can show us how. The specific agent matters less than the practice: Claude Code, OpenAI Codex, GitHub Copilot coding agent, Cursor, or another agentic tool all count, provided you have used it to build real software from specifications, not just for autocomplete. Required Hands-on production experience with spec driven, agentic development: writing specifications that a coding agent implements, and delivering real features that way. GitHub Spec Kit experience is ideal; a comparable spec driven approach counts. You can show us a real example An agentic coding tool as your primary daily development tool. Claude Code, OpenAI Codex, GitHub Copilot coding agent or CLI, Cursor agent mode, or comparable, used to run work end to end rather than for inline suggestions. You can explain how you direct it, how you check its output, and where you have learned not to trust it. Our team works in Claude Code, so direct experience with it is a plus but not a requirement 4+ years of professional software development building and shipping production web applications. This is a hard requirement regardless of agentic experience Strong C# and .NET, including ASP.NET Core and designing and consuming REST APIsProficiency with Angular or React with TypeScript, or Blazor, including the architecture and design patterns of a large front end Solid SQL and relational data modeling Experience designing, deploying, and running cloud-native applications on Azure, or another major cloud with a willingness to go deep on AzureAgent-assisted automated testing as a normal part of how you build, and the judgment to tell adequate coverage from theater Git, pull requests, and critical code review of agent-generated diffs as everyday practice Experience on an agile team working in sprints Consulting, agency, or equivalent client-facing experience: working directly with client stakeholders to shape requirements, run working sessions, present and demo your work, and handle the conversations when priorities or scope change Clear, structured written communication. Your specifications, plans, and review notes are read by agents, teammates, and clients, and the quality of that writing is the quality of the work Strong collaboration habits on a delivery team: pairing with a Tech Lead on architecture, keeping a Delivery Lead informed, reviewing teammates' work constructively, and asking for help early Ownership and follow-through. Non-negotiable
Our hiring process:
This is a US-based remote, direct-hire position. Candidates must be authorized to work in the United States without current or future sponsorship, and we do not work with third-party recruiters, staffing firms, or corp-to-corp arrangements.
Resume review. We review every submission against the requirements of the role.
Pre-interview screening exam. A real-world use case completed in CoderPad using spec driven development, with roughly one to two hours of commitment.
Identity verification. A brief online check to confirm your identity, completed after the screening exam.
Virtual interviews. Several rounds with members of our delivery team and management.
Background check. A full federal and all-50-state background check is required after offer acceptance and before hire.
How to apply:
Submit your resume with a short note describing one feature you delivered end to end using a spec driven, agentic workflow: which tools you used, what the spec covered, what the agent got wrong, and what you changed. Applications that do not address this will not be reviewed.
Compensation and benefits: Base salary $120,000 to $150,000, depending on experience.
Benefits include:
401(k), dental insurance, flexible spending account, health insurance, health savings account, paid time off, parental leave, retirement plan, and vision insurance. Work location. Remote (US)
Apply now (opens in a new tab)
Level
LeadL6
Salary
$120,000 to $150,000
Location
Sacramento, CA
Occupation
Software Developers
Industry
Custom Computer Programming Services
Posted
today
To get sharper similar jobs, create your profile using the link below.