Job Description

We're looking for a Senior Software Engineer - Salesforce to join the Student Lifecycle Services engineering team at WGU. You'll work on a large, complex Salesforce org that directly supports the student journey - from enrollment through graduation. This isn't a simple CRM. It's an enterprise platform with 300+ flows, 2000+ Apex classes, deep integrations with Banner (SIS), ServiceNow, Kafka, and other university systems, and serves thousands of internal users daily.

You'll build and maintain the automation, integrations, and platform capabilities that enable WGU to serve 150,000+ students. The work matters - every flow you build, every integration you design, every performance problem you solve has a direct line to whether a student enrolls on time, gets their financial aid processed, or connects with their mentor.

We use Copado for CI/CD, follow a trigger framework pattern, and deploy through a structured promotion pipeline. We value code that's readable, testable, and built with the next engineer in mind.

The Salesforce engineering team operates within WGU's broader Ed Tech Engineering organization. We work closely with Product, Marketing, Operations, Enrollment, and Student Services stakeholders. The team practices Agile (Scrum).

This is a full-time, in-office position requiring 5 days per week in Salt Lake City, designed to foster the collaboration and connection that fuel our best work.

What You'll Do

• Design systems that span multiple Salesforce capabilities and external systems - expertise in when and how to deploy Platform Events, CDC, async Apex, and integration callouts, and how these can work together as a coherent architecture
• Make architectural decisions for the portfolio - not just your team's code, but how it fits with everything else
• Lead technical design for complex cross-system features (Salesforce, Banner, ServiceNow, Kafka)
• Solve the hardest platform problems - the ones that cross transaction boundaries, involve multiple async handoffs, or require understanding the full order of execution
• Mentor SE I and SE II engineers through design guidance, architecture reviews, and pairing on complex problems
• Drive technical direction for Salesforce development practices (async patterns, integration standards, testing strategy)
• Own and reduce technical debt - identify what needs to change, build the case, and execute the plan
• Partner with engineering leadership on platform strategy (migration plans, org health, governance limit forecasting)
• Represent the technical perspective to non-technical stakeholders (Product, Operations, Academic leadership)
• Design CI/CD improvements and release strategy for the portfolio

What You Bring

• 6+ years of software development experience, with at least 3 years on the Salesforce platform
• Bachelor's Degree in Computer Science, Information Technology, or a related field
• Experience designing multi-system integrations (not just building them - designing the approach, error handling strategy, and data reconciliation pattern)
• Mastery of async Apex patterns - you choose between Batch, Queueable, Platform Events, and CDC based on the problem, not habit
• Deep understanding of Salesforce order of execution and how it impacts complex automation
• Track record of solving problems that span multiple systems and nobody else could figure out
• Experience mentoring engineers and elevating team capability
• Ability to communicate technical architecture to both engineers and non-technical leadership
• Experience with CI/CD pipeline design and management (Copado or equivalent)

Preferred

• Salesforce Platform Developer II certification
• One or more Architect-level certifications (Integration Architect, Data Architect, Application Architect)
• Experience with Copado at the pipeline/strategy level (not just as a user)
• Experience with Kafka or event streaming platforms
• Experience in higher education technology (SIS integration, FERPA-aware systems)
• Experience with large-scale Salesforce orgs (complex sharing models, 100+ objects, 300+ automation components)
• Experience migrating legacy automation (Process Builder/Workflow Rules to Flow/Apex)