Principal Architect

POSITION SUMMARY

The Principal Architect is a senior individual contributor and hands-on technical leader responsible for defining and advancing MedPro’s target-state architecture, platform modernization strategy, and cross-product technical direction. This role partners directly with the VP of Engineering, engineering leads, product stakeholders, Data Operations, and IT/Security to move MedPro from a collection of independently built legacy and modern products toward a coherent, scalable platform company.

This role does not manage people or own a separate budget. It leads through technical authority, execution, influence, credibility, and clear decision frameworks. The Principal Architect is expected to design, prototype, and help deliver critical reference implementations while guiding teams toward common patterns, reusable capabilities, and intentional modernization decisions.

A central focus of the role is DataFlow, MedPro’s strategic in-house data platform and shared foundation for acquiring, mastering, matching, exploring, securing, and distributing MedPro data. DataFlow is intended to become the common internal and external interface for data capabilities across MedPro, replacing duplicated patterns and fragmented systems over time through disciplined modernization and incremental migration.

ESSENTIAL DUTIES AND RESPONSIBILITIES

• Define and maintain MedPro’s technical North Star, target-state architecture, and modernization principles in partnership with the VP of Engineering.
• Own the architecture vision for DataFlow as MedPro’s shared data platform foundation, including identity integration, role-based access control, data acquisition, master data management, matching and merging, search, data exploration, standard extracts, outbound data services, APIs, and shared platform capabilities.
• Translate the DataFlow vision into pragmatic architecture patterns, phased migration plans, and reference implementations that engineering teams can adopt incrementally.
• Design and lead strangler-pattern modernization approaches that allow MedPro to replace legacy Oracle/PLSQL, Classic ASP, .NET, and other legacy components without halting product delivery.
• Identify and collapse duplicate functionality, integrations, data flows, workflows, and storage patterns across MCR US, MCR International, MedProID, Data Acquisition, LDD/DLS, DASH, EngagePro, Bulk ID, WebID, AD/outbound data capabilities, and related platforms.
• Establish clean domain boundaries and shared services that allow products to converge where commonality creates leverage while preserving fit-for-purpose components where separation is warranted.
• Design and implement critical systems, prototypes, shared services, and hardest-path code that demonstrate the intended architecture and reduce adoption risk for product engineering teams.
• Partner with technical leads to align product-level decisions with enterprise architecture goals, without creating a heavy approval process or slowing teams unnecessarily.
• Lead lightweight engineering design reviews, architecture decision records, and technical standards that promote velocity with coherence rather than gatekeeping.
• Guide patterns for scalability, reliability, observability, performance, maintainability, security, and supportability across the engineering organization.
• Partner with Product leadership and Product Owners to ensure roadmap decisions account for long-term platform convergence, technical debt reduction, modernization sequencing, and customer impact.
• Collaborate with Data Operations, IT/Security, and shared service owners to clarify boundaries between product engineering, platform capabilities, infrastructure, security, operations, and data stewardship.
• Advance AI-assisted engineering practices and AI-enabled product architecture where they create measurable leverage, while ensuring responsible, secure, and maintainable implementation patterns.
• Serve as a mentor, coach, and force multiplier for engineering leads and senior engineers through design pairing, technical reviews, architecture office hours, and direct delivery collaboration.
• Communicate complex architecture decisions clearly to technical and non-technical stakeholders, including executive audiences when needed.