Senior Software Engineer

We need to output HTML fragment with sections: About the role? The posting includes "About Agile Defense" description. That could be "About the role" or maybe "About Agile Defense". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections are present. We have: - About Agile Defense (company description) -> could be "About the role"? Actually "About the role" is generic; but we can put "About Agile Defense" as heading? The instruction says use headings like About the role, Responsibilities, etc. It doesn't forbid other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those exact headings if content exists. But we can also use other headings if appropriate? The examples are just examples; they didn't say we must only use those. But safer to stick to those headings. We have content: "Job Description" paragraph describing role. Could be "About the role". Then "Responsibilities" list. Then "Education Background" maybe "Qualifications". Then "Required Skills" and "Preferred Skills" maybe "Skills". Also "Working Conditions" maybe "Schedule"? Actually working conditions: Onsite twice a week in Rosslyn, VA. That's schedule/location. Could be "Schedule". Also "Clearance Level: Secret, Must Have Clearance to Start" maybe part of Requirements? Could be included in Qualifications. We need to preserve all substantive info, remove boilerplate: EEO, AI tools statement, etc. Also remove "Requisition #: 1888", "Job Title: Senior Software Engineer", location maybe part of schedule? But location is given: Hybrid, Rosslyn, VA. Could be in Schedule? Actually schedule is about onsite twice a week. Location is separate but we could include in a short p under maybe "About the role"? But we shouldn't create new headings not in list. Could embed location in a paragraph under About the role. We must not repeat job title as heading. So we won't have heading for Senior Software Engineer. We need to output only HTML fragment, no html/body tags. Let's structure:

About the role

... company description and job description ...

Then

Responsibilities

• ... list items ...

Then

Qualifications

Education: High School Diploma or equivalent (GED) required.

Experience: 4+ years of experience.

Clearance: Secret clearance required to start.

Then

Skills

• Required Skills: ...
• Preferred Skills: ...

maybe separate lists? Could combine. But we need to preserve details: Required Skills: Hands-on experience with Java and Spring Boot; Background designing and implementing RESTful APIs; Proficiency with core AWS services. Preferred Skills: Experience in fast-paced mission-focused environment collaborating with AI, DevSecOps, data engineering, platform engineering, cybersecurity; Familiarity with frameworks and tools like Django, NATS, Kafka, Redis, ClickHouse, OpenTelemetry, OpenRouter, LiteLLM advantageous; Experience with any of those technologies; Prior experience with OpenFGA. We could split into two lists: Required Skills and Preferred Skills but heading Skills only one. Could have subheadings? Not allowed? Could use

to separate. Better:

Skills

Required: Hands-on experience with Java and Spring Boot; background designing and implementing RESTful APIs; proficiency with core AWS services.

Preferred: Experience in a fast-paced mission-focused environment collaborating with AI, DevSecOps, data engineering, platform engineering, and cybersecurity; familiarity with frameworks and tools like Django, NATS, Kafka, Redis, ClickHouse, OpenTelemetry, OpenRouter, and LiteLLM; prior experience with OpenFGA.

Then

Schedule

Hybrid role: onsite twice a week in Rosslyn, VA.

We should also include location maybe in schedule. We must not include Pay/Benefits sections because not present. We must not include empty sections. Check for any other substantive content: "Our Core Values" etc. That's boilerplate? It's about company culture but could be considered "About the role"? Might be considered fluff but it's substantive? It's describing culture; maybe we could include in About the role paragraph. It's not boilerplate like EEO; it's about values. Could keep. But we need to preserve ALL substantive information; not invent or summarize away detail. So we should include the core values description? It's lengthy but it's part of posting. It's not boilerplate like EEO; it's specific to Agile Defense. So we should include it. Thus About the role paragraph should include the company vision paragraph, the job description paragraph, and maybe core values. Let's extract: About Agile Defense paragraph: "At Agile Defense we know that action defines the outcome and new challenges require new solutions. That’s why we always look to the future and embrace change with an unmovable spirit and the courage to build for what comes next. Our vision is to bring adaptive innovation to support our nation's most important missions through the seamless integration of advanced technologies, elite minds, and unparalleled agility—leveraging a foundation of speed, flexibility, and ingenuity to strengthen and protect our nation’s vital interests." Job Description: "In this role, you will build distributed backend services and durable APIs that support a modern Hub‑and‑Spoke architecture. Your work will play a key role in advancing operational AI, enabling mission systems, enterprise governance, agentic AI, and scalable delivery. Senior Software Engineer Contribute to development and supporting tools, writing clean, maintainable code under guidance of senior engineers. Design, develop, and maintain backend microservices and distributed systems to support enterprise AI operations. You will be responsible for building and maintaining microservices that integrate seamlessly with cloud-native platforms, ensuring continuous monitoring and high reliability across all operational workflows. Build and optimize APIs and event-driven architectures for scalable and reliable data flow." Then later "Our Core Values Employees of Agile Defense are our number one priority, and the importance we place on our culture here is fundamental. Our culture is alive and evolving, but it always stays true to its roots. Here, you are valued as a family member, and we believe that we can accomplish great things together. Agile Defense has been highly successful in the past few years due to our employees and the culture we create together. What makes us Agile? We call it the 6Hs, the values that define our culture and guide everything we do. Together, these values infuse vibrancy, integrity, and a tireless work ethic into advancing the most important national security and critical civilian missions. It's how we show up every day. It's who we are. Happy - Be Infectious. Happiness multiplies and creates a positive and connected environment where motivation and satisfaction have an outsized effect on everything we do. Helpful - Be Supportive. Being helpful is the foundation of teamwork, resulting in a supportive atmosphere where collaboration flourishes, and collective success is celebrated. Honest - Be Trustworthy. Honesty serves as our compass, ensuring transparent communication and ethical conduct, essential to who we are and the complex domains we support. Humble - Be Grounded. Success is not achieved alone, humility ensures a culture of mutual respect, encouraging open communication, and a willingness to learn from one another and take on any task. Hungry - Be Eager. Our hunger for excellence drives an insatiable appetite for innovation and continuous improvement, propelling us forward in the face of new and unprecedented challenges. Hustle - Be Driven. Hustle is reflected in our relentless work ethic, where we are each committed to going above and beyond to advance the mission and achieve success." We could include that as part of About the role. Now ensure we removed boilerplate: "Requisition #: 1888 Job Title: Senior Software Engineer Location: Hybrid, Rosslyn, VA Clearance Level: Secret, Must Have Clearance to Start" we folded clearance into Qualifications, location into Schedule, requisition and job title removed. Also remove "Equal Opportunity Employer/Protected Veterans/Individuals with Disabilities We may use artificial intelligence (AI) tools..." etc. Now produce HTML. Make sure to use

for each section heading. Let's craft:

About the role

At Agile Defense we know that action defines the outcome and new challenges require new solutions. That’s why we always look to the future and embrace change with an unmovable spirit and the courage to build for what comes next. Our vision is to bring adaptive innovation to support our nation's most important missions through the seamless integration of advanced technologies, elite minds, and unparalleled agility—leveraging a foundation of speed, flexibility, and ingenuity to strengthen and protect our nation’s vital interests. In this role, you will build distributed backend services and durable APIs that support a modern Hub‑and‑Spoke architecture. Your work will play a key role in advancing operational AI, enabling mission systems, enterprise governance, agentic AI, and scalable delivery. Contribute to development and supporting tools, writing clean, maintainable code under guidance of senior engineers. Design, develop, and maintain backend microservices and distributed systems to support enterprise AI operations. You will be responsible for building and maintaining microservices that integrate seamlessly with cloud-native platforms, ensuring continuous monitoring and high reliability across all operational workflows. Build and optimize APIs and event-driven architectures for scalable and reliable data flow. Employees of Agile Defense are our number one priority, and the importance we place on our culture here is fundamental. Our culture is alive and evolving, but it always stays true to its roots. Here, you are valued as a family member, and we believe that we can accomplish great things together. Agile Defense has been highly successful in the past few years due to our employees and the culture we create together. What makes us Agile? We call it the 6Hs, the values that define our culture and guide everything we do. Together, these values infuse vibrancy, integrity, and a tireless work ethic into advancing the most important national security and critical civilian missions. It's how we show up every day. It's who we are. Happy - Be Infectious. Happiness multiplies and creates a positive and connected environment where motivation and satisfaction have an outsized effect on everything we do. Helpful - Be Supportive. Being helpful is the foundation of teamwork, resulting in a supportive atmosphere where collaboration flourishes, and collective success is celebrated. Honest - Be Trustworthy. Honesty serves as our compass, ensuring transparent communication and ethical conduct, essential to who we are and the complex domains we support. Humble - Be Grounded. Success is not achieved alone, humility ensures a culture of mutual respect, encouraging open communication, and a willingness to learn from one another and take on any task. Hungry - Be Eager. Our hunger for excellence drives an insatiable appetite for innovation and continuous improvement, propelling us forward in the face of new and unprecedented challenges. Hustle - Be Driven. Hustle is reflected in our relentless work ethic, where we are each committed to going above and beyond to advance the mission and achieve success.

Responsibilities

• Implement API endpoints and business logic for wrapper service
• Develop features for OpenFGA data model management
• Write unit tests and integration tests
• Debug and resolve software defects
• Assist with documentation and code examples
• Participate in code reviews and team ceremonies
• Support onboarding team with technical questions
• Contribute to CI/CD pipeline improvements