Solutions Architect

At SCP Health, what you do matters

As part of the SCP Health team, you have an opportunity to make a difference. At our core, we work to bring hospitals and healers together in the pursuit of clinical effectiveness. With a portfolio of over 8 million patients, 7500 providers, 30 states, and 400 healthcare facilities, SCP Health is a leader in clinical practice management spanning the entire continuum of care, including emergency medicine, hospital medicine, wellness, telemedicine, intensive care, and ambulatory care.

Why you will love working here:

• Strong track record of providing excellent work/life balance.

• Comprehensive benefits package and competitive compensation.

• Commitment to fostering an inclusive culture of belonging and empowerment through our core values - collaboration, courage, agility, and respect.

Key Responsibilities

Functional Solution Design

• Turn business needs and requirements into solution concepts and functional designs centered on Salesforce, accounting for how QGenda, Workday, and integrations interact
• Develop user stories, acceptance criteria, and technical spikes from product epics, partnering with Engineering so work is ready to build
• Partner with Product Management to ensure requirements align with architecture best practices and platform standards; recommend alternatives when a request introduces unnecessary customization, technical debt, or cross-system risk
• Evaluate design options and recommend a path, making trade-offs clear (cost, effort, scale, risk, time to market)
• Ensure solutions align across workstreams and with SCP’s platform direction and architecture standards
• Produce solution artifacts, including architecture and data flow diagrams, sequence diagrams, and process-to-system maps, using tools such as Lucidchart, plus wireframes or UI mockups where needed

System & Integration Analysis

• Query systems and validate data to understand how solutions actually behave
• Review integration behavior between Salesforce, QGenda, Workday, and MuleSoft, and interpret findings with Engineering and Technical Architects to confirm design intent
• Lead root-cause analysis for design and integration issues, and feed what you learn back into future designs
• Document data mappings, source-of-truth decisions, and integration requirements in design artifacts
• Identify data and integration needs early in discovery, not after build

Design Governance

• Prepare complete design submissions and present them to the Design Authority and EARB
• Record key design decisions in decision records
• Apply established platform standards (naming conventions, data model patterns, access controls, development practices) in every design