Staff Software Engineer - Back End
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive info, no boilerplate like EEO, navigation, cookie, legal, scam warning, application instructions, duplicated lines. Remove "To learn more about working at Ad Hoc, please visit: ..." and the equal opportunity statement, etc. Also remove the link at end "Job Reference". Also remove "Our recruiters will be happy to answer any questions..." maybe that's application instruction? It's about salary questions; might be considered application instruction? Probably remove.
We need to include Pay section with range $130,000 - $160,000.
We need to include Benefits section with list: Company-subsidized health, dental, and vision insurance; Flexible PTO; 401K with employer match; Paid parental leave after one year of service; Employee Assistance Program.
We need to include About the role? There's "About The Program" which describes role context. Could use heading "About the role" or "About The Program". The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those exact headings. For this posting, we have "About The Program" which is similar to About the role. We'll use About the role
and put the paragraph(s) from About The Program.
Responsibilities: Use Primary Responsibilities heading? The instruction says Responsibilities. We'll use Responsibilities
and list the bullet points from Primary Responsibilities Include.
Requirements/Qualifications: We have Basic Qualifications and Preferred Qualifications. Could combine into Requirements? But we have separate headings Qualifications and Skills maybe. The instruction list includes Qualifications, Skills. We could put Basic Qualifications under Qualifications
and Preferred Qualifications under Skills
or maybe under Qualifications as well. But we need to follow instruction: Prefer a few substantive sections over many thin ones. Could combine Basic and Preferred into Qualifications and Skills sections. Let's think: Basic Qualifications are mandatory; Preferred Qualifications are nice-to-have. Could put Basic under Qualifications, Preferred under Skills. That seems reasonable.
We need to ensure we don't create sections with filler like "commensurate with experience". Not present.
We need to preserve all substantive info: So we need to include all bullet points from Primary Responsibilities, Basic Qualifications, Preferred Qualifications, Benefits, Pay range, About the role paragraph.
We must not include duplicated lines. There's a duplicated "Primary Responsibilities" heading in text; we will output only once.
We must not include application instructions like "To learn more about working at Ad Hoc, please visit: ..." and the equal opportunity statement, etc.
We must not include Job ID.
We must not include the link "https://adhoc.team/" etc.
We must not include the sentence about recruiters answering salary questions.
We must not include the EEO statement.
We must not include the line about "In support of various state and city equal pay transparency laws..." maybe that's part of Pay? Actually it's about pay range disclosure. Could be considered part of Pay section? It's substantive about pay range. The instruction: include Pay section only if posting actually states them. It does state range and also mentions that actual compensation influenced by factors. That's part of pay info. We could include that as part of Pay section prose.
Thus Pay section: Pay
The range of starting pay for this role is $130,000 - $160,000. Actual compensation is influenced by a wide range of factors including but not limited to skill set, level of experience, and responsibility.
We must not include the line about "Our recruiters will be happy to answer any questions you may have, and we look forward to learning more about your salary requirements." That's application instruction-ish; remove.
Now Benefits: list.
Now About the role: we need to include the paragraph(s) from "About The Program". Let's extract:
"This role supports the Veterans Enrollment System Enrollment Eligibility (VESEE) program for the Department of Veterans Affairs (VA) Office of Information & Technology. These systems support Veteran health care eligibility and enrollment and serve more than 16,000 users across the Health Eligibility Center and VHA Office of Community Care. The program is actively modernizing a large, mission-critical enterprise Java application into a microservices-based architecture. This modernization is happening in phases, with several phases still ahead. You will join active, in-flight modernization work, building modern backend services while the legacy platform remains in production and continues to require enhancement and sustainment. The modern and legacy stacks coexist and interoperate, and this role will work across both environments to help move the platform forward while maintaining the reliability of systems Veterans depend on today."
We can put that in .
Now Responsibilities: list bullet points from "Primary Responsibilities Include". Let's capture each line:
- Design, develop, and maintain backend services within a microservices architecture using Java 17+, Spring Boot, JPA/Hibernate, and REST APIs
- Design and implement REST and SOAP-based services, including integrations between the modernized platform and existing systems
- Support the enhancement and sustainment of the legacy enterprise Java platform using technologies including Java, Spring Framework, Struts, JSP, EJB, JMS, WebLogic, Hibernate, and Oracle
- Analyze, troubleshoot, and resolve complex software defects and production issues across modern and legacy systems
- Develop and optimize SQL queries, data access patterns, and database integrations with Oracle
- Collaborate with architects and senior engineers on modernization initiatives, technical design, and implementation strategy
- Reduce technical ambiguity through clear documentation, thoughtful refactoring, automated testing, and improvements to existing systems
- Contribute to automated testing, CI/CD processes, application deployments, and overall engineering quality
- Participate actively in Agile ceremonies, including sprint planning, standups, reviews, and retrospectives, as well as planning and technical discussions with partners and key stakeholders
- Conduct code reviews, share technical knowledge, and mentor junior and mid-level engineers
- Plan and execute technical roadmaps and complex engineering work with minimal guidance from technical leadership
- Present technical topics effectively, clearly articulating implementation complexity, tradeoffs, risks, and costs to help inform business and technical decisions
- Communicate effectively about existing systems, design decisions, and program history in support of technical demonstrations, bid writing, and other client-facing activities
- Participate in technical interviews and help evaluate engineering candidates
- Periodically travel to collaborate with and present to clients, partners, and stakeholders
We need to put each as
- inside
.
Now Qualifications (Basic): list bullet points:
- Bachelor's degree in Computer Science, Software Engineering, Information Systems, or a related field and 10+ years of professional software development experience
- Relevant professional experience may be substituted for education
- 8+ years of hands-on Java development experience
- 5+ years of hands-on experience with Spring Framework and/or Spring Boot
- 5+ years of hands-on experience developing REST APIs and web services within a microservices architecture
- 5+ years of experience working with Oracle or another relational database
- Experience designing, developing, troubleshooting, and supporting production enterprise applications
- Experience working within Agile/Scrum development environments
- Experience using Git-based source control
- Strong troubleshooting, analytical, and problem-solving skills
- Strong verbal and written communication skills, with the ability to work directly with teammates, partners, and stakeholders in a distributed environment
Now Skills (Preferred): list bullet points:
- Experience with event-driven architectures and technologies such as Kafka
- Experience with caching technologies such as Redis
- Experience designing resilient external integrations using patterns such as circuit breakers, retry logic, timeout handling, and graceful failure
- Familiarity with legacy J2EE technologies such as Struts, JSP, EJB, JMS, and WebLogic
- Experience with containerized application development using Docker and Kubernetes
- Strong automated testing practices using tools such as JUnit and Mockito
- Experience modernizing or decomposing large monolithic applications into microservices
- Experience supporting environments where legacy and modernized architectures must operate concurrently
- Prior experience working in FedRAMP, FISMA, HIPAA, or similarly regulated environments
Now Benefits: list bullet points:
- Company-subsidized health, dental, and vision insurance
- Flexible PTO
- 401K with employer match
- Paid parental leave after one year of service
- Employee Assistance Program
Now Pay: as above.
Now we need to ensure we don't include any empty sections.
Now output HTML fragment only.
Let's craft:
About the role
...
Responsibilities
- ...
...
Qualifications
...
Skills
...
Benefits
...
Pay
...
Make sure no extra whitespace at start? It's fine.
Now double-check we didn't include any boilerplate like "Ad Hoc is a technology company..." etc. That's in the beginning but not part of sections; we omitted it because it's not under a heading we kept? Actually the initial paragraphs about Ad Hoc mission etc. Are they substantive? They describe company mission. Should we include them? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include that info somewhere. Where could we put? Possibly under About the role? But we already used that for program description. Could we add another section like "About Ad Hoc"? Not in the list of headings but we could still use About the company
? The instruction gave examples but not exclusive; we can use other headings if needed? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are typical but not strictly limited. However to be safe, we could incorporate the company description into About the role section as additional paragraph. That would preserve info.
Thus About the role section could have two paragraphs: first about Ad Hoc mission and remote culture etc., then about the program. Let's extract the relevant substantive paragraphs from the top:
- "This is a remote position." (maybe metadata but we can include as part of description)
- "JOB ID #936 Ad Hoc is a technology company that empowers organizations to deliver scalable, impactful digital services. Using modern, agile methods, our team creates products that meet people's needs and transform their experience of government."
- "Work on things that matter Our collaborations have shaped some of the defining moments in public-sector service delivery. We've helped build products that connect Veterans to tailored services, help millions access affordable health care, and support important programs like Head Start."
- "As we work with agencies to deliver critical services, we're also changing how the government approaches technology."
- "Built for a remote life Our culture, communications, and tools are built for remote work, enabling us to bring together top talent nationwide. At Ad Hoc, remote life empowers our teams to design work environments that fit their lives and that foster flexibility and collaboration to achieve positive outcomes for our customers."
- "Committed
for prose. We need to preserve all substantive info, no boilerplate like EEO, navigation, cookie, legal, scam warning, application instructions, duplicated lines. Remove "To learn more about working at Ad Hoc, please visit: ..." and the equal opportunity statement, etc. Also remove the link at end "Job Reference". Also remove "Our recruiters will be happy to answer any questions..." maybe that's application instruction? It's about salary questions; might be considered application instruction? Probably remove. We need to include Pay section with range $130,000 - $160,000. We need to include Benefits section with list: Company-subsidized health, dental, and vision insurance; Flexible PTO; 401K with employer match; Paid parental leave after one year of service; Employee Assistance Program. We need to include About the role? There's "About The Program" which describes role context. Could use heading "About the role" or "About The Program". The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those exact headings. For this posting, we have "About The Program" which is similar to About the role. We'll use About the role
and put the paragraph(s) from About The Program.
Responsibilities: Use Primary Responsibilities heading? The instruction says Responsibilities. We'll use Responsibilities
and list the bullet points from Primary Responsibilities Include.
Requirements/Qualifications: We have Basic Qualifications and Preferred Qualifications. Could combine into Requirements? But we have separate headings Qualifications and Skills maybe. The instruction list includes Qualifications, Skills. We could put Basic Qualifications under Qualifications
and Preferred Qualifications under Skills
or maybe under Qualifications as well. But we need to follow instruction: Prefer a few substantive sections over many thin ones. Could combine Basic and Preferred into Qualifications and Skills sections. Let's think: Basic Qualifications are mandatory; Preferred Qualifications are nice-to-have. Could put Basic under Qualifications, Preferred under Skills. That seems reasonable.
We need to ensure we don't create sections with filler like "commensurate with experience". Not present.
We need to preserve all substantive info: So we need to include all bullet points from Primary Responsibilities, Basic Qualifications, Preferred Qualifications, Benefits, Pay range, About the role paragraph.
We must not include duplicated lines. There's a duplicated "Primary Responsibilities" heading in text; we will output only once.
We must not include application instructions like "To learn more about working at Ad Hoc, please visit: ..." and the equal opportunity statement, etc.
We must not include Job ID.
We must not include the link "https://adhoc.team/" etc.
We must not include the sentence about recruiters answering salary questions.
We must not include the EEO statement.
We must not include the line about "In support of various state and city equal pay transparency laws..." maybe that's part of Pay? Actually it's about pay range disclosure. Could be considered part of Pay section? It's substantive about pay range. The instruction: include Pay section only if posting actually states them. It does state range and also mentions that actual compensation influenced by factors. That's part of pay info. We could include that as part of Pay section prose.
Thus Pay section: Pay
The range of starting pay for this role is $130,000 - $160,000. Actual compensation is influenced by a wide range of factors including but not limited to skill set, level of experience, and responsibility.
We must not include the line about "Our recruiters will be happy to answer any questions you may have, and we look forward to learning more about your salary requirements." That's application instruction-ish; remove. Now Benefits: list. Now About the role: we need to include the paragraph(s) from "About The Program". Let's extract: "This role supports the Veterans Enrollment System Enrollment Eligibility (VESEE) program for the Department of Veterans Affairs (VA) Office of Information & Technology. These systems support Veteran health care eligibility and enrollment and serve more than 16,000 users across the Health Eligibility Center and VHA Office of Community Care. The program is actively modernizing a large, mission-critical enterprise Java application into a microservices-based architecture. This modernization is happening in phases, with several phases still ahead. You will join active, in-flight modernization work, building modern backend services while the legacy platform remains in production and continues to require enhancement and sustainment. The modern and legacy stacks coexist and interoperate, and this role will work across both environments to help move the platform forward while maintaining the reliability of systems Veterans depend on today." We can put that in. Now Responsibilities: list bullet points from "Primary Responsibilities Include". Let's capture each line: - Design, develop, and maintain backend services within a microservices architecture using Java 17+, Spring Boot, JPA/Hibernate, and REST APIs - Design and implement REST and SOAP-based services, including integrations between the modernized platform and existing systems - Support the enhancement and sustainment of the legacy enterprise Java platform using technologies including Java, Spring Framework, Struts, JSP, EJB, JMS, WebLogic, Hibernate, and Oracle - Analyze, troubleshoot, and resolve complex software defects and production issues across modern and legacy systems - Develop and optimize SQL queries, data access patterns, and database integrations with Oracle - Collaborate with architects and senior engineers on modernization initiatives, technical design, and implementation strategy - Reduce technical ambiguity through clear documentation, thoughtful refactoring, automated testing, and improvements to existing systems - Contribute to automated testing, CI/CD processes, application deployments, and overall engineering quality - Participate actively in Agile ceremonies, including sprint planning, standups, reviews, and retrospectives, as well as planning and technical discussions with partners and key stakeholders - Conduct code reviews, share technical knowledge, and mentor junior and mid-level engineers - Plan and execute technical roadmaps and complex engineering work with minimal guidance from technical leadership - Present technical topics effectively, clearly articulating implementation complexity, tradeoffs, risks, and costs to help inform business and technical decisions - Communicate effectively about existing systems, design decisions, and program history in support of technical demonstrations, bid writing, and other client-facing activities - Participate in technical interviews and help evaluate engineering candidates - Periodically travel to collaborate with and present to clients, partners, and stakeholders We need to put each as
- .
Now Qualifications (Basic): list bullet points:
- Bachelor's degree in Computer Science, Software Engineering, Information Systems, or a related field and 10+ years of professional software development experience
- Relevant professional experience may be substituted for education
- 8+ years of hands-on Java development experience
- 5+ years of hands-on experience with Spring Framework and/or Spring Boot
- 5+ years of hands-on experience developing REST APIs and web services within a microservices architecture
- 5+ years of experience working with Oracle or another relational database
- Experience designing, developing, troubleshooting, and supporting production enterprise applications
- Experience working within Agile/Scrum development environments
- Experience using Git-based source control
- Strong troubleshooting, analytical, and problem-solving skills
- Strong verbal and written communication skills, with the ability to work directly with teammates, partners, and stakeholders in a distributed environment
Now Skills (Preferred): list bullet points:
- Experience with event-driven architectures and technologies such as Kafka
- Experience with caching technologies such as Redis
- Experience designing resilient external integrations using patterns such as circuit breakers, retry logic, timeout handling, and graceful failure
- Familiarity with legacy J2EE technologies such as Struts, JSP, EJB, JMS, and WebLogic
- Experience with containerized application development using Docker and Kubernetes
- Strong automated testing practices using tools such as JUnit and Mockito
- Experience modernizing or decomposing large monolithic applications into microservices
- Experience supporting environments where legacy and modernized architectures must operate concurrently
- Prior experience working in FedRAMP, FISMA, HIPAA, or similarly regulated environments
Now Benefits: list bullet points:
- Company-subsidized health, dental, and vision insurance
- Flexible PTO
- 401K with employer match
- Paid parental leave after one year of service
- Employee Assistance Program
Now Pay: as above.
Now we need to ensure we don't include any empty sections.
Now output HTML fragment only.
Let's craft:
- ... ...
About the role
...
Responsibilities
Qualifications
-
...
Skills
-
...
Benefits
-
...
Pay
...
Make sure no extra whitespace at start? It's fine. Now double-check we didn't include any boilerplate like "Ad Hoc is a technology company..." etc. That's in the beginning but not part of sections; we omitted it because it's not under a heading we kept? Actually the initial paragraphs about Ad Hoc mission etc. Are they substantive? They describe company mission. Should we include them? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include that info somewhere. Where could we put? Possibly under About the role? But we already used that for program description. Could we add another section like "About Ad Hoc"? Not in the list of headings but we could still use