Mid/Sr Software Development Engineer (US Federal)

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job posting. First, there is a lot of fluff at start: "Your work days are brighter here..." etc. That's likely boilerplate, but we need to preserve substantive info. The posting includes sections: About The Team, About The Role, About You, Basic Qualification, Other Qualifications, Preferred DoD..., etc. Also Pay Transparency Statement with salary range. Also Flexible Work description (schedule). Benefits? Not explicit benefits listed; only mention of total compensation package, bonus plan, stock grants, but not specific benefits like health, 401k. The instruction: only include Pay/Schedule/Benefits sections if posting actually states them. It does state Pay (salary range) and schedule (flex work). Benefits? Not explicit; maybe we can infer but not stated. So we should not create Benefits section unless explicit. There's mention of "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." That's compensation but not benefits like health. The instruction says "Benefits" section only if posting actually states them. It does mention bonus plan and stock grants, which could be considered benefits. But ambiguous. Safer to not include Benefits unless explicit benefits like health, dental, 401k. I'd omit Benefits. We need sections: About the role (maybe from "About The Role"), Responsibilities (maybe from role description), Requirements (basic qualifications), Qualifications (maybe other qualifications?), Skills (maybe list of skills). However we need to avoid duplication. Let's extract substantive content. First, "About The Team": describes Workday Government, mission, etc. Could be considered "About the role"? Actually there is separate "About The Role". We'll treat "About The Team" as maybe part of "About the role"? But instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings. We have "About The Team" and "About The Role". Could combine into About the role? Probably "About The Role" is the role description. "About The Team" could be considered part of "About the role" or maybe we could treat as "About the role" includes team context. We'll include About the role heading and put content from both About The Team and About The Role (since both describe role/team). Ensure not to repeat job title. Next, Responsibilities: from "About The Role" we have responsibilities: architect and provide async messaging, streaming, NoSQL platforms; develop client libraries and SDKs; develop automation to deploy and run clusters; operate and tune clusters; design and build new capabilities; work hand in hand with application and service teams; improve services and encourage adoption; etc. Also from "About You" maybe responsibilities? Actually "About You" includes qualifications. We'll extract responsibilities. Requirements: Basic Qualification list (3+ years DevOps experience etc). Also maybe "Other Qualifications" could be considered Requirements or Qualifications. We'll separate: Requirements = Basic Qualification (must-haves). Qualifications = Other Qualifications (preferred). Skills maybe list of specific technologies: Python, Kubernetes/Docker, Terraform, Git, Jenkins, ArgoCD, Grafana, RESTful services, etc. Could be under Skills. Pay: salary range $123,900 - $222,000 USD. Schedule: Flexible work description: at least 50% time in office/field each quarter; freedom to create flexible schedule; remote home office roles also have opportunity to come together. We must not include boilerplate like EEO, legal, etc. We must not repeat job title as heading. We must not include Job ID/requisition numbers. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like "TS/SCI w/CI Poly", "US citizenship", "on site at client locations in DC, MD, VA (DMV) area", etc. Those are part of Requirements/Qualifications. We need to output only HTML fragment, no /, no markdown fences. Let's structure:

About the role

...combined text from About The Team and About The Role...

Responsibilities

• ... each responsibility as li

Requirements

• ... each basic qualification bullet

Qualifications

• ... other qualifications (preferred)

Skills

• ... list of specific technologies/tools

Pay

$123,900 USD - $222,000 USD annualized base salary range (primary location Reston, VA). Additional details: eligibility for Workday Bonus Plan, role-specific commission/bonus, annual refresh stock grants.

Schedule

Flexible work approach: at least 50% of time each quarter in office or field with customers/prospects/partners; freedom to create schedule; remote home office roles can come to offices for important moments.

