Senior Software Development Engineer (US Federal)

We need to output HTML fragment only, with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive information. We need to parse the posting. Key sections: - Intro paragraph about company culture etc. Might be considered "About the team"? Actually there is "About The Team" section. That could be considered "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can also include "About the Team" maybe as "About the role"? But they said use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings. Likely we need sections: About the role (maybe includes description of role), Responsibilities, Requirements (maybe basic qualifications), Qualifications (maybe other qualifications), Skills (maybe specific skills), Benefits (maybe flexible work description?), Pay (salary ranges), Schedule (flexible work approach). Also maybe "About The Team" could be part of About the role or omitted? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use those for section headings. Probably we should stick to those headings only. If a section doesn't have content, we omit it. Thus we need to extract: - About the role: description of role: "This role will support one or more direct or indirect contracts with the U.S. Federal Government which, due to federal government security requirements, mandates that all Workday personnel working on the contracts be United States citizens (naturalized or native). May be required to be on site at client locations in the DC, MD, and VA (DMV) area. We are looking for a highly motivated and Senior Engineer to join our growing Infrastructure and Platform Engineering team. You will play a critical role in building, scaling, observing and maintaining our Kubernetes-based platform and enabling our engineering organization to deliver capabilities and incremental products quickly and reliably. You will have the opportunity to work with cutting-edge technologies, solve complicated problems, and contribute to the foundation of our infrastructure. This role requires a strong technical background, a passion for automation, and a collaborative mindset. This role involves collaborating with teams across multiple locations and time zones. You will need to be adept at communicating optimally and building positive relationships with colleagues in diverse locations. You have a growth mindset and will be part of a team promoting a diverse and inclusive environment where you and your workmates are happy, energized and engaged, and who are excited to come to work every day." We can include that as About the role. - Responsibilities: list bullet points after "Responsibilities:" includes many items. We'll capture each as

