Senior Software Engineer - WGU Labs
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to extract substantive content: The posting includes:
- 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."
- 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 410 Pay Range: $143,700.00 - $222,700.00"
- Job Description: "The Senior Software Engineer is responsible for the research, design, development, analysis, testing, and implementation of software operating or application systems. They communicate project information to client, project manager, or other design personnel working on projects. They maintain good working relationships with clients and staff. They write and maintains complete documentation. They support team members and ensures established goals and deadlines are met. They keep management informed of status and significant problems."
- "What You'll Do As a Senior Software Engineer, you'll play a critical role in shaping the future of our technology platforms while helping drive innovation across the organization. You'll partner with talented engineers, architects, and business leaders to solve complex technical challenges and deliver solutions that directly impact students, faculty, and the broader educational experience. In this role, you will:"
Then a list of bullet points (starting with "Design, build, and support scalable, secure, and high-performing software solutions using modern full-stack technologies — including React, Next.js, and Node.js on the front end and Python (FastAPI, Flask, or similar) on the back end — that power critical business capabilities." etc). Many bullet points.
- "Why Engineers Love This Role" with bullet points.
- "Job Description Disclaimer: This position description provides the major duties/responsibilities, requirements and working conditions for the position. It is intended to be an accurate reflection of the current position, however management reserves the right to revise or change as necessary to meet organizational needs. Other responsibilities may be assigned when circumstances require. This position requires occasional travel of up to 20%, including required attendance at designated company summits (typically one to two per year). Additional travel may include conferences, visits to company locations, and other business-related events as needed. Additional travel may be assigned as needed to support business requirements."
- "Position & Application Details Full-Time Regular Positions (classified as regular and working 40 standard weekly hours): This is a full-time, regular position (classified for 40 standard weekly hours) that is eligible for bonuses; 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; and 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, and other paid leaves, including up to 12 weeks of parental leave."
- "How to Apply: If interested, an application will need to be submitted online. Internal WGU employees will need to apply through the internal job board in Workday." (application instructions - we need to remove)
- "Additional Information Disclaimer: The job posting highlights the most critical responsibilities and requirements of the job. It’s not all-inclusive." (boilerplate - remove)
- "Accommodations: Applicants with disabilities who require assistance or accommodation during the application or interview process should contact our Talent Acquisition team at recruiting@wgu.edu." (EEO/accommodations - remove)
- "Equal Employment Opportunity: All qualified applicants will receive consideration for employment without regard to any protected characteristic as required by law." (remove)
We need to keep substantive info: intro, salary/pay, responsibilities (what you'll do), maybe "Why Engineers Love This Role" could be considered "Benefits"? Actually it's more about role appeal; could be a section like "Why Engineers Love This Role" but not in prescribed headings. The allowed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map content to these.
- About the role: could include the intro paragraph about WGU mission and role purpose.
- Responsibilities: list of duties from "What You'll Do" bullet points.
- Requirements/Qualifications/Skills: The posting does not explicitly list requirements like education, years experience, etc. It mentions responsibilities but not explicit qualifications. There's a generic "Job Description" earlier about responsibilities. There's no explicit qualifications list. So we should not create sections for Requirements, Qualifications, Skills if no specific content. We should avoid filler.
- Benefits: The "Position & Application Details" includes benefits list: bonuses; 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; flexible paid sick time; 11 paid holidays; other paid leaves including up to 12 weeks of parental leave. That's benefits.
- Pay: we have salary range.
- Schedule: we have full-time regular position 40 standard weekly hours. That's schedule.
Thus we can create sections: About the role, Responsibilities, Benefits, Pay, Schedule.
We must not repeat job title as heading. Use
for each section heading.
We need to use - for any list of duties/requirements/benefits. For prose, use
.
We need to preserve all substantive information, not invent or summarize away detail. So we need to include the bullet points exactly as given (or close). We must not omit any bullet point content. Also need to include the intro paragraph(s). Also need to include the salary range details (including grade). Also need to include schedule details (full-time regular 40 standard weekly hours). Also need to include benefits list exactly.
We need to remove boilerplate like disclaimer, accommodations, EEO, how to apply, additional information disclaimer.
We also need to remove the "Job Description" earlier generic responsibilities (the first paragraph about responsibilities) because we have the "What You'll Do" list which is more detailed. However we should preserve all substantive information; the earlier generic responsibilities may be considered duplicate of the list but still substantive. The instruction: remove duplicated lines. So we can drop the earlier generic responsibilities if they are duplicated by the list. The list includes many items; the earlier generic responsibilities are covered but not exactly same. However to avoid duplication, we can keep the list and maybe keep the earlier generic responsibilities as prose? But that would be duplication. Safer to keep only the list and maybe the introductory sentence "What You'll Do As a Senior Software Engineer, you'll play a critical role..." as prose before the list. That is part of the responsibilities section.
Thus responsibilities section: start with a
containing "What You'll Do As a Senior Software Engineer, you'll play a critical role in shaping the future of our technology platforms while helping drive innovation across the organization. You'll partner with talented engineers, architects, and business leaders to solve complex technical challenges and deliver solutions that directly impact students, faculty, and the broader educational experience." Then a
with each bullet point.
We need to ensure we include all bullet points exactly as in the posting. Let's extract them:
From the posting:
- Design, build, and support scalable, secure, and high-performing software solutions using modern full-stack technologies — including React, Next.js, and Node.js on the front end and Python (FastAPI, Flask, or similar) on the back end — that power critical business capabilities.
- Serve as a technical leader and trusted advisor, influencing architecture, engineering standards, and best practices across teams.
- Lead the delivery of complex initiatives from concept through implementation, balancing speed, quality, and long-term maintainability.
- Mentor and develop fellow engineers through technical guidance, code reviews, design discussions, and knowledge sharing.
- Partner with cross-functional teams to understand business objectives and translate requirements into thoughtful technical solutions.
- Identify risks, dependencies, and opportunities early, helping teams navigate challenges before they impact delivery.
- Drive continuous improvement in software quality, reliability, observability, and operational excellence.
- Contribute to modernization initiatives, including cloud-native development, containerization and orchestration (Docker, ECS, Kubernetes), Infrastructure as Code (Terraform, CloudFormation), application integrations, and system scalability.
- Design and work with modern data layers, including PostgreSQL and ORMs such as Drizzle, Prisma, or SQLAlchemy.
- Apply AI-assisted development practices to accelerate delivery, and integrate AI/ML services into applications to create smarter, more capable platform experiences.
- Lead troubleshooting and resolution efforts for complex production issues, improving service stability and customer experience.
- Champion engineering excellence through thoughtful testing strategies, automation, and data-driven decision making.
- Explore emerging technologies and innovative approaches — including real-time collaboration tools (WebSockets, Y.js) and evolving AI/ML capabilities — that can improve platform capabilities, developer productivity, and organizational outcomes.
- Foster a collaborative engineering culture where knowledge sharing, innovation, and continuous learning thrive.
That's 14 bullet points.
Now "Why Engineers Love This Role" bullet points:
- Architectural Influence: Help drive technical direction and shape platform strategy.
- Meaningful Impact: Build solutions that directly support higher education and student success.
- Complex Technical Challenges: Work on integrations, scalability, cloud modernization, AI/ML-powered features, and enterprise-scale systems.
- Modern Toolset: Build with a contemporary stack — React, Next.js, Node.js, Python, PostgreSQL, Docker/Kubernetes, and Terraform — alongside AI-assisted development tools.
- Leadership Without Management: Influence teams, mentor engineers, and be recognized as a technical expert.
- Continuous Learning: Explore new technologies, including AI/ML integr
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to extract substantive content: The posting includes: - 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." - 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 410 Pay Range: $143,700.00 - $222,700.00" - Job Description: "The Senior Software Engineer is responsible for the research, design, development, analysis, testing, and implementation of software operating or application systems. They communicate project information to client, project manager, or other design personnel working on projects. They maintain good working relationships with clients and staff. They write and maintains complete documentation. They support team members and ensures established goals and deadlines are met. They keep management informed of status and significant problems." - "What You'll Do As a Senior Software Engineer, you'll play a critical role in shaping the future of our technology platforms while helping drive innovation across the organization. You'll partner with talented engineers, architects, and business leaders to solve complex technical challenges and deliver solutions that directly impact students, faculty, and the broader educational experience. In this role, you will:" Then a list of bullet points (starting with "Design, build, and support scalable, secure, and high-performing software solutions using modern full-stack technologies — including React, Next.js, and Node.js on the front end and Python (FastAPI, Flask, or similar) on the back end — that power critical business capabilities." etc). Many bullet points. - "Why Engineers Love This Role" with bullet points. - "Job Description Disclaimer: This position description provides the major duties/responsibilities, requirements and working conditions for the position. It is intended to be an accurate reflection of the current position, however management reserves the right to revise or change as necessary to meet organizational needs. Other responsibilities may be assigned when circumstances require. This position requires occasional travel of up to 20%, including required attendance at designated company summits (typically one to two per year). Additional travel may include conferences, visits to company locations, and other business-related events as needed. Additional travel may be assigned as needed to support business requirements." - "Position & Application Details Full-Time Regular Positions (classified as regular and working 40 standard weekly hours): This is a full-time, regular position (classified for 40 standard weekly hours) that is eligible for bonuses; 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; and 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, and other paid leaves, including up to 12 weeks of parental leave." - "How to Apply: If interested, an application will need to be submitted online. Internal WGU employees will need to apply through the internal job board in Workday." (application instructions - we need to remove) - "Additional Information Disclaimer: The job posting highlights the most critical responsibilities and requirements of the job. It’s not all-inclusive." (boilerplate - remove) - "Accommodations: Applicants with disabilities who require assistance or accommodation during the application or interview process should contact our Talent Acquisition team at recruiting@wgu.edu." (EEO/accommodations - remove) - "Equal Employment Opportunity: All qualified applicants will receive consideration for employment without regard to any protected characteristic as required by law." (remove) We need to keep substantive info: intro, salary/pay, responsibilities (what you'll do), maybe "Why Engineers Love This Role" could be considered "Benefits"? Actually it's more about role appeal; could be a section like "Why Engineers Love This Role" but not in prescribed headings. The allowed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map content to these. - About the role: could include the intro paragraph about WGU mission and role purpose. - Responsibilities: list of duties from "What You'll Do" bullet points. - Requirements/Qualifications/Skills: The posting does not explicitly list requirements like education, years experience, etc. It mentions responsibilities but not explicit qualifications. There's a generic "Job Description" earlier about responsibilities. There's no explicit qualifications list. So we should not create sections for Requirements, Qualifications, Skills if no specific content. We should avoid filler. - Benefits: The "Position & Application Details" includes benefits list: bonuses; 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; flexible paid sick time; 11 paid holidays; other paid leaves including up to 12 weeks of parental leave. That's benefits. - Pay: we have salary range. - Schedule: we have full-time regular position 40 standard weekly hours. That's schedule. Thus we can create sections: About the role, Responsibilities, Benefits, Pay, Schedule. We must not repeat job title as heading. Use
for each section heading.
We need to use - for any list of duties/requirements/benefits. For prose, use
.
We need to preserve all substantive information, not invent or summarize away detail. So we need to include the bullet points exactly as given (or close). We must not omit any bullet point content. Also need to include the intro paragraph(s). Also need to include the salary range details (including grade). Also need to include schedule details (full-time regular 40 standard weekly hours). Also need to include benefits list exactly.
We need to remove boilerplate like disclaimer, accommodations, EEO, how to apply, additional information disclaimer.
We also need to remove the "Job Description" earlier generic responsibilities (the first paragraph about responsibilities) because we have the "What You'll Do" list which is more detailed. However we should preserve all substantive information; the earlier generic responsibilities may be considered duplicate of the list but still substantive. The instruction: remove duplicated lines. So we can drop the earlier generic responsibilities if they are duplicated by the list. The list includes many items; the earlier generic responsibilities are covered but not exactly same. However to avoid duplication, we can keep the list and maybe keep the earlier generic responsibilities as prose? But that would be duplication. Safer to keep only the list and maybe the introductory sentence "What You'll Do As a Senior Software Engineer, you'll play a critical role..." as prose before the list. That is part of the responsibilities section.
Thus responsibilities section: start with a
containing "What You'll Do As a Senior Software Engineer, you'll play a critical role in shaping the future of our technology platforms while helping drive innovation across the organization. You'll partner with talented engineers, architects, and business leaders to solve complex technical challenges and deliver solutions that directly impact students, faculty, and the broader educational experience." Then a
with each bullet point.
We need to ensure we include all bullet points exactly as in the posting. Let's extract them:
From the posting:
- Design, build, and support scalable, secure, and high-performing software solutions using modern full-stack technologies — including React, Next.js, and Node.js on the front end and Python (FastAPI, Flask, or similar) on the back end — that power critical business capabilities.
- Serve as a technical leader and trusted advisor, influencing architecture, engineering standards, and best practices across teams.
- Lead the delivery of complex initiatives from concept through implementation, balancing speed, quality, and long-term maintainability.
- Mentor and develop fellow engineers through technical guidance, code reviews, design discussions, and knowledge sharing.
- Partner with cross-functional teams to understand business objectives and translate requirements into thoughtful technical solutions.
- Identify risks, dependencies, and opportunities early, helping teams navigate challenges before they impact delivery.
- Drive continuous improvement in software quality, reliability, observability, and operational excellence.
- Contribute to modernization initiatives, including cloud-native development, containerization and orchestration (Docker, ECS, Kubernetes), Infrastructure as Code (Terraform, CloudFormation), application integrations, and system scalability.
- Design and work with modern data layers, including PostgreSQL and ORMs such as Drizzle, Prisma, or SQLAlchemy.
- Apply AI-assisted development practices to accelerate delivery, and integrate AI/ML services into applications to create smarter, more capable platform experiences.
- Lead troubleshooting and resolution efforts for complex production issues, improving service stability and customer experience.
- Champion engineering excellence through thoughtful testing strategies, automation, and data-driven decision making.
- Explore emerging technologies and innovative approaches — including real-time collaboration tools (WebSockets, Y.js) and evolving AI/ML capabilities — that can improve platform capabilities, developer productivity, and organizational outcomes.
- Foster a collaborative engineering culture where knowledge sharing, innovation, and continuous learning thrive.
That's 14 bullet points.
Now "Why Engineers Love This Role" bullet points:
- Architectural Influence: Help drive technical direction and shape platform strategy.
- Meaningful Impact: Build solutions that directly support higher education and student success.
- Complex Technical Challenges: Work on integrations, scalability, cloud modernization, AI/ML-powered features, and enterprise-scale systems.
- Modern Toolset: Build with a contemporary stack — React, Next.js, Node.js, Python, PostgreSQL, Docker/Kubernetes, and Terraform — alongside AI-assisted development tools.
- Leadership Without Management: Influence teams, mentor engineers, and be recognized as a technical expert.
- Continuous Learning: Explore new technologies, including AI/ML integr
. We need to preserve all substantive information, not invent or summarize away detail. So we need to include the bullet points exactly as given (or close). We must not omit any bullet point content. Also need to include the intro paragraph(s). Also need to include the salary range details (including grade). Also need to include schedule details (full-time regular 40 standard weekly hours). Also need to include benefits list exactly. We need to remove boilerplate like disclaimer, accommodations, EEO, how to apply, additional information disclaimer. We also need to remove the "Job Description" earlier generic responsibilities (the first paragraph about responsibilities) because we have the "What You'll Do" list which is more detailed. However we should preserve all substantive information; the earlier generic responsibilities may be considered duplicate of the list but still substantive. The instruction: remove duplicated lines. So we can drop the earlier generic responsibilities if they are duplicated by the list. The list includes many items; the earlier generic responsibilities are covered but not exactly same. However to avoid duplication, we can keep the list and maybe keep the earlier generic responsibilities as prose? But that would be duplication. Safer to keep only the list and maybe the introductory sentence "What You'll Do As a Senior Software Engineer, you'll play a critical role..." as prose before the list. That is part of the responsibilities section. Thus responsibilities section: start with a
containing "What You'll Do As a Senior Software Engineer, you'll play a critical role in shaping the future of our technology platforms while helping drive innovation across the organization. You'll partner with talented engineers, architects, and business leaders to solve complex technical challenges and deliver solutions that directly impact students, faculty, and the broader educational experience." Then a
- with each bullet point.
We need to ensure we include all bullet points exactly as in the posting. Let's extract them:
From the posting:
- Design, build, and support scalable, secure, and high-performing software solutions using modern full-stack technologies — including React, Next.js, and Node.js on the front end and Python (FastAPI, Flask, or similar) on the back end — that power critical business capabilities.
- Serve as a technical leader and trusted advisor, influencing architecture, engineering standards, and best practices across teams.
- Lead the delivery of complex initiatives from concept through implementation, balancing speed, quality, and long-term maintainability.
- Mentor and develop fellow engineers through technical guidance, code reviews, design discussions, and knowledge sharing.
- Partner with cross-functional teams to understand business objectives and translate requirements into thoughtful technical solutions.
- Identify risks, dependencies, and opportunities early, helping teams navigate challenges before they impact delivery.
- Drive continuous improvement in software quality, reliability, observability, and operational excellence.
- Contribute to modernization initiatives, including cloud-native development, containerization and orchestration (Docker, ECS, Kubernetes), Infrastructure as Code (Terraform, CloudFormation), application integrations, and system scalability.
- Design and work with modern data layers, including PostgreSQL and ORMs such as Drizzle, Prisma, or SQLAlchemy.
- Apply AI-assisted development practices to accelerate delivery, and integrate AI/ML services into applications to create smarter, more capable platform experiences.
- Lead troubleshooting and resolution efforts for complex production issues, improving service stability and customer experience.
- Champion engineering excellence through thoughtful testing strategies, automation, and data-driven decision making.
- Explore emerging technologies and innovative approaches — including real-time collaboration tools (WebSockets, Y.js) and evolving AI/ML capabilities — that can improve platform capabilities, developer productivity, and organizational outcomes.
- Foster a collaborative engineering culture where knowledge sharing, innovation, and continuous learning thrive.
That's 14 bullet points.
Now "Why Engineers Love This Role" bullet points:
- Architectural Influence: Help drive technical direction and shape platform strategy.
- Meaningful Impact: Build solutions that directly support higher education and student success.
- Complex Technical Challenges: Work on integrations, scalability, cloud modernization, AI/ML-powered features, and enterprise-scale systems.
- Modern Toolset: Build with a contemporary stack — React, Next.js, Node.js, Python, PostgreSQL, Docker/Kubernetes, and Terraform — alongside AI-assisted development tools.
- Leadership Without Management: Influence teams, mentor engineers, and be recognized as a technical expert.
- Continuous Learning: Explore new technologies, including AI/ML integr