Senior Principal Software Architect - Healthcare

Overview

The Senior Principal Software Architect role shapes and guides the architecture of complex systems, platforms, and technology practice domains across the organization. The role balances architectural rigor with pragmatic delivery by considering business outcomes, quality attributes, organizational capabilities, cost, risk, and time‑to‑market commitments. The architect remains hands‑on through discovery, design, technical spikes, reference implementations, and foundational assets that enable durable delivery, develop the capabilities of others, and sustain support continuity.

The architect also communicates architectural strategy, trade‑offs, risk, and technology direction to technical and nontechnical stakeholders and evaluates industry developments to guide company and partner implementations.

• Develop architecture and technical roadmaps with engineering, product, security, data, infrastructure, and business leadership.
• Shape architecture strategy and drive alignment across technology domains, platforms, product areas, and business capabilities.
• Provide hands‑on technical leadership through discovery, architecture design, trade‑off analysis, technical spikes, reference implementations, architecture fitness tests, and critical design or code reviews.
• Define, socialize, evolve, and drive adoption of architecture principles, standards, reference patterns, implementation guidance, and technical decision records, establishing lightweight governance and automated guardrails where appropriate.
• Constructively challenge decisions that diverge from agreed architecture, standards, patterns, or governance processes and ensure exceptions are explicitly risk‑assessed, documented, time‑bound, and assigned to an accountable owner.
• Partner with engineering, product, and program leadership to translate architecture decisions into executable plans, protect critical quality attributes, and resolve trade‑offs that could materially affect delivery or operational outcomes.
• Coach internal and external stakeholders on the appropriate application of architecture, patterns, platforms, and technologies, enabling teams to make sound decisions independently.
• Build trusted relationships across engineering, product, security, data, infrastructure, operations, and business leadership, influencing with and without formal authority through listening, coaching, facilitation, evidence, and clear communication of technical and business trade‑offs.
• Evaluate relevant industry, vendor, security, regulatory, and platform developments and translate them into actionable recommendations, roadmap changes, or risk‑mitigation strategies.
• Identify and address architectural drift, unmanaged complexity, and inappropriate technology use, collaborating with teams to achieve remediation and using formal exception, accountability, and escalation processes when material risks persist.
• Lead evaluation of solution options with a balanced understanding of non‑functional quality goals such as scalability, reliability, performance, security, maintainability, operability, and cost against risk and implementation constraints.
• Lead architecture reviews, decision forums, learning sessions, and design discussions, facilitating resolution of cross‑team disagreements and acting as an escalation point for material architectural risks or decisions that cannot be resolved within delivery teams.
• Participate in relevant industry conferences and working groups to shape effective architecture and technical roadmaps.

• Deep knowledge across relevant architecture domains and technology disciplines with a demonstrated ability to increase organizational technical competence through stakeholder and engineering feedback.
• Experience in shaping and communicating architectural strategy that results in measurable improvements in customer outcomes, delivery speed, cost/TCO, resilience, security, scalability, and operability.
• Track record of producing systems and services that meet agreed service‑level objectives and service‑level agreements, with architecture decisions, exceptions, risks, and remediation plans remaining current and traceable.
• Ability to…