Senior Microservices Engineer

We need to output HTML fragment with sections: headings

for each section present: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. We need to parse the job description. Given content: It starts with "ACTIVE SECURITY CLEARANCE AT THE TS/SCI POLYGRAPH LEVEL IS REQUIRED". Then description: "We are seeking a versatile, mission-driven Senior Java Developer...". Then details about role: design, build, deploy robust back-end microservices and APIs using Java, dependency injection (Guice), modern containerization. Manage Git workflows, automating builds with Gradle, containerizing with Docker, developing RESTful services. Working directly in customer spaces or offsite SCIF environments, collaborate with cross-functional teammates and occasionally lend skills to limited-scope front-end UI enhancements. Then salary: "The annual base salary range for this role is $201,000-$238,000 (USD) , which does not include discretionary bonus compensation or our comprehensive benefits package. Actual compensation offered to the successful candidate may vary from posted hiring range based upon geographic location, work experience, education, and/or skill level, among other things." Then "Required Skills" list: Core Java & Modern Architecture..., Build & Version Control Systems..., Containerization & Deployment..., Linux Proficiency..., SCIF / On-Site Operations..., Education: Bachelor’s Degree ... OR High School Diploma / GED, PLUS 18+ years... Then "Desired Skills": Data & Search Technologies..., Orchestration & Infrastructure Automation..., Full-Stack / UI Capability... Then "About Nyla Technology Solutions": description. Then "Taking Care of All of You": benefits description: Nyla FLEX program details: PAY, LEAVE, SCHEDULE, other benefits: health care 100% covered, 10% 401k matching, Professional Development $5k per year, student loan repayment program, 8 hours volunteering annually. We need to produce sections: About the role (maybe a brief paragraph summarizing role), Responsibilities (list of duties), Requirements (maybe required skills?), Qualifications (education/experience), Skills (maybe desired skills?), Benefits, Pay, Schedule. We must not repeat job title as heading. Must not include Job ID etc. Must not include boilerplate like EEO etc. Must not include navigation/cookie etc. Must not include duplicated lines. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting. We need to decide which sections to include based on content. We have content for: - About the role: maybe the introductory paragraph describing the role: "We are seeking a versatile, mission-driven Senior Java Developer to join a high-impact, tight-knit team dedicated to delivering critical defense tech solutions. In this role, you will design, build, and deploy robust back-end microservices and APIs using Java, dependency injection (Guice), and modern containerization. You will work across the full software lifecycle—managing Git workflows, automating builds with Gradle, containerizing applications with Docker, and developing reliable RESTful services. Working directly in customer spaces or offsite SCIF environments, you will collaborate closely with cross-functional teammates and occasionally lend your skills to limited-scope front-end UI enhancements to drive end-to-end operational success." That's about the role. - Responsibilities: Could be the list of duties: design, build, deploy microservices; manage Git workflows; automate builds with Gradle; containerize with Docker; develop RESTful services; work in customer spaces/SCIF; collaborate; occasional front-end UI enhancements. - Requirements: maybe the required skills list (Core Java & Modern Architecture, Build & Version Control Systems, Containerization & Deployment, Linux Proficiency, SCIF/On-Site Operations, Education). Could be considered requirements. - Qualifications: maybe the education/experience specifics: Bachelor's degree plus 14+ years OR HS/GED plus 18+ years. Could be separate. - Skills: maybe desired skills list (ELK stack, MongoDB, Kubernetes, Ansible, Angular/TypeScript, willingness for UI tasks). - Benefits: Nyla FLEX program details: PAY, LEAVE, SCHEDULE, health care, 401k matching, professional development, student loan repayment, volunteering. - Pay: The salary range: $201,000-$238,000 base, plus discretionary bonus not included, actual compensation may vary. - Schedule: The Nyla FLEX schedule details: ability to scale down to 30-32 hours while still enjoying benefits. We must not create sections with filler like "commensurate with experience". We have actual content for Pay and Schedule. We must not repeat job title as heading. We must not include Job ID/requisition numbers. We must not include boilerplate like equal opportunity employer. We must output only HTML fragment. Thus produce something like:

About the role

We are seeking a versatile, mission-driven Senior Java Developer to join a high-impact, tight-knit team dedicated to delivering critical defense tech solutions. In this role, you will design, build, and deploy robust back-end microservices and APIs using Java, dependency injection (Guice), and modern containerization. You will work across the full software lifecycle—managing Git workflows, automating builds with Gradle, containerizing applications with Docker, and developing reliable RESTful services. Working directly in customer spaces or offsite SCIF environments, you will collaborate closely with cross-functional teammates and occasionally lend your skills to limited-scope front-end UI enhancements to drive end-to-end operational success.

Responsibilities

