Staff Software Engineer - Salesforce

We need to output HTML fragment with sections: About the role? Actually the posting includes mission statement etc. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We must not repeat job title as heading. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, duplicated lines, application instructions, cookie/navigation/legal/EEO etc. We need to parse the posting. Key content: - Intro paragraph: "If you’re passionate about building a better future for individuals, communities, and our country—and you’re committed to working hard to play your part in building that future—consider WGU as the next step in your career. Driven by a mission to expand access to higher education through online, competency-based degree programs, WGU is also committed to being a great place to work for a diverse workforce of student-focused professionals. The university has pioneered a new way to learn in the 21st century, one that has received praise from academic, industry, government, and media leaders. Whatever your role, working for WGU gives you a part to play in helping students graduate, creating a better tomorrow for themselves and their families." That's about the role/company. Could be "About the role" or maybe "About WGU". We'll use "About the role". - Salary range: "The salary range for this position takes into account the wide range of factors that are considered in making compensation decisions including but not limited to skill sets; experience and training; licensure and certifications; and other business and organizational needs. At WGU, it is not typical for an individual to be hired at or near the top of the range for their position, and compensation decisions are dependent on the facts and circumstances of each case. A reasonable estimate of the current range is: Grade: Technical 411 Pay Range: $161,000.00 - $249,500.00" We need a Pay section with that info. Not schedule. - Job Description: "The Staff Software Engineer is a position of technical expertise, influence, and leadership in the technology realm. The position will be required to apply their expert knowledge to ensure best practices and well-engineered architecture across the department. They will also be a key stakeholder and initiator of major changes to processes, engineering practices, and system administration. This position will be required to work in a space of solving critical issues and initiatives across multiple teams. It will require an extensive and deep understanding of cutting-edge practices and innovative approaches to problems. Principal Software Engineers are also tasked with establishing and maintaining a positive and productive culture based on the WGU Leadership Principles. As a Staff Software Engineer (Salesforce), you’ll lead the evolution of WGU’s Salesforce ecosystem, shaping systems that power our student experience, enrollment processes, and operational excellence. This is a high-impact role where your technical leadership will directly improve the lives of thousands of students." That's description; could go under "About the role" or "Responsibilities". But we have separate sections: Responsibilities (list of duties). We'll extract duties from "What You'll Do" bullet list. - Experience: "Experience: 10+ years of software engineering experience, with deep hands-on expertise in Salesforce core engineering (Apex, SOQL, async patterns, integration architecture) — or equivalent depth in another enterprise stack (Java/Spring Boot, C#/.NET, or similar) with a demonstrated ability to ramp quickly onto Salesforce." That's requirement. - What You'll Do: list of duties (multiple bullet points). We'll put under Responsibilities as