. - Requirements: maybe "Basic Qualifications:" and "Other Qualifications (preferred):" could be considered Requirements? The instruction separate Requirements and Qualifications. We could treat Basic Qualifications as Requirements, and Other Qualifications as Qualifications. Or we could combine. Let's follow: Requirements = Basic Qualifications. Qualifications = Other Qualifications (preferred). Skills maybe separate list of specific skills like programming languages, tools, etc. But we can also put those under Qualifications. However we need to include Skills section if there is specific content. The posting lists many skills: Infrastructure as code: Proficiency in infrastructure automation tools like Terraform; CI/CD: Experience with building, maintaining, and consuming CI/CD pipelines and tools like Argo CD; Programming skills: Proficiency in at least one programming language; Problem-solving: Strong analytical and problem-solving skills; Communication: Excellent communication and collaboration skills; Strong understanding of Kubernetes; Amazon Web Services proficiency working in a production environment; C#, Python, Ruby, Rust, or Go programming language proficiency; Experience with security auditing and compliance frameworks; Experience working in air gapped cloud regions; Preferred DoD 8570/8140 compliant with at least IAT Level II certification, including a current Computing Environment (CE) credential and one approved specialty certification (e.g., CompTIA CySA+, GICSP, CASP+); Bachelor's degree in a computer related field or equivalent work experience. We could split: Requirements (basic qualifications) = 5+ years of hands-on experience working with large scale cloud infrastructure, DevOps, and software development engineering skills. Also maybe Bachelor's degree? Actually Bachelor's degree is under Other Qualifications (preferred). So Basic Qualifications: 5+ years of hands-on experience working with large scale cloud infrastructure, DevOps, and software development engineering skills. Thus Requirements section: that bullet. Qualifications section: list the Other Qualifications (preferred) items. Skills section: maybe we could extract specific technical skills: Terraform, Argo CD, programming languages, Kubernetes, AWS, security auditing, air-gapped, DoD 8570 certifications. But those are already in Qualifications. To avoid duplication, maybe we omit Skills section and put those under Qualifications. But instruction says we can have Skills section if there is real specific content. We could still include Skills section listing e.g., Terraform, Argo CD, Kubernetes, AWS, C#/Python/Ruby/Rust/Go, security auditing, air-gapped, DoD 8570 certifications. However that would duplicate content from Qualifications. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is okay as long as we preserve? It might be considered redundant but not wrong. However better to avoid duplication by placing those specifics under Qualifications and not having a separate Skills section. But we need to decide. Given the headings list includes Skills, we could include it if we have content. The posting does have a list of skills under Other Qualifications (preferred). So we could treat that as Skills section. Then Qualifications could be things like Bachelor's degree, security clearance, etc. But the posting lumps them together. Let's parse: Other Qualifications (preferred): list includes: - Infrastructure as code: Proficiency in infrastructure automation tools like Terraform. - CI/CD: Experience with building, maintaining, and consuming CI/CD pipelines and tools like Argo CD. - Programming skills: Proficiency in at least one programming language - Problem-solving: Strong analytical and problem-solving skills. - Communication: Excellent communication and collaboration skills. - Strong understanding of Kubernetes - Amazon Web Services proficiency working in a production environment - C#, Python, Ruby, Rust, or Go programming language proficiency - Experience with security auditing and compliance frameworks. - Experience working in air gapped cloud regions - Preferred DoD 8570/8140 compliant with at least IAT Level II certification, including a current Computing Environment (CE) credential and one approved specialty certification (e.g., CompTIA CySA+, GICSP, CASP+) - Bachelor's degree in a computer related field or equivalent work experience Thus we could split: Skills = technical skills (Terraform, Argo CD, programming languages, Kubernetes, AWS, security auditing, air-gapped, DoD 8570 certs). Qualifications = education (Bachelor's degree) and maybe security clearance? Actually security clearance is mentioned earlier under "About You": "This role may require a security clearance at the TS/SCI w/CI Poly level. Applicants must have the ability to obtain and maintain a U.S. government issued security clearance. An active TS/SCI w/CI Poly is preferred." That could be under Requirements or Qualifications. Let's treat that as Requirements (since it's a requirement). But we already used Requirements for basic qualifications (5+ years). Could combine multiple items under Requirements: 5+ years experience, ability to obtain/maintain TS/SCI clearance, US citizenship (due to contract). Actually US citizenship is mandated by contract; that is a requirement. So we can include those. Thus: Requirements: - 5+ years of hands-on experience working with large scale cloud infrastructure, DevOps, and software development engineering skills. - Ability to obtain and maintain a U.S. government issued security clearance (TS/SCI w/CI Poly preferred). - Must be a United States citizen (naturalized or native) due to federal government contract requirements. Qualifications: - Bachelor's degree in a computer related field or equivalent work experience. Skills: - Proficiency in infrastructure automation tools like Terraform. - Experience with building, maintaining, and consuming CI/CD pipelines and tools like Argo CD. - Proficiency in at least one programming language (C#, Python, Ruby, Rust, or Go). - Strong analytical and problem-solving skills. - Excellent communication and collaboration skills. - Strong understanding of Kubernetes. - Amazon Web Services proficiency in a production environment. - Experience with security auditing and compliance frameworks. - Experience working in air-gapped cloud regions. - DoD 8570/8140 compliant with at least IAT Level II certification, including a current Computing Environment (CE) credential and one approved specialty certification (e.g., CompTIA CySA+, GICSP, CASP+). Benefits: The posting mentions "Our Approach to Flexible Work" and some benefits like trust, tools, skills, support, etc. Also mentions "Workday Pay Transparency Statement" and bonus plan, stock grants. Also "Our Approach to Flexible Work" describes schedule flexibility. Benefits could include: trust to take risks, tools to grow, skills to develop, support of company invested in you, Workday Bonus Plan or role-specific commission/bonus, annual refresh stock grants, flexible work approach (at least 50% time in office/field each quarter). Also maybe "We’re obsessed with making hard work pay off" but that's fluff. We need to include Benefits section only if there is real specific content. The posting does mention: "In return, we’ll give you the trust to take risks, the tools to grow, the skills to develop and the support of a company invested in you for the long haul." Also "As a part of the total compensation package, this role may be eligible for the Workday Bonus Plan or a role-specific commission/bonus, as well as annual refresh stock grants." Also "Our Approach to Flexible Work..." which is more about schedule. Thus Benefits could include those non-pay, non-schedule items: trust, tools, skills, support, bonus plan, stock grants. Pay: Salary ranges: Primary Location: USA.VA.Reston Primary Location Base Pay Range: $163,800 USD - $245,800 USD Additional US Location(s) Base Pay Range: $148,200 USD - $264,000 USD. Also mention bonus plan etc but that's under Benefits. Schedule: "Our Approach to Flexible Work With Flex Work, we’re combining the best of both worlds: in-person time and remote. Our approach enables our teams to deepen connections, maintain a strong community, and do their best work. We know that flexibility can take shape in many ways, so rather than a number of required days in-office each week, we simply spend at least half (50%) of our time each quarter in the office or in the field with our customers, prospects, and partners (depending on role). This means you'll have the freedom to create a flexible schedule that caters to your business, team, and personal needs, while being intentional to make the most of time spent together. Those in our remote "home office" roles also have the opportunity to come together in our offices for important moments that matter." Thus schedule content. Now we need to output HTML fragment with

headings and

• for lists,

  for prose. We must not include any boilerplate like EEO, legal, etc. Also must not include duplicated lines. Ensure we preserve all substantive information. We need to be careful not to include navigation etc. Let's craft sections: