Chief Agentic Systems Architect
Summary
Architect who transforms a 10+ year legacy codebase into an agent-operable architecture: decomposing monoliths via the Strangler Pattern, building MCP servers and agent context layers, and governing AI-generated pull requests. Core stack: TypeScript, .NET, Node.js with LLM/MCP tooling.
Our client is looking for a Chief Agentic Systems Architect to transform a 10+ year legacy codebase into a high‑velocity, agent‑operable architecture.
This role sits at the intersection of software architecture, AI‑agent orchestration, and engineering governance. You will design system patterns, MCP interfaces, and cognitive context layers that allow LLMs and autonomous agents to safely refactor, test, and ship production code with minimal human intervention.
Responsibilities:
Decompose legacy monoliths into agent‑readable, modular systems with strict boundaries and single responsibility
Lead incremental modernization using the Strangler Pattern, wrapping legacy logic in modern, contract‑driven interfaces
Architect and maintain the agent context layer: standardized Skills, Rules, and Commands for AI‑driven engineering workflows
Build and operate Model Context Protocol (MCP) servers exposing legacy APIs, services, and databases as typed, secure, AI‑consumable tools
Own contract‑first API design as the primary interface between human intent and autonomous agent execution
Act as architectural gatekeeper for AI‑generated pull requests, ensuring scalability, security, and long‑term maintainability
Mandate test‑driven development (TDD) and characterization testing to preserve legacy behavior during refactoring
Monitor and optimize agentic reasoning loops to balance cost, speed, and architectural integrity
Requirements:
15+ years in software architecture, platform engineering, or technical leadership
Deep hands‑on expertise with TypeScript, .NET, and Node.js
Proven experience modernizing large, undocumented legacy systems
Strong background in API design, distributed systems, and modular architectures
Practical experience with agentic development, MCP, LLM tooling, or AI‑assisted engineering
Bias toward clean code, deterministic systems, and production‑grade AI
Availability to work until 2 pm - 3pm US EST
Will be a plus:
Experience with remote‑first or globally distributed teams
Background in SaaS transformations, scale‑ups, or PE‑backed environments
Comfort operating in high‑ambiguity, high‑ownership settings
Why this role matters:
You are not adding AI features.
You are designing the architectural substrate that allows AI to safely build software at scale.
This is a career‑defining role for architects shaping how autonomous systems write, change, and govern production code.