We must ensure we don't include filler like "commensurate with experience". Not present. We need to verify we didn't miss any substantive info: The posting also mentions "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. May be required to be on site at client locations in the DC, MD, and VA (DMV) area." This is part of Requirements/Qualifications. Also "Software Development Engineer" is the job title; we shouldn't repeat as heading. Also "Basic Qualification" list includes many items; we need to capture each bullet. Let's extract Basic Qualification bullet points from text: "Software Development Engineer Basic Qualification 3 or more years of DevOps experience including Infrastructure automation, building CICD pipelines. Good in System design and writing comprehensive technical design docs Proficient in Python programming. Design, implement, and maintain robust DevOps pipelines for deploying, monitoring, and scaling machine learning runtime environment. Experience using technologies like Kubernetes/Docker to help developers scale their efforts in creating new and innovative products. Collaborate with other Machine Learning teams to improve not just the product, but efficiencies in engineering processes." That seems to be the basic qualification list. Then "Other Qualifications:" list includes many items: "specialty certification (e.g., CompTIA CySA+, GICSP, CASP+) Machine learning background. Experience with communication protocols, RESTful services, service-oriented architecture, distributed systems, and microservices. Building comprehensive monitoring services. Prior experience with enterprise SaaS products. Experience with monitoring tools like Grafana. Passion for creating and maintaining documentation and fixing run books. Availability for on-call support on a rotating basis. Proficiency in infrastructure automation tools like Terraform, implementing CI/CD pipelines using Git and Jenkins, and applying continuous deployment tool such as ArgoCD BS/MS in Computer Science or a related technical field. Excellent problem-solving skills with a focus on creating and maintaining accurate documentation. Experience in leading or mentoring other team members and proven team collaboration experience, i.e. understanding group dynamics, effective communication strategies, conflict resolution techniques, and the ability to foster a positive and inclusive team. Preferred DoD 8570/8140 compliant with at least IAT Level II certification, including a current Computing Environment (CE) credential and one approved" Then later there is a repeat for "Sr. Software Development Engineer Basic Qualification" which seems like a duplicate but with more details: "5 or more years of DevOps experience..." etc. Actually there is a section that repeats similar content but with Sr. level. It includes both basic and other qualifications again. We need to preserve all substantive info, not summarize away detail. So we need to include both sets? The posting seems to have two qualification sections: one for Software Development Engineer (maybe junior) and one for Sr. Software Development Engineer. The content overlaps but there are differences: years of experience (3+ vs 5+), etc. We should include both as part of Requirements/Qualifications? Might be confusing but we must preserve all detail. We could combine them under Requirements (must-haves) and Qualifications (preferred) but we need to not lose the distinction of years. We could treat the first "Basic Qualification" as Requirements (3+ years DevOps etc). The second "Sr. Software Development Engineer Basic Qualification" could be considered as Requirements for senior level (5+ years). Since both are present, we should include both bullet points. Similarly, the "Other Qualifications" appears twice (once after first basic, once after second). They are largely same but with some ordering differences. We'll include all bullets, maybe deduplicate identical lines? But we must not invent or summarize away detail; deduplication could be considered summarizing? It's okay to avoid duplicate lines if they are exactly same; but we need to be careful. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Removing exact duplicates could be considered summarizing away detail? It's removing redundancy but not losing information. I think it's acceptable to avoid duplicate identical lines; but safer to keep them as they appear, even if duplicate. However that would cause repetitive content. Might be okay but could be considered noisy. I'd deduplicate identical bullets to keep concise but still preserve all unique info. The instruction says do not summarize away detail; deduplication is not summarizing, it's removing redundancy. I'd keep unique bullets. Let's extract unique bullets from both Basic Qualification sections: First set (3+ years): - 3 or more years of DevOps experience including Infrastructure automation, building CICD pipelines. - Good in System design and writing comprehensive technical design docs - Proficient in Python programming. - Design, implement, and maintain robust DevOps pipelines for deploying, monitoring, and scaling machine learning runtime environment. - Experience using technologies like Kubernetes/Docker to help developers scale their efforts in creating new and innovative products. - Collaborate with other Machine Learning teams to improve not just the product, but efficiencies in engineering processes. Second set (5+ years Sr): - 5 or more years of DevOps experience including Infrastructure automation, building CICD pipelines. - Good in System design and writing comprehensive technical design docs - Proficient in Python programming. - Design, implement, and maintain robust DevOps pipelines for deploying, monitoring, and scaling machine learning runtime environment. - Experience using technologies like Kubernetes/Docker to help developers scale their efforts in creating new and innovative products. - Collaborate with other Machine Learning teams to improve not just the product, but efficiencies in engineering processes. - Other Qualifications: specialty certification (e.g., CompTIA CySA+, GICSP, CASP+) - Machine learning background. - Experience with communication protocols, RESTful services, service-oriented architecture, distributed systems, and microservices. - Building comprehensive monitoring services. - Prior experience with enterprise SaaS products. - Experience with monitoring tools like Grafana. - Passion for creating and maintaining documentation and fixing run books. - Availability for on-call support on a rotating basis. - Proficiency in infrastructure automation tools like Terraform, implementing CI/CD pipelines using Git and Jenkins, and applying continuous deployment tool such as ArgoCD - BS/MS in Computer Science or a related technical field. - Excellent problem-solving skills with a focus on creating and maintaining accurate documentation. - Experience in leading or mentoring other team members and proven team collaboration experience, i.e. understanding group dynamics, effective communication strategies, conflict resolution techniques, and the ability to foster a positive and inclusive team. - Preferred DoD 8570/8140 compliant with at least IAT Level II certification, including a current Computing