• . - What You Bring: Required and Preferred sections. We'll put under Requirements (maybe Qualifications). We need to decide sections: Requirements, Qualifications, Skills. The posting has Required and Preferred. We could put Required under Requirements, Preferred under Qualifications or Skills. But we must not create thin sections. We'll combine Required and Preferred into Requirements? But we need to preserve all detail. Could have Requirements (Required) and Qualifications (Preferred). Or Skills for technical skills. Let's map: - Requirements: Required items (10+ years experience, mastery of async Apex, etc.) - Qualifications: Preferred items (certifications, experience with Data Cloud, etc.) - Skills: maybe we could list specific technical skills (Apex, SOQL, etc.) but they are already in requirements. Might be redundant. Better to have Requirements and Qualifications sections. - Benefits: The posting lists benefits under "Position & Application Details": medical, dental, vision, telehealth, mental healthcare; HSA/FSA; life insurance; disability; accident, critical illness, hospital indemnity; legal and identity theft coverage; retirement savings plan; wellbeing program; discounted WGU tuition; flexible paid time off; flexible paid sick time; 11 paid holidays; other paid leaves including up to 12 weeks parental leave; bonuses eligible. That's benefits. So we create Benefits section with list. - Schedule: The posting mentions "Full-Time Regular Positions (classified as regular and working 40 standard weekly hours)". That's schedule info. So we can create Schedule section with that. - Pay: we already have. - About the role: we have intro paragraph. We must not include boilerplate like "Job Description Disclaimer", "Additional Information Disclaimer", "How to Apply", "Equal Employment Opportunity", etc. We must not repeat job title as heading. We must not include metadata like Job ID. We must preserve all substantive info. Now produce HTML fragment with

  headings and appropriate

  or

  • . We need to ensure we don't create sections with filler like "commensurate with experience". We have actual content. Let's craft:

    About the role

    If you’re passionate about building a better future for individuals, communities, and our country—and you’re committed to working hard to play your part in building that future—consider WGU as the next step in your career. Driven by a mission to expand access to higher education through online, competency-based degree programs, WGU is also committed to being a great place to work for a diverse workforce of student-focused professionals. The university has pioneered a new way to learn in the 21st century, one that has received praise from academic, industry, government, and media leaders. Whatever your role, working for WGU gives you a part to play in helping students graduate, creating a better tomorrow for themselves and their families.

    Responsibilities

    • Split time between hands-on engineering/mentoring within the team and serving as the Salesforce architects' implementation partner — turning architecture decisions for emerging platform capabilities (Data Cloud/Data 360, Agentforce, Marketing Cloud, Tableau Next) into working solutions
    • Set automation, integration, security, and DevOps standards adopted across multiple teams, not just your own
    • Own org-wide security posture and compliance-framework decisions for the platform (including FERPA-aware design)
    • Govern enterprise data model decisions — cross-system data contracts, org split/merge strategy, legacy automation tech-debt strategy
    • Lead architectural reviews and platform health assessments — governance-limit forecasting, remediation planning
    • Mentor SE I/II/Senior engineers and shape technical direction through influence — no formal management/headcount responsibility
    • Represent the technical perspective to non-technical stakeholders (Product, Operations, Academic leadership) and drive alignment on platform strategy

    Requirements

    • 10+ years of software engineering experience with deep hands-on expertise in Salesforce core engineering (Apex, SOQL, async patterns, integration architecture) — or equivalent depth in another enterprise stack (Java/Spring Boot, C#/.NET, or similar) with a demonstrated ability to ramp quickly onto Salesforce
    • Mastery of async Apex / event-driven patterns at a governance level — choosing and standardizing approaches across teams, not just applying them
    • Experience designing (not just building) multi-system integration architecture — API strategy, event-driven decisions, vendor evaluation
    • Track record of setting technical standards adopted beyond your own team
    • Deep understanding of security architecture and compliance frameworks in a regulated environment (FERPA or equivalent)
    • Demonstrated ability to mentor and shape technical direction through influence
    • Strong communication skills across technical and non-technical audiences
    • Comfort operating in ambiguity — partnering with architects on platform capabilities before established patterns exist

    Qualifications

    • Application Architect or System Architect certification (or equivalent depth without the cert)
    • Experience with Data Cloud, Agentforce, Marketing Cloud, or Tableau Next
    • Experience with large-scale Salesforce orgs (100+ objects, 300+ automation components)
    • Higher education or large-scale SaaS platform experience
    • Experience with Copado (or equivalent) at the pipeline/governance level

    Benefits

    • Bonuses eligible
    • Medical, dental, vision, telehealth and mental healthcare
    • Health savings account and flexible spending account
    • Basic and voluntary life insurance
    • Disability coverage
    • Accident, critical illness and hospital indemnity supplemental coverages
    • Legal and identity theft coverage
    • Retirement savings plan
    • Wellbeing program
    • Discounted WGU tuition
    • Flexible paid time off for rest and relaxation with no need for accrual
    • Flexible paid sick time with no need for accrual
    • 11 paid holidays
    • Other paid leaves, including up to 12 weeks of parental leave

    Pay

    Grade: Technical 411; Pay Range: $161,000.00 - $249,500.00

    Schedule

    Full‑time regular position (40 standard weekly hours)

    We must ensure we didn't include any boilerplate. Check: we omitted "Job Description", "Job Description Disclaimer", "Additional Information Disclaimer", "How to Apply", "Equal Employment Opportunity", etc. Good. We kept all substantive info: intro, responsibilities, requirements, qualifications, benefits, pay, schedule. Check if any info missing: The initial paragraph about "The Staff Software Engineer is a position of technical expertise..." we didn't include that explicitly. That is part of job description; maybe we should incorporate into About the role or Responsibilities. The responsibilities list we have from "What You'll Do". The earlier paragraph about position description could be added to About the role as extra detail. Let's add a paragraph after intro maybe. We could add to About the role: "The Staff Software Engineer is a position of technical expertise, influence, and leadership in the technology realm. The position will be required to apply their expert knowledge to ensure best practices and well-engineered architecture across the department. They will also be a key stakeholder and initiator of major changes to processes, engineering practices, and system administration. This position will be required to work in a space of solving critical issues and initiatives across multiple teams. It will require an extensive and deep understanding of cutting-edge practices and innovative approaches to problems. Principal Software Engineers are also tasked with establishing and maintaining a positive and productive culture based on the WGU Leadership Principles. As a Staff Software Engineer (Salesforce), you’ll lead the evolution of WGU’s Salesforce ecosystem, shaping systems that power our student experience, enrollment processes, and operational excellence. This is a high-impact role where your technical leadership will directly improve the lives of thousands of students." That is substantive and not covered elsewhere