Senior Java Application Developer

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 posting. First, location and clearance: "Location This is a hybrid role requiring 3 days per week on site in Tysons Corner, VA Clearance U.S. Citizenship is required; must be able to obtain an ICE Public Trust clearance". This is metadata; we can fold into a short

maybe under About the role? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include a paragraph with location and clearance. Then "Summary Dev Technology Group is seeking a Senior Application Developer ...". That's about the role. So we can have

About the role

with paragraphs summarizing. Then "What You'll Be Doing" list of duties: we can put under

Responsibilities

with

• . Then "Required Education, Experience, and Skills:" list of required items. That's requirements/qualifications/skills. We need to decide sections: maybe

  Requirements

  for required education/experience, and

  Skills

  for technical skills? Or combine. The instruction: prefer a few substantive sections over many thin ones. Could have Requirements (education/experience) and Skills (technical). Also Preferred Education, Experience, and Skills could be under Preferred Qualifications maybe as a separate section? Could be under Qualifications? But we have to avoid filler. Preferred section has content: AWS certifications, Section 508, AWS Cloud, Serverless, etc. That's substantive. Could be under

  Preferred Qualifications

  . But allowed headings list includes Qualifications (maybe for both required and preferred). However we can still use Qualifications heading and include both required and preferred? Might be mixing. Better to have separate sections: Requirements (required) and Preferred Qualifications (preferred). The allowed headings list includes Qualifications (generic). Could use that for both required and preferred? But we need to differentiate. Could use Requirements for required, and Qualifications for preferred? Or Skills for technical skills. Let's think. We have required education/experience and required skills list. Preferred includes certifications, AWS, etc. Could put required under Requirements, preferred under Qualifications, and maybe Skills separate? But we have many technical skills in required list (Java, Spring, etc.) That's also skills. Could combine required education/experience and skills under Requirements. Then preferred under Qualifications. Then Benefits: we have a paragraph about benefits under "Who We Are" describing benefits: generous time-off, flexible schedules, career dev, tuition reimbursement, industry-leading benefits (health plans, dental, vision, FSA, commuter, life insurance, 401K matching, social events, community engagement). That's substantive. So we can have Benefits section. Pay: we have salary range: $100,000 - $145,000. That's specific. So we can have Pay section. Schedule: we have hybrid role requiring 3 days per week on site in Tysons Corner, VA. That's schedule info. So we can have Schedule section. Thus sections: About the role, Responsibilities, Requirements, Qualifications (preferred), Benefits, Pay, Schedule. Possibly also Skills? But we already covered skills in Requirements. Could also have Skills separate but might be thin. Let's keep Requirements covering education/experience and required technical skills. Qualifications covering preferred. Now we need to strip boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. At end there is "Equal Opportunity Employer / Individuals with Disabilities / Protected Veterans Dev Technology Group operates in the following states: ..." That's EEO boilerplate; remove. Also "To learn more about working at Dev Technology, visit Working At Dev Technology Group" maybe promotional; could be considered boilerplate? It's not EEO but maybe still promotional; but it's not required. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. That line is not exactly those but could be considered promotional; but we can keep if it's substantive? It's just a link to learn more; not substantive about job. Safer to remove. Also "Who We Are" paragraph includes description of company and benefits; we already extracted benefits. The rest of Who We Are description about Dev Technology being growing IT company etc. Could be considered boilerplate? It's not required but maybe we can keep as part of About the role? But we already have About the role summary. The Who We Are includes mission etc. Could be considered extra but not required. Might be okay to keep as part of About the role? But we already have summary. To avoid duplication, we could incorporate relevant parts into About the role. However we must preserve ALL substantive information; we cannot invent or summarize away detail. So we need to keep the details from Who We Are that are not already covered. The Who We Are includes: "Dev Technology is a growing IT company with an employee-centric culture that works on mission-critical projects for the federal government. We partner with our federal customers to deliver technology services and solutions, and to drive our client’s missions forward through innovation. We use Agile and DevSecOps principles to provide services including application development, biometrics and identity management, cloud and infrastructure optimization, IT and legacy modernization, and data management. As a Washington Post Top Workplace award winner for the past THIRTEEN years in a row, the Top Workplaces USA for the past five years, and a recipient of the Companies As Responsive Employers (CARE) Award for the past six years, Dev Technology employees enjoy: ..." Then benefits list. We already captured benefits list. The preceding sentences about company culture, mission, services, awards are substantive about the employer. Should we keep them? They are not directly about the role but provide context. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that info. Where to place? Could be part of About the role (maybe as a second paragraph). Or we could have a separate section "About the company". But allowed headings list does not include About the company. Could fold into About the role as extra paragraph. That seems okay. Thus About the role will have: summary paragraph from "Summary Dev Technology Group is seeking..." plus the Who We Are description (excluding benefits which we will list separately). Ensure not to duplicate benefits. Now Responsibilities: list from "What You'll Be Doing". We'll extract each bullet. Now Requirements: required education/experience and required skills list. We'll need to parse. Required Education, Experience, and Skills: bullet list after colon? Actually it's a paragraph: "Bachelor’s degree in computer science, engineering, or a related field with five (5) or more years of relevant experience in an Enterprise IT environment OR in lieu of a degree seven (7) or more years of relevant experience in an Enterprise IT environment Java web applications and associated frameworks Spring Framework Legacy Java Server Pages and MVC-based application models JavaScript and/or JavaScript frameworks, such as Angular Experience with relational databases (e.g., Oracle, PostgreSQL) Experience writing and executing automated unit tests Experience in an automated development environment, using CI/CD tools such as Git, Jenkins, or SonarQube Understanding of DevSecOps and secure code practices Experience with software delivery using the Agile Scrum or Kanban methodology via Jira Excellent communication skills (both verbal and written) plus active listening skills to collaborate with a large cross-functional team" We need to turn into list items. Could split by sentences. Let's create
  • for each distinct requirement. We'll list: - Bachelor’s degree in computer science, engineering, or a related field with five (5) or more years of relevant experience in an Enterprise IT environment - OR in lieu of a degree, seven (7) or more years of relevant experience in an Enterprise IT environment - Experience with Java web applications and associated frameworks - Experience with Spring Framework - Experience with Legacy Java Server Pages and MVC-based application models - Experience with JavaScript and/or JavaScript frameworks, such as Angular - Experience with relational databases (e.g., Oracle, PostgreSQL) - Experience writing and executing automated unit tests - Experience in an automated development environment, using CI/CD tools such as Git, Jenkins, or SonarQube - Understanding of DevSecOps and secure code practices - Experience with software delivery using the Agile Scrum or Kanban methodology via Jira - Excellent communication skills (both verbal and written) plus active listening skills to collaborate with a large cross-functional team Now Preferred Education, Experience, and Skills: list after colon. "AWS certifications (e.g., AWS Certified Developer or Solutions Architect) Understanding of Section 508 accessibility and compliance Experience developing in and deploying to the AWS Cloud environment Experience with Serverless, AWS Lambda, Micro Frontend, Micro Backend services Experience with IBM MQ, Amazon MQ, or ActiveMQ Experience with Node.js or Python Experience working on a federal government project Experience using agentic AI tools such as Claude Code" We'll make list items. Now Benefits: from Who We Are after colon: "Generous and flexible time-off policy Flexible work schedules and telework options, including remote work availability for eligible projects Career development opportunities including a mentorship program, technical and management training through Dev University, hands-on learning through DevLab, tuition reimbursement, and paid training opportunities Industry-leading benefits including a choice of two health plans that include dental and vision, flexible spending account, commuter benefits, life insurance, and more 401K matching with a 5% matching contribution Regular team and company social events including our annual party, happy hours, fitness challenges, and more A focus on community engagement including company wide support activities, employer match for donations, and time off for volunteer efforts" We'll make list items. Pay: "$100,000 - $145,000". Also note disclaimer: "this presented salary range is not a guarantee of compensation or salary. Offered salary is based on experience, geographic location, and possibly contractual requirements as appropriate to the role. *Salary could fall outside of this range." We should include that as prose maybe. Schedule: hybrid role requiring 3 days per week on site in Tysons Corner, VA. Also location mention. We'll include that. Now About the role: combine summary and Who We Are description (excluding benefits). Let's extract Who Are description before benefits: "Dev Technology is a growing IT company with an employee-centric culture that works on mission-critical projects for the federal government. We partner with our federal customers to deliver technology services and solutions, and to drive our client’s missions forward through innovation. We use Agile and DevSecOps principles to provide services including application development, biometrics and identity management, cloud and infrastructure optimization, IT and legacy modernization, and data management. As a Washington Post Top Workplace award winner for the past THIRTEEN years in a row, the Top Workplaces USA for the past five years, and a recipient of the Companies As Responsive Employers (CARE) Award for the past six years, Dev Technology employees enjoy:" Then benefits list. So we will take the sentences before "Dev Technology employees enjoy:" as About the role content. Thus About the role paragraphs: - Summary paragraph: "Dev Technology Group is seeking a Senior Application Developer to support an Operations and Maintenance program that delivers enhancements and functionality across multiple web-based applications for a dynamic government customer. In this role, the Senior Application Developer will work closely with the Project Manager, Development Leads, incumbent team members, and customer stakeholders to intake customer-prioritized user stories and deliver high-quality solutions to production. The senior developer will be expected to independently manage complex development tasks, contribute to technical design and implementation, support peer developers, and help guide more junior team members. The ideal candidate will bring strong application development experience, sound technical judgment, and the ability to collaborate effectively in a fast-paced, mission-focused environment. This is an excellent opportunity to support mission-critical