Senior Software Development Specialist - Java - Remote
NTT DATA North America · Plano, TX · 3 wk ago
Engineering$75k–$131k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "Position Overview" and "Key Responsibilities", "Basic Qualifications", "Preferred Qualifications", "Pay Transparency", "About NTT DATA". Also maybe "Benefits". The instructions: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a 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 the posting actually states them. Prefer a few substantive sections over many thin ones.
We need to decide which sections to include. The posting includes:
- Position Overview (could be "About the role")
- Key Responsibilities (Responsibilities)
- Basic Qualifications (Requirements/Qualifications)
- Preferred Qualifications (maybe also Qualifications)
- Pay Transparency (Pay)
- Benefits (the paragraph about benefits)
- About NTT DATA (maybe "About the company" but not in list; but we could include as a section? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Not "About NTT DATA". However we could treat it as "About the role"? No. The instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." meaning examples, not exclusive list? Probably we should stick to those headings. But we can also include other headings if needed? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are the expected headings. It doesn't forbid others, but to be safe we should map content to those headings.
Thus:
- About the role: Position Overview paragraph.
- Responsibilities: Key Responsibilities list.
- Requirements: Basic Qualifications list (maybe also Preferred Qualifications could be under Qualifications or Skills). Could combine Basic and Preferred under Qualifications? But we have separate headings: Requirements and Qualifications. Could put Basic Qualifications under Requirements, Preferred Qualifications under Qualifications. Or we could put both under Qualifications. Let's decide: Requirements = Basic Qualifications (must-have). Qualifications = Preferred Qualifications (nice-to-have). Skills maybe not needed.
- Benefits: paragraph about benefits.
- Pay: Pay Transparency paragraph.
- Schedule: Not mentioned; remote role but no schedule specifics. Should not create Schedule section if not stated.
Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
We need to use for each heading. Then content: For prose use
. For lists use
- . Ensure we preserve all substantive information.
We must remove boilerplate: Req ID line, NTT DATA strives to hire..., apply now, etc. Also remove EEO, legal, scam-warning, contact us, accessibility, equal opportunity, etc. Also remove duplicated lines. Also remove "About NTT DATA" maybe? But we could keep as part of About the role? Actually About NTT DATA is company description; not required but could be included as part of About the role? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep About NTT DATA info somewhere. Where to put? Could be under About the role? But that heading is for role overview. Could add another section like "About the company" but not in allowed headings. However we could include it as a paragraph under About the role? Might be okay to add as a separate section with heading "About NTT DATA" even if not in examples? The instruction says use those headings (e.g.) but not strictly limited. Safer to include it as a section with heading "About NTT DATA". But the instruction says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are the expected headings; but we could still add others if needed. However to be safe, we could incorporate About NTT DATA into About the role section as additional prose. That would preserve the info. The role overview already includes some description; we can append the About NTT DATA paragraph after it. That would preserve all substantive info.
Thus About the role section will contain two paragraphs: Position Overview and About NTT DATA.
Now we need to extract the exact text.
Let's copy relevant parts:
Position Overview:
"We are seeking a Senior Software Development Specialist with extensive experience designing, developing, testing, and supporting enterprise Java/J2EE applications. The ideal candidate will have a strong background in modern Java development, enterprise application architecture, web technologies, integration, and application modernization. This role will participate throughout the Software Development Life Cycle (SDLC) and work closely with business stakeholders, architects, developers, QA teams, and other technology partners to deliver scalable, reliable, and high-quality solutions. The successful candidate will also contribute to application modernization, product redesign, automated testing, and containerized deployment strategies."
Key Responsibilities list:
- Design, develop, test, implement, and maintain scalable and stable Java/J2EE enterprise applications.
- Develop both custom-built and commercial/off-the-shelf application solutions using Java and enterprise web technologies.
- Participate in the full application development lifecycle, including requirements analysis, solution design, data modeling, coding, integration, implementation, testing, and production support.
- Collaborate with business partners and stakeholders to understand business requirements and translate them into effective technical solutions.
- Design and develop new applications, features, and enhancements to existing enterprise applications.
- Contribute to product development initiatives, including significant application redesign, modernization, and performance improvements.
- Develop and implement effective application versioning, release, and deployment strategies.
- Design and develop application integrations using RESTful and SOAP-based web services and other enterprise integration technologies.
- Develop automated testing frameworks and reusable functional test libraries to improve application quality and delivery efficiency.
- Support containerized application deployments using Docker and Kubernetes, including deployment, orchestration, scaling, and management.
- Troubleshoot complex application, integration, database, and deployment issues.
- Collaborate with cross-functional teams to establish development standards, resolve technical challenges, and deliver solutions on schedule.
- Lead or participate in technical meetings, design sessions, code reviews, and implementation activities.
Basic Qualifications list (need to preserve exactly as given, but we can format as list items). The text:
"10+ years of professional experience in application development, including the design and development of Java/J2EE enterprise applications and web technologies.
8+ years of hands-on experience with core Java/J2EE technologies, including:JavaJSPServletsJSFJSTLEJBJavaBeansSpringHibernateStrutsXML MappingAntMaven
5+ years of experience with XML and related web/integration technologies, including:AJAXWeb ServicesSOAPWSDLRESTful servicesDTDXSL/XSLTXPathDOMSAXHTMLCSSJavaScript
3+ years of experience developing automated testing frameworks and reusable functional test libraries.
2+ years of experience with Kubernetes, including orchestration, deployment, scaling, and management of Docker containers."
Note there are missing spaces after colons; we should preserve as is? Probably we should keep the exact wording but maybe add spaces for readability? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't require exact formatting, but we should keep the content. We can format as list items with the same text.
Preferred Qualifications list:
"Experience working in the healthcare industry, particularly health plan implementation and healthcare payer environments.
Strong understanding of enterprise application architecture, development methodologies, and SDLC practices.
Experience modernizing legacy Java applications and transitioning enterprise applications to newer frameworks and deployment platforms.
Strong understanding of application integration and enterprise web services.
Excellent written and verbal communication skills, with the ability to effectively communicate with technical and non-technical stakeholders.
Strong customer-service orientation with the ability to understand business needs, address customer concerns, and translate requirements into practical technology solutions.
Strong analytical and problem-solving skills with a high level of attention to detail.
Excellent time-management and organizational skills, with the ability to manage multiple priorities.
Demonstrated ability to work effectively with diverse, cross-functional teams.
Comfortable leading technical discussions, working sessions, and stakeholder meetings.
Strong work ethic and a collaborative, results-oriented approach."
Pay Transparency paragraph:
"Where required by law, NTT DATA provides a reasonable range of compensation for specific roles. The starting pay range for this remote role is $75,168-$130,500. This range reflects the minimum and maximum target compensation for the position across all US locations. Actual compensation will depend on a number of factors, including the candidate’s actual work location, relevant experience, technical skills, and other qualifications."
Benefits paragraph:
"This position is eligible for company benefits including medical, dental, and vision insurance with an employer contribution, flexible spending or health savings account, life and AD&D insurance, short- and long-term disability coverage, paid time off, employee assistance, participation in a 401k program with company match, and additional voluntary or legally-required benefits."
Now we need to strip boilerplate: Remove Req ID line, NTT DATA strives to hire..., apply now, etc. Also remove the line "We are currently seeking a Senior Software Development Specialist - Java - Remote to join our team in Plano, Texas (US-TX), United States (US)." That's maybe part of the posting but it's location info; could be considered minor metadata; we could fold into a short p or drop. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we could include location info as a short p maybe under About the role? But we already have About the role with position overview and company description. Could add a short p about location. However location is not essential? It's substantive? It says location: Plano, Texas (US-TX), United States (US). Could be considered minor metadata; we could drop it. Safer to drop it.
Also remove "Position Overview" heading (we will replace with About the role). Remove "Key Responsibilities", "Basic Qualifications", "Preferred Qualifications", "Pay Transparency", "About NTT DATA", "NTT DATA recruiters will never ask for payment..." etc. Also remove EEO, legal, scam-warning, contact us, accessibility, equal opportunity, etc.
Now produce HTML.
Structure:
About the role
Position overview paragraph.
About NTT DATA paragraph.
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- ...
...
.
Benefits
...
Pay
...
Make sure no extra whitespace? It's fine.
Now ensure we didn't miss any responsibilities: The list includes "Design and develop application integrations using RESTful and SOAP-based web services and other enterprise integration technologies." In the text we saw "Design and develop application integrations using RESTful and SOAP-based web services and other enterprise integration technologies."
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a 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 the posting actually states them. Prefer a few substantive sections over many thin ones. We need to decide which sections to include. The posting includes: - Position Overview (could be "About the role") - Key Responsibilities (Responsibilities) - Basic Qualifications (Requirements/Qualifications) - Preferred Qualifications (maybe also Qualifications) - Pay Transparency (Pay) - Benefits (the paragraph about benefits) - About NTT DATA (maybe "About the company" but not in list; but we could include as a section? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Not "About NTT DATA". However we could treat it as "About the role"? No. The instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." meaning examples, not exclusive list? Probably we should stick to those headings. But we can also include other headings if needed? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are the expected headings. It doesn't forbid others, but to be safe we should map content to those headings.
Thus:
- About the role: Position Overview paragraph.
- Responsibilities: Key Responsibilities list.
- Requirements: Basic Qualifications list (maybe also Preferred Qualifications could be under Qualifications or Skills). Could combine Basic and Preferred under Qualifications? But we have separate headings: Requirements and Qualifications. Could put Basic Qualifications under Requirements, Preferred Qualifications under Qualifications. Or we could put both under Qualifications. Let's decide: Requirements = Basic Qualifications (must-have). Qualifications = Preferred Qualifications (nice-to-have). Skills maybe not needed.
- Benefits: paragraph about benefits.
- Pay: Pay Transparency paragraph.
- Schedule: Not mentioned; remote role but no schedule specifics. Should not create Schedule section if not stated.
Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
We need to use for each heading. Then content: For prose use
. For lists use
- . Ensure we preserve all substantive information.
We must remove boilerplate: Req ID line, NTT DATA strives to hire..., apply now, etc. Also remove EEO, legal, scam-warning, contact us, accessibility, equal opportunity, etc. Also remove duplicated lines. Also remove "About NTT DATA" maybe? But we could keep as part of About the role? Actually About NTT DATA is company description; not required but could be included as part of About the role? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep About NTT DATA info somewhere. Where to put? Could be under About the role? But that heading is for role overview. Could add another section like "About the company" but not in allowed headings. However we could include it as a paragraph under About the role? Might be okay to add as a separate section with heading "About NTT DATA" even if not in examples? The instruction says use those headings (e.g.) but not strictly limited. Safer to include it as a section with heading "About NTT DATA". But the instruction says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are the expected headings; but we could still add others if needed. However to be safe, we could incorporate About NTT DATA into About the role section as additional prose. That would preserve the info. The role overview already includes some description; we can append the About NTT DATA paragraph after it. That would preserve all substantive info. Thus About the role section will contain two paragraphs: Position Overview and About NTT DATA. Now we need to extract the exact text. Let's copy relevant parts: Position Overview: "We are seeking a Senior Software Development Specialist with extensive experience designing, developing, testing, and supporting enterprise Java/J2EE applications. The ideal candidate will have a strong background in modern Java development, enterprise application architecture, web technologies, integration, and application modernization. This role will participate throughout the Software Development Life Cycle (SDLC) and work closely with business stakeholders, architects, developers, QA teams, and other technology partners to deliver scalable, reliable, and high-quality solutions. The successful candidate will also contribute to application modernization, product redesign, automated testing, and containerized deployment strategies." Key Responsibilities list: - Design, develop, test, implement, and maintain scalable and stable Java/J2EE enterprise applications. - Develop both custom-built and commercial/off-the-shelf application solutions using Java and enterprise web technologies. - Participate in the full application development lifecycle, including requirements analysis, solution design, data modeling, coding, integration, implementation, testing, and production support. - Collaborate with business partners and stakeholders to understand business requirements and translate them into effective technical solutions. - Design and develop new applications, features, and enhancements to existing enterprise applications. - Contribute to product development initiatives, including significant application redesign, modernization, and performance improvements. - Develop and implement effective application versioning, release, and deployment strategies. - Design and develop application integrations using RESTful and SOAP-based web services and other enterprise integration technologies. - Develop automated testing frameworks and reusable functional test libraries to improve application quality and delivery efficiency. - Support containerized application deployments using Docker and Kubernetes, including deployment, orchestration, scaling, and management. - Troubleshoot complex application, integration, database, and deployment issues. - Collaborate with cross-functional teams to establish development standards, resolve technical challenges, and deliver solutions on schedule. - Lead or participate in technical meetings, design sessions, code reviews, and implementation activities. Basic Qualifications list (need to preserve exactly as given, but we can format as list items). The text: "10+ years of professional experience in application development, including the design and development of Java/J2EE enterprise applications and web technologies. 8+ years of hands-on experience with core Java/J2EE technologies, including:JavaJSPServletsJSFJSTLEJBJavaBeansSpringHibernateStrutsXML MappingAntMaven 5+ years of experience with XML and related web/integration technologies, including:AJAXWeb ServicesSOAPWSDLRESTful servicesDTDXSL/XSLTXPathDOMSAXHTMLCSSJavaScript 3+ years of experience developing automated testing frameworks and reusable functional test libraries. 2+ years of experience with Kubernetes, including orchestration, deployment, scaling, and management of Docker containers." Note there are missing spaces after colons; we should preserve as is? Probably we should keep the exact wording but maybe add spaces for readability? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't require exact formatting, but we should keep the content. We can format as list items with the same text. Preferred Qualifications list: "Experience working in the healthcare industry, particularly health plan implementation and healthcare payer environments. Strong understanding of enterprise application architecture, development methodologies, and SDLC practices. Experience modernizing legacy Java applications and transitioning enterprise applications to newer frameworks and deployment platforms. Strong understanding of application integration and enterprise web services. Excellent written and verbal communication skills, with the ability to effectively communicate with technical and non-technical stakeholders. Strong customer-service orientation with the ability to understand business needs, address customer concerns, and translate requirements into practical technology solutions. Strong analytical and problem-solving skills with a high level of attention to detail. Excellent time-management and organizational skills, with the ability to manage multiple priorities. Demonstrated ability to work effectively with diverse, cross-functional teams. Comfortable leading technical discussions, working sessions, and stakeholder meetings. Strong work ethic and a collaborative, results-oriented approach." Pay Transparency paragraph: "Where required by law, NTT DATA provides a reasonable range of compensation for specific roles. The starting pay range for this remote role is $75,168-$130,500. This range reflects the minimum and maximum target compensation for the position across all US locations. Actual compensation will depend on a number of factors, including the candidate’s actual work location, relevant experience, technical skills, and other qualifications." Benefits paragraph: "This position is eligible for company benefits including medical, dental, and vision insurance with an employer contribution, flexible spending or health savings account, life and AD&D insurance, short- and long-term disability coverage, paid time off, employee assistance, participation in a 401k program with company match, and additional voluntary or legally-required benefits." Now we need to strip boilerplate: Remove Req ID line, NTT DATA strives to hire..., apply now, etc. Also remove the line "We are currently seeking a Senior Software Development Specialist - Java - Remote to join our team in Plano, Texas (US-TX), United States (US)." That's maybe part of the posting but it's location info; could be considered minor metadata; we could fold into a short p or drop. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we could include location info as a short p maybe under About the role? But we already have About the role with position overview and company description. Could add a short p about location. However location is not essential? It's substantive? It says location: Plano, Texas (US-TX), United States (US). Could be considered minor metadata; we could drop it. Safer to drop it. Also remove "Position Overview" heading (we will replace with About the role). Remove "Key Responsibilities", "Basic Qualifications", "Preferred Qualifications", "Pay Transparency", "About NTT DATA", "NTT DATA recruiters will never ask for payment..." etc. Also remove EEO, legal, scam-warning, contact us, accessibility, equal opportunity, etc. Now produce HTML. Structure:
About the role
Position overview paragraph.
About NTT DATA paragraph.
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ... .
Benefits
...
Pay
...
Make sure no extra whitespace? It's fine. Now ensure we didn't miss any responsibilities: The list includes "Design and develop application integrations using RESTful and SOAP-based web services and other enterprise integration technologies." In the text we saw "Design and develop application integrations using RESTful and SOAP-based web services and other enterprise integration technologies."