• Design, build, and deploy robust back-end microservices and APIs using Java, dependency injection (Guice), and modern containerization.
• Manage Git workflows and automate builds with Gradle.
• Containerize applications with Docker and develop reliable RESTful services.
• Work in customer spaces or offsite SCIF environments.
• Collaborate closely with cross-functional teammates.
• Occasionally contribute to limited-scope front-end UI enhancements.

Requirements

• Deep hands‑on experience in Java development, object‑oriented design, RESTful web services, and dependency injection frameworks (e.g., Guice or Spring).
• Expertise with Git version control workflows and automated build tools such as Gradle or Maven.
• Solid experience containerizing applications using Docker and deploying services within container environments.
• Strong operational command‑line skills in Linux environments for application configuration, debugging, and system administration.
• Flexibility and willingness to work collaboratively in customer spaces or offsite SCIF locations.
• Education: Bachelor’s Degree in Computer Science, Computer Engineering, Software Engineering, or a related technical discipline, PLUS 14+ years of professional software development experience OR High School Diploma / GED, PLUS 18+ years of hands‑on technical software engineering experience in lieu of a degree.

Qualifications

The role requires either a Bachelor’s degree in a relevant technical field with 14+ years of experience, or a High School Diploma/GED with 18+ years of hands‑on technical software engineering experience.

But we might be duplicating education info. Could combine Requirements and Qualifications. However we need to avoid thin sections. Perhaps we can merge education into Requirements and not have separate Qualifications. But the instruction says we can include sections only when posting has real specific content. It does not forbid overlapping content. But better to avoid duplication. We have Required Skills list (which includes education). That could be considered Requirements. Then Desired Skills list could be Skills. Thus we may not need a separate Qualifications section. However the instruction lists possible headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose to include only those we have content for. We have content for About the role, Responsibilities, Requirements (required skills), Skills (desired skills), Benefits, Pay, Schedule. We may omit Qualifications if we feel it's redundant. But we need to ensure we preserve all substantive information. The education/experience requirement is in Required Skills list; we have included that. So Qualifications not needed. Now Benefits: we need to capture Nyla FLEX program details: PAY, LEAVE, SCHEDULE, health care, 401k matching, professional development $5k per year, student loan repayment, 8 hours volunteering. We also have separate Pay and Schedule sections; but the Benefits section already includes PAY, LEAVE, SCHEDULE details. However the instruction says: "Prefer a few substantive sections over many thin ones." And we must not create Pay/Schedule/Benefits sections unless posting actually states them. The posting does state Pay, Leave, Schedule details within the benefits description. It also states the base salary range separately. So we have both a general benefits description and explicit Pay and Schedule details. We could combine them into a Benefits section that includes pay, leave, schedule, other benefits. But the instruction also says we can have separate Pay and Schedule sections if posting actually states them. It does state Pay (salary range) and Schedule (flex schedule). So we could have separate Pay and Schedule sections, and Benefits section for other benefits (health care, 401k, professional development, student loan, volunteering). However the posting also mentions PAY, LEAVE, SCHEDULE as part of Nyla FLEX program. So we could treat those as part of Benefits, but we also have separate Pay and Schedule sections for salary range and flexible schedule details. Might be okay. We need to avoid duplication: If we put Pay section with salary range, and Benefits section also includes PAY details (like 4 weeks annual leave etc.) that might duplicate. But we can keep Benefits section focusing on non-pay benefits: health care, 401k matching, professional development, student loan repayment, volunteering. And Pay section for salary range and maybe mention discretionary bonus. Schedule section for flexible schedule details (30-32 hours, etc.). Leave details could be part of Benefits or Schedule? The posting mentions LEAVE under Nyla FLEX: ability to buy additional annual leave etc. That could be part of Benefits or maybe Schedule? Since it's about leave, could be part of Benefits. But we already have Schedule section for work hours. Might be better to have Benefits include health care, 401k, professional development, student loan, volunteering, and leave details (since it's a benefit). However the instruction says we should not create Pay/Schedule/Benefits sections unless posting actually states them. It does state Leave details, so we could include a Leave section? But not in the list of allowed headings. The allowed headings list includes Benefits, Pay, Schedule. No separate Leave heading. So we should incorporate leave details into Benefits or Schedule. Since leave is a benefit, we can put it under Benefits. Thus Benefits section will include: Nyla FLEX program details: 4 weeks annual leave + 11 holidays + additional day per year, ability to cash out annual leave, opt out of other benefits, arrange additional hours on contract, option to earn 1.3x hourly after 1880 hours; ability to buy additional annual leave for total 6 weeks (240 hours) plus 11 holidays; paid anniversary leave; health care 100% covered; 10% 401k matching with full vesting day 1; Professional Development $5k per year; student loan repayment program; 8 hours volunteering annually. Pay section: base salary range $201,000-$238,000 USD, does not include discretionary bonus, actual compensation may vary based on location,