JAVA/Spring Boot Engineer Senior
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Preserve all substantive information; do not invent or summarize away detail. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them. Prefer a few substantive sections over many thin ones.
We need to parse the posting.
Key content:
- Hybrid work: requires associates to be in-office 1-2 days per week, fostering collaboration, etc. Also note: Alternate locations may be considered if candidates reside within commuting distance from an office. Note about policy: candidates not within reasonable commuting distance will not be considered unless accommodation. Also note: PLEASE NOTE: This position is not eligible for current or future visa sponsorship.
- Role description: Engineer Senior responsible for delivery of end to end application, system development and maintenance on complex multi technology platforms within assigned client group, business unit or corporate department and utilizing various customer technology platforms.
- How You Will Make An Impact: bullet list of responsibilities (looks like a list). Let's extract bullet points:
Maintains active relationships with customers to determine business requirements and leads requirements gathering meetings.
Owns the change request process and may coordinate with other teams as necessary.
Provides technical advice and weighs in on technical decisions that impact cross functional teams.
Researches and may propose new technologies.
Develops and owns list of final enhancements.
Develops and defines application scope and objectives and prepares technical and/or functional specifications from with programs will be written.
Performs technical design reviews and code reviews.
May own technical testing to ensures unit test is completed and meets the test plan requirements, system testing is completed and system is implemented according to plan.
Assesses current status and supports data information planning.
Coordinates on-call support and ensures effective monitoring of system.
Maintains technical development environment.
Mentors others and may lead multiple or small to medium sized projects.
Will begin to set direction at the project/service level and influences decision-making.
Provides technical guidance, and mentoring.
Understands the tradeoffs between technical, analytical and product needs of the technical solutions.
Identifies and propose strategies around technical problems affecting team, communicates standards and gets buy-in on solutions.
Facilitates group sessions to elicit complex information on requirements clarification, design sessions, code reviews and troubleshooting issues. Supports vendor evaluation.
- Minimum Requirements: Requires a BA/BS degree in Information Technology, Computer Science or related field of study and a minimum of 5 years related experience; experience working with multi dimensional platforms, and business and technical applications also required; or any combination of education and experience, which would provide an equivalent background.
- Preferred Skills, Capabilities & Experiences: list:
Full Stack Java Developer with hands-on experience with Java 21, Spring, Spring Boot, WebSphere, and ORM frameworks (Hibernate, Spring DAO).
Intermediate proficiency with Oracle, RESTful web services design and development, JUnit, and SQL.
Experience working with multiple platform (Linux, Cloud(Azure))
Experience deploying applications to servers (preferably WebSphere) and working with CI/CD tools such as Checkmarx, SonarQube, and Artifactory.
Strong understanding of design patterns and their application throughout the development lifecycle.
Knowledge of microservices architecture and performance optimization techniques.
Experience mentoring others, leading multiple small projects and providing troubleshooting support is preferred.
Facets Provider domain knowledge preferred.
Familiarity with AI-assisted development tools (e.g., GitHub Copilot, Windsurf) preferred.
- Salary: For candidates working in person or virtually in the below location(s), the salary* range for this specific position is $120,080 to $180,120. Locations: Virginia
- Benefits: In addition to your salary, Elevance Health offers benefits such as a comprehensive benefits package, incentive and recognition programs, equity stock purchase and 401k contribution (all benefits are subject to eligibility requirements).
- Additional details about salary: The salary offered for this specific position is based on a number of legitimate, non-discriminatory factors set by the Company... etc. This is more boilerplate about salary determination. Might be considered part of Pay section? The instruction: include Pay section only if posting actually states them. It does state salary range and location. So we can include Pay section with that info. Also Benefits section: they mention benefits package etc. So we can include Benefits.
- Schedule: The posting mentions hybrid: requires associates to be in-office 1-2 days per week. That's schedule info. So we can include Schedule section with that detail.
- About the role: maybe we can have an "About the role" section summarizing the role description (Engineer Senior responsible for delivery...). Could be a paragraph.
- Responsibilities: we have the "How You Will Make An Impact" list. That's responsibilities.
- Requirements: Minimum Requirements.
- Qualifications: maybe combine Minimum Requirements and Preferred Skills? But we have separate sections: Requirements (minimum) and Qualifications (preferred). The instruction: use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have Requirements for minimum, Qualifications for preferred? Or Skills for preferred skills. The list includes "Preferred Skills, Capabilities & Experiences". That could go under Skills or Qualifications. We need to decide.
We should avoid thin sections. Perhaps combine Requirements and Qualifications into one? But we have headings list; we can choose to include only those with substantive content. Let's see:
- About the role: we have a paragraph describing role. Good.
- Responsibilities: we have bullet list. Good.
- Requirements: we have minimum requirements (degree + 5 years). Good.
- Qualifications: we could put preferred skills under Qualifications, or Skills. The instruction includes Skills as a possible heading. Since the preferred list is about skills, we could use Skills heading. Qualifications could be for education/experience? But we already used Requirements for that. Maybe we can put preferred skills under Skills, and keep Qualifications empty? Better to not create empty heading. So we could use Skills heading for the preferred skills list. Then we might not need Qualifications heading. Or we could put both minimum and preferred under Requirements and Qualifications respectively. Let's examine: The posting has "Minimum Requirements" and "Preferred Skills, Capabilities & Experiences". So we can map Minimum Requirements to Requirements heading, and Preferred Skills to Skills heading. That seems appropriate. Qualifications heading could be omitted if no distinct qualifications beyond those. But we could also put education/experience under Qualifications and skills under Skills. However we already have degree+experience under Minimum Requirements. That could be considered qualifications. But to avoid thin sections, we can combine: Requirements heading for minimum requirements (degree+experience) and Skills heading for preferred skills. That's two sections.
- Benefits: we have benefits paragraph. Good.
- Pay: we have salary range and location. Good.
- Schedule: we have hybrid schedule (1-2 days in office). Good.
Thus we will output sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule.
We need to use
for each section heading. Then content:
for prose,
- for lists.
We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate like EEO, legal, etc. Also remove duplicated lines, application instructions, etc.
We need to preserve all substantive information. Let's extract substantive info:
About the role: "Engineer Senior is responsible for delivery of end to end application, system development and maintenance on complex multi technology platforms within assigned client group, business unit or corporate department and utilizing various customer technology platforms." Also maybe mention hybrid work? But that's schedule. Could also mention that this role requires associates to be in-office 1-2 days per week fostering collaboration etc. That's schedule. So About the role can be just the description of role responsibilities high-level.
Responsibilities: list of bullet points as above.
Requirements: "Requires a BA/BS degree in Information Technology, Computer Science or related field of study and a minimum of 5 years related experience; experience working with multi dimensional platforms, and business and technical applications also required; or any combination of education and experience, which would provide an equivalent background."
Skills: list of preferred skills as above.
Benefits: "In addition to your salary, Elevance Health offers benefits such as a comprehensive benefits package, incentive and recognition programs, equity stock purchase and 401k contribution (all benefits are subject to eligibility requirements)." Also maybe mention other benefits from later paragraph: "We offer a range of market-competitive total rewards that include merit increases, paid holidays, Paid Time Off, and incentive bonus programs (unless covered by a collective bargaining agreement), medical, dental, vision, short and long term disability benefits, 401(k) +match, stock purchase plan, life insurance, wellness programs and financial education resources, to name a few." That's also benefits. Should we include that? It's substantive. The posting includes that under "How We Work". It's part of benefits description. So we should include that as part of Benefits section. Combine both.
Pay: "For candidates working in person or virtually in the below location(s), the salary* range for this specific position is $120,080 to $180,120. Locations: Virginia". Also maybe note that salary offered based on factors etc. That's more detail about salary determination. Could include as prose. But we must avoid filler like "The salary offered for this specific position is based on a number of legitimate, non-discriminatory factors set by the Company." That is substantive but maybe considered boilerplate? It's still info about salary determination. The instruction: do not create Pay section unless posting actually states them. It does state salary range. The additional sentences about salary determination are also part of posting. Should we include them? They are not filler like "commensurate with experience". They are specific. I'd include them as part of Pay section prose.
Schedule: "This role requires associates to be in-office 1 - 2 days per week, fostering collaboration and connectivity, while providing flexibility to support productivity and work-life balance. This approach combines structured office engagement with the autonomy of virtual work, promoting a dynamic and adaptable workplace. Alternate locations may be considered if candidates reside within a commuting distance from an office. Please note that per our policy on hybrid/virtual work, candidates not within a reasonable commuting distance from the posting location(s) will not be considered for employment, unless an accommodation is granted as required by law." Also note about visa sponsorship: "PLEASE NOTE: This position is not eligible for current or future visa sponsorship." That's not schedule but maybe a note. Could be included in About the role or a separate note? It's not schedule. Could be included in About the role or maybe a separate section like "Additional notes". But we should not create a section unless we have substantive content. Could add a short paragraph under About the role or maybe under Responsibilities? Better to include under About the role as additional note? But the instruction: do not repeat job title as heading. We can include that note in About the role paragraph or maybe as a separate
under About the role. However the note about visa sponsorship is important substantive info. Where to place? Could be under About the role as a note. Or we could create a section "Additional Information" but not in allowed headings. Better to incorporate into About the role or Responsibilities? It's not a responsibility. I'd add a
under About the role after the role description, covering
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Preserve all substantive information; do not invent or summarize away detail. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the posting. Key content: - Hybrid work: requires associates to be in-office 1-2 days per week, fostering collaboration, etc. Also note: Alternate locations may be considered if candidates reside within commuting distance from an office. Note about policy: candidates not within reasonable commuting distance will not be considered unless accommodation. Also note: PLEASE NOTE: This position is not eligible for current or future visa sponsorship. - Role description: Engineer Senior responsible for delivery of end to end application, system development and maintenance on complex multi technology platforms within assigned client group, business unit or corporate department and utilizing various customer technology platforms. - How You Will Make An Impact: bullet list of responsibilities (looks like a list). Let's extract bullet points: Maintains active relationships with customers to determine business requirements and leads requirements gathering meetings. Owns the change request process and may coordinate with other teams as necessary. Provides technical advice and weighs in on technical decisions that impact cross functional teams. Researches and may propose new technologies. Develops and owns list of final enhancements. Develops and defines application scope and objectives and prepares technical and/or functional specifications from with programs will be written. Performs technical design reviews and code reviews. May own technical testing to ensures unit test is completed and meets the test plan requirements, system testing is completed and system is implemented according to plan. Assesses current status and supports data information planning. Coordinates on-call support and ensures effective monitoring of system. Maintains technical development environment. Mentors others and may lead multiple or small to medium sized projects. Will begin to set direction at the project/service level and influences decision-making. Provides technical guidance, and mentoring. Understands the tradeoffs between technical, analytical and product needs of the technical solutions. Identifies and propose strategies around technical problems affecting team, communicates standards and gets buy-in on solutions. Facilitates group sessions to elicit complex information on requirements clarification, design sessions, code reviews and troubleshooting issues. Supports vendor evaluation. - Minimum Requirements: Requires a BA/BS degree in Information Technology, Computer Science or related field of study and a minimum of 5 years related experience; experience working with multi dimensional platforms, and business and technical applications also required; or any combination of education and experience, which would provide an equivalent background. - Preferred Skills, Capabilities & Experiences: list: Full Stack Java Developer with hands-on experience with Java 21, Spring, Spring Boot, WebSphere, and ORM frameworks (Hibernate, Spring DAO). Intermediate proficiency with Oracle, RESTful web services design and development, JUnit, and SQL. Experience working with multiple platform (Linux, Cloud(Azure)) Experience deploying applications to servers (preferably WebSphere) and working with CI/CD tools such as Checkmarx, SonarQube, and Artifactory. Strong understanding of design patterns and their application throughout the development lifecycle. Knowledge of microservices architecture and performance optimization techniques. Experience mentoring others, leading multiple small projects and providing troubleshooting support is preferred. Facets Provider domain knowledge preferred. Familiarity with AI-assisted development tools (e.g., GitHub Copilot, Windsurf) preferred. - Salary: For candidates working in person or virtually in the below location(s), the salary* range for this specific position is $120,080 to $180,120. Locations: Virginia - Benefits: In addition to your salary, Elevance Health offers benefits such as a comprehensive benefits package, incentive and recognition programs, equity stock purchase and 401k contribution (all benefits are subject to eligibility requirements). - Additional details about salary: The salary offered for this specific position is based on a number of legitimate, non-discriminatory factors set by the Company... etc. This is more boilerplate about salary determination. Might be considered part of Pay section? The instruction: include Pay section only if posting actually states them. It does state salary range and location. So we can include Pay section with that info. Also Benefits section: they mention benefits package etc. So we can include Benefits. - Schedule: The posting mentions hybrid: requires associates to be in-office 1-2 days per week. That's schedule info. So we can include Schedule section with that detail. - About the role: maybe we can have an "About the role" section summarizing the role description (Engineer Senior responsible for delivery...). Could be a paragraph. - Responsibilities: we have the "How You Will Make An Impact" list. That's responsibilities. - Requirements: Minimum Requirements. - Qualifications: maybe combine Minimum Requirements and Preferred Skills? But we have separate sections: Requirements (minimum) and Qualifications (preferred). The instruction: use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have Requirements for minimum, Qualifications for preferred? Or Skills for preferred skills. The list includes "Preferred Skills, Capabilities & Experiences". That could go under Skills or Qualifications. We need to decide. We should avoid thin sections. Perhaps combine Requirements and Qualifications into one? But we have headings list; we can choose to include only those with substantive content. Let's see: - About the role: we have a paragraph describing role. Good. - Responsibilities: we have bullet list. Good. - Requirements: we have minimum requirements (degree + 5 years). Good. - Qualifications: we could put preferred skills under Qualifications, or Skills. The instruction includes Skills as a possible heading. Since the preferred list is about skills, we could use Skills heading. Qualifications could be for education/experience? But we already used Requirements for that. Maybe we can put preferred skills under Skills, and keep Qualifications empty? Better to not create empty heading. So we could use Skills heading for the preferred skills list. Then we might not need Qualifications heading. Or we could put both minimum and preferred under Requirements and Qualifications respectively. Let's examine: The posting has "Minimum Requirements" and "Preferred Skills, Capabilities & Experiences". So we can map Minimum Requirements to Requirements heading, and Preferred Skills to Skills heading. That seems appropriate. Qualifications heading could be omitted if no distinct qualifications beyond those. But we could also put education/experience under Qualifications and skills under Skills. However we already have degree+experience under Minimum Requirements. That could be considered qualifications. But to avoid thin sections, we can combine: Requirements heading for minimum requirements (degree+experience) and Skills heading for preferred skills. That's two sections. - Benefits: we have benefits paragraph. Good. - Pay: we have salary range and location. Good. - Schedule: we have hybrid schedule (1-2 days in office). Good. Thus we will output sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. We need to use
for each section heading. Then content:
for prose,
- for lists.
We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate like EEO, legal, etc. Also remove duplicated lines, application instructions, etc.
We need to preserve all substantive information. Let's extract substantive info:
About the role: "Engineer Senior is responsible for delivery of end to end application, system development and maintenance on complex multi technology platforms within assigned client group, business unit or corporate department and utilizing various customer technology platforms." Also maybe mention hybrid work? But that's schedule. Could also mention that this role requires associates to be in-office 1-2 days per week fostering collaboration etc. That's schedule. So About the role can be just the description of role responsibilities high-level.
Responsibilities: list of bullet points as above.
Requirements: "Requires a BA/BS degree in Information Technology, Computer Science or related field of study and a minimum of 5 years related experience; experience working with multi dimensional platforms, and business and technical applications also required; or any combination of education and experience, which would provide an equivalent background."
Skills: list of preferred skills as above.
Benefits: "In addition to your salary, Elevance Health offers benefits such as a comprehensive benefits package, incentive and recognition programs, equity stock purchase and 401k contribution (all benefits are subject to eligibility requirements)." Also maybe mention other benefits from later paragraph: "We offer a range of market-competitive total rewards that include merit increases, paid holidays, Paid Time Off, and incentive bonus programs (unless covered by a collective bargaining agreement), medical, dental, vision, short and long term disability benefits, 401(k) +match, stock purchase plan, life insurance, wellness programs and financial education resources, to name a few." That's also benefits. Should we include that? It's substantive. The posting includes that under "How We Work". It's part of benefits description. So we should include that as part of Benefits section. Combine both.
Pay: "For candidates working in person or virtually in the below location(s), the salary* range for this specific position is $120,080 to $180,120. Locations: Virginia". Also maybe note that salary offered based on factors etc. That's more detail about salary determination. Could include as prose. But we must avoid filler like "The salary offered for this specific position is based on a number of legitimate, non-discriminatory factors set by the Company." That is substantive but maybe considered boilerplate? It's still info about salary determination. The instruction: do not create Pay section unless posting actually states them. It does state salary range. The additional sentences about salary determination are also part of posting. Should we include them? They are not filler like "commensurate with experience". They are specific. I'd include them as part of Pay section prose.
Schedule: "This role requires associates to be in-office 1 - 2 days per week, fostering collaboration and connectivity, while providing flexibility to support productivity and work-life balance. This approach combines structured office engagement with the autonomy of virtual work, promoting a dynamic and adaptable workplace. Alternate locations may be considered if candidates reside within a commuting distance from an office. Please note that per our policy on hybrid/virtual work, candidates not within a reasonable commuting distance from the posting location(s) will not be considered for employment, unless an accommodation is granted as required by law." Also note about visa sponsorship: "PLEASE NOTE: This position is not eligible for current or future visa sponsorship." That's not schedule but maybe a note. Could be included in About the role or a separate note? It's not schedule. Could be included in About the role or maybe a separate section like "Additional notes". But we should not create a section unless we have substantive content. Could add a short paragraph under About the role or maybe under Responsibilities? Better to include under About the role as additional note? But the instruction: do not repeat job title as heading. We can include that note in About the role paragraph or maybe as a separate
under About the role. However the note about visa sponsorship is important substantive info. Where to place? Could be under About the role as a note. Or we could create a section "Additional Information" but not in allowed headings. Better to incorporate into About the role or Responsibilities? It's not a responsibility. I'd add a
under About the role after the role description, covering