AI Solutions Delivery Lead

Job Description

About ArchitectNow\n

\n

For 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) — the practice areas we invest in most heavily and the work we do day in and day out. Across cloud-native applications, AI, the Power Platform, Dataverse, and the managed cloud services that keep production environments running, our focus has always been getting hard things built, well, and on time.

\n

\n

What has changed is how we build them. We are in the middle of a fast, deliberate move into an AI-first practice. Our engineers use Claude, GitHub Copilot, and a growing stack of internal AI tooling to put their experience to work on harder problems and ship stronger solutions faster than the industry standard. Eighteen years of engineering discipline applied to a new generation of tools — that combination is what our clients hire us for, and it is the era we are building toward.

\n

\n

We are fully remote across 14 states. We are small enough that the work you do is visible to leadership the same week you do it, and selective about who we hire because the team carries real weight from day one. There are no layers between an engineer and the client by design.

\n

\n

The work we do is for real businesses solving real problems. Right now those businesses are asking a harder question than they were two years ago: how do we weave AI into how the work actually gets done, not bolt it on as a demo. That is the work. And that is why this role exists.

The role\n

The job of a delivery manager looks different than it did 18 months ago. We are hiring for the version that comes next.

\n

\n

The AI Solutions Delivery Lead is a new role at ArchitectNow that combines what our Technical Delivery Managers have always done — own client engagements, run agile teams of senior engineers, drive outcomes — with the work of an AI-fluent product manager and business analyst. You will turn client conversations into specifications our development teams can implement, using a Spec-Driven Development (SDD) workflow we have built and continue to refine for AI-augmented teams. You will run delivery for some of our largest engagements. And you will be a major contributor to how we rebuild our SDLC around AI.

\n

If you are already using Claude or Copilot to compress half-day tasks into twenty-minute ones, this is the environment to do that work at scale.

What you will actually do\n

You will own delivery across multiple significant client engagements, typically our most strategic accounts. These are real software projects with real budgets and real deadlines. You will run agile process for each team, drive sprint planning and refinement, and sit in the client conversations that set direction.

\n

\n

You will write a lot of specs — better specs than most people write today, because AI gives you the time to think things through more carefully. You will run scrum for teams of senior engineers who are themselves heavy AI users; they do not need someone who tracks tickets, they need a partner who can engage substantively on an architectural decision and push back on a half-formed user story. You will be on calls with C-level clients walking them through progress and, at times, having the harder conversation about saying no. And you will be looking, constantly, at how we deliver — where AI can take cost out, where it can shorten cycle time, and where a new tool changes what is possible.

\n

Who we are looking for\n

To be clear on scope first: this is not a heads-down software engineering position. Our AI-augmented engineering teams handle the day-to-day code. This is a hybrid product owner, project manager, and business analyst role built for the AI era — someone who engages with multiple clients and runs delivery across multiple concurrent projects, using AI as a force multiplier to operate at that scale without losing depth on any single engagement.

\n

\n

That said, this is still a highly technical role, and a real software development background is a meaningful differentiator. We care less about which tech stacks you have worked in than about whether you have actually been hands-on in software delivery — sitting with stakeholders on requirements, writing code, reviewing pull requests, debugging in production, and shipping things customers depend on. The more of the SDLC you have lived in, and the deeper your involvement at each stage, the more value you will bring to the work on day one.

\n

\n

And one trait matters as much as any of the above: we are looking for someone who communicates clearly, takes real ownership, and follows through on what they commit to. Our clients and partners come back to us, refer us, and stay with us through difficult projects because the people on our teams are people they actually want to work with — communicators who close loops, raise issues early, and do what they said they were going to do. AI is a tool we use heavily; it is not what the relationship is built on. The relationship is built on the people, and we hire for that with the same seriousness we hire for technical skill. This one is non-negotiable.

Required\n

\n

