Architect / Consult

Classification: Contract

Contract Length: 6 Months, likely to extend or convert FTE

Position Summary

The Architect – Consulting Level will be part of the team in Nashville, TN . The API / MCP Architect will work with Enterprise Architecture, integration teams, application teams, product owners, and Converge platform stakeholders to review existing APIs, access patterns, and tooling needs, then design and build solutions that align to the Converge Enterprise Semantic API strategy. This role will support the migration of existing APIs into the Converge Enterprise Semantic API suite through remediation, consolidation, facading, adapter patterns, or phased retirement. The role will also design and develop Model Context Protocol capabilities, including MCPs that expose Converge semantic APIs to AI-enabled consumers and MCPs that front development, operational, or platform tooling.

This is a hands‑on architecture and engineering role, expected to be approximately 50% API/MCP review and design and 50% coding, implementation, automation, and prototyping. The ideal candidate has strong experience with well‑formed REST API design, OpenAPI specifications, API modernization, multi‑stage migration planning, Python development, and emerging MCP design patterns.

Responsibilities

• Review existing APIs, integrations, and data access patterns to determine fit with the Converge Enterprise Semantic API suite.
• Recommend migration approaches, including API remediation, consolidation, facading, adapter development, replacement, or phased retirement.
• Design standards‑based REST APIs using OpenAPI and enterprise API design best practices.
• Design and develop MCP servers/tools that expose Converge semantic APIs safely and consistently to AI‑enabled consumers.
• Design and develop MCPs that front development, platform, operational, or governance tooling where MCP provides a practical interface for automation or assisted workflows.
• Ensure MCP implementations rely on stable, governed API or tooling interfaces rather than embedding source‑system complexity directly into the MCP layer.
• Develop multi‑stage implementation plans, build plans, and transition roadmaps for moving existing APIs and tooling interfaces toward Converge‑aligned patterns.
• Partner with architects, analysts, developers, application teams, and platform teams to define reusable API contracts, MCP tools, schemas, prompts, and operational patterns.
• Support semantic alignment of API resources, identifiers, relationships, request/response structures, tool inputs/outputs, and domain concepts.
• Build, modify, or prototype API façade, adapter, validation, testing, automation, and MCP components using Python.
• Produce clear documentation, including API specifications, MCP tool definitions, examples, design decisions, migration recommendations, and onboarding materials.
• Identify technical debt, design inconsistencies, security gaps, reuse opportunities, and governance concerns across existing APIs, MCPs, and tooling interfaces.

Requirements

• 10+ years of hands‑on Python development experience.
• 10+ years of backend and middleware development experience
• Strong experience designing REST APIs and documenting them with OpenAPI.
• Experience evaluating existing APIs and defining phased modernization or migration strategies.
• Experience with façade, adapter, orchestration, remediation, and API consolidation patterns.
• Familiarity with MCP concepts, including tools, schemas, server design, and safe exposure of governed capabilities to AI‑enabled clients.
• Ability to develop practical implementation plans that balance architecture standards with delivery needs.
• Strong written communication skills for documenting designs, build plans, migration options, and technical recommendations.
• Ability to work across architecture, engineering, product, operations, and application teams with limited supervision.
• Experience with enterprise API platforms, API gateways, Apigee, OAuth/OIDC, policy enforcement, and runtime governance.
• Experience with semantic API design, canonical models, ontology‑informed design, or domain‑driven API design.
• Experience building MCPs over enterprise APIs, developer tooling, operational tooling, or platform automation interfaces.
• Healthcare, data access, interoperability, or enterprise integration experience.
• Experience supporting reusable enterprise API or AI‑enablement platforms.