Principal Architect

POSITION SUMMARY

• The Principal Architect is a senior individual contributor and hands-on technical leader responsible for defining and advancing 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, strategic in-house data platform and shared foundation for acquiring, mastering, matching, exploring, securing, and distributing data.

ESSENTIAL DUTIES AND RESPONSIBILITIES

• Own the architecture vision for DataFlow as 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 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 various 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.

JOB QUALIFICATIONS

• Proven ability to define architecture and technical strategy that impacts multiple products, teams, or domains.
• Strong hands-on engineering capability with the ability to design, prototype, review, and implement critical platform components or reference implementations.
• Ability to influence without direct management authority and align technical leads, engineers, product stakeholders, and executives around a shared technical direction.
• Exceptional analytical, communication, facilitation, and mentorship skills.
• Strong judgment in balancing modernization, technical debt reduction, operational risk, customer impact, and roadmap delivery.

YEARS'''' EXPERIENCE

• 5+ years of software engineering experience, including significant ownership of complex systems, platforms, or modernization initiatives.

TECHNOLOGY/SOFTWARE KNOWLEDGE

• Experience with target and legacy technology landscape preferred, including React, Python/FastAPI, PostgreSQL, MongoDB, Oracle/PLSQL, .NET, Classic ASP, message queues, search platforms, observability tooling, and cloud or hybrid infrastructure patterns.
• Fluency with AI-assisted software development practices and the ability to guide responsible adoption across engineering teams.
• Demonstrated experience modernizing legacy SaaS, enterprise software, healthcare technology, data platforms, or other business-critical systems while maintaining production continuity.
• Experience with platform architecture, API-first design, domain-driven design, event-driven architecture, integration patterns, data products, and incremental migration approaches.