\n
• Delivery management, technical project management, product ownership, or business analysis experience. Consulting or services background strongly preferred.
\n
• Technical fluency to operate alongside senior engineers. You can read code, follow a system diagram, and engage substantively on API design or technical trade-offs. Prior hands-on software experience is the most common path to that fluency, but it is not the only one — what matters is that you can hold your own on a technical conversation.
\n
• Active, daily use of AI tools in your delivery work — Claude Desktop, Claude Code, GitHub Copilot, or comparable. You can walk us through how you use them, what you ask them to do, and where you have learned not to trust them.
\n
• A working command of prompt design and context engineering. You have informed opinions on how to structure a prompt, what context to provide, when to decompose work into steps, and how to evaluate the result. Familiarity with system prompts, agents, skills, and MCP is a strong plus.
\n
• A genuine interest in helping organizations improve through the disciplined application of AI. You treat AI as a craft to develop and teach, not a checkbox to satisfy.
\n
• Practical command of agile and scrum. You have run sprints, owned a backlog, and shipped software in a team-based environment.
\n
• Proven ability to manage multiple client engagements with competing priorities and shifting timelines.
\n
• Excellent written and verbal communication. You write clearly, communicate proactively, and adjust your approach for your audience. Communication is not a bonus skill in this role — it is the role.
\n
• Ownership and follow-through as a defining trait. You close loops, raise issues early, and do what you said you were going to do. Non-negotiable.
\n
• Demonstrated ability to manage up. You bring leadership the context to act, not just the problem.
\n

\n

Bonus\n

\n

\n
• A background in software development. A coder, engineer, or hands-on technical lead who has moved into a product owner, product manager, or delivery role is exactly the profile we are hoping to find. It is not required, but it is a big plus.
\n
• Familiarity with Spec-Driven Development as a practice. GitHub Spec Kit experience is a plus.
\n
• Hands-on time with Azure DevOps and GitHub for backlog management and CI/CD.
\n
• Experience with Microsoft Azure, Power Platform, Dataverse, or Dynamics 365.
\n
• Scrum certifications (CSM, CSPO, SAFe, PSPO).
\n
• A blog, an open-source contribution, a side project, or a Claude skill, MCP, or agent you have built. Anything showing how you think about AI in practice.
\n

\n

The AI stack you will have\n

We treat AI tooling as core infrastructure, not a perk. We invest where the productivity gains are real and equip every delivery lead accordingly. In this role you will have:

\n

\n

\n
• A Claude Max account
\n
• GitHub Copilot
\n
• Our internal library of Claude skills, MCP servers, and delivery agents — and a real opportunity to extend and build new ones
\n
• Microsoft Copilot across the M365 suite
\n
• Time and budget to experiment with whatever new tooling looks promising
\n

\n Our hiring process\n

We have made deliberate changes to how we hire for this role, and we want to be transparent about all of them up front. Every step described below is required for any candidate moving forward in the process. There are no exceptions.

\n

Eligibility and direct hire\n

This is a US-based remote position. All candidates must be legally authorized to work in the United States indefinitely, without current or future sponsorship. We do not sponsor work visas, transfer existing sponsorships, or hire on any basis that would require sponsorship in the foreseeable future. This is also a direct-hire position. We are not partnering with third-party recruiters, staffing firms, contracting agencies, or consultancies on this role. Please apply directly; submissions from third parties will not be considered.

\n

Identity verification\n

Candidates selected to move forward to an interview will be required to complete an identity verification check through Checkr, our third-party verification provider, prior to continuing in the process. The rise of synthetic resumes and AI-assisted candidate impersonation across the industry has made this step necessary, and we ask every candidate to complete it without exception.

\n

Skills assessment\n

Candidates may be asked to complete an online assessment prior to interviewing. The assessment focuses on the capabilities this role actually requires: AI fluency, prompting technique, agentic development, and the ability to apply these tools to real work.

\n

Live technical interview\n

During the technical interview, we may use a comparable shared environment to work through a structured challenge together, with AI tools available and in use. This is designed to mirror the way work actually gets done at ArchitectNow, not to test memorization or trivia.