Jobs · North Carolina

Senior Java Backend Developer (FTE / Hybrid)

NTT DATA North America · Charlotte, NC · 3 wk ago
$97k–$145k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "Day-to-Day Job Duties", "Basic Qualifications", "Nice to Have", "Education", "Travel", "Pay", "Benefits", "About NTT DATA". Also maybe "Responsibilities" etc. We need to use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map content to appropriate headings. The instructions: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those exact headings when appropriate. We need to include a section only when posting has real, specific content for it. So we need to decide which sections to include. We have: - About the role: could be a brief description? The posting includes "We are currently seeking a Senior Java Backend Developer (FTE / Hybrid) to join our team in Charlotte, North Carolina (US-NC), United States (US)." Also "NTT DATA strives to hire exceptional...". That's more about company. But we could put "About the role" with that description. - Responsibilities: Day-to-Day Job Duties list. - Requirements: Basic Qualifications list. - Qualifications: maybe Nice to Have? Or we could combine Basic Qualifications as Requirements, and Nice to Have as Qualifications or Skills. - Skills: maybe list of technical skills? Could be from Nice to Have. - Benefits: benefits description. - Pay: compensation range. - Schedule: maybe hybrid? The posting mentions "FTE / Hybrid". Also location and hybrid. Could include schedule: Hybrid (FTE/Hybrid). Also travel NA. We should not repeat job title as heading. Do not put Job ID/requisition numbers as headings. Remove boilerplate. We need to preserve all substantive information. So we need to include all duties, qualifications, nice-to-have, education, travel, pay, benefits, about NTT DATA (maybe as About the role or About NTT DATA). The instructions say we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. Let's decide sections: - About the role: short paragraph describing role and location: "We are currently seeking a Senior Java Backend Developer (FTE / Hybrid) to join our team in Charlotte, North Carolina (US-NC), United States (US)." Also maybe include NTT DATA strives to hire... but that's more company. Could include in About NTT DATA but we don't have a heading for that. Could put under About the role? Might be okay. - Responsibilities: list of day-to-day duties. - Requirements: basic qualifications list. - Qualifications: nice-to-have list. - Skills: maybe we could list specific technical skills from nice-to-have? But we already have Qualifications for nice-to-have. Could combine. But we need to avoid thin sections. Perhaps we can combine Nice to Have into Qualifications heading, and not have separate Skills. Or we could have Skills heading for technical skills like Java, Spring Boot, REST, microservices, SQL, etc. However those are already in Requirements. Might be redundant. Better: Use headings: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. That's six sections. We need to include Education somewhere. Could be under Requirements (as part of basic qualifications). The basic qualifications list includes Education bullet? Actually Education is separate bullet after Basic Qualifications list. It says "Education Bachelor’s degree in Computer Science, Information Technology, Engineering, or a related field, or equivalent experience." So we can include that as part of Requirements. Travel NA: we can note under Schedule maybe? Or as a short paragraph under About the role? Travel NA means no travel required. Could include in Schedule section: "Travel: Not required". Or we could add a short p under About the role. We need to preserve all substantive information. So we need to include the NTT DATA company description? That's under "About NTT DATA". Could we put that under About the role? Might be okay but it's more about company. However we don't have a heading for About the company. Could we add a section "About NTT DATA"? The instructions only gave examples but didn't forbid other headings? It says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but we should follow the pattern. Safer to stick to those headings. So we could incorporate the company description into About the role or maybe under Responsibilities? Not ideal. Perhaps we can create a section "About NTT DATA" as a heading, but it's not in the examples. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. So we could use other headings if needed. But to be safe, we could include a section "About NTT DATA" as an

. It's substantive. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule, About NTT DATA. We need to ensure we don't create sections with filler like "commensurate with experience". We have actual content. Now we need to format lists with
  • . For prose, use

    . We must not include markdown code fences. Just output HTML fragment. Let's gather content: About the role: "We are currently seeking a Senior Java Backend Developer (FTE / Hybrid) to join our team in Charlotte, North Carolina (US-NC), United States (US)." Also maybe include "NTT DATA strives to hire exceptional, innovative and passionate individuals who want to grow with us. If you want to be part of an inclusive, adaptable, and forward-thinking organization, apply now." That's more about company but could be part of About the role. We'll include that as prose. Responsibilities: list of duties from "Day-to-Day Job Duties". We'll bullet each. Requirements: Basic Qualifications list (including education). We'll bullet each qualification plus education. Qualifications: Nice to Have list. Benefits: description of benefits. Pay: compensation range description. Schedule: mention FTE/Hybrid, location, travel NA. About NTT DATA: company description paragraph(s). Now we need to ensure we don't repeat job title as heading. We won't. We must not include Job ID/requisition numbers. We'll drop "Req ID: 390737". We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip the EEO statements, the "NTT DATA recruiters will never ask for payment..." etc. Also the accessibility statements, etc. Now craft HTML. We'll start with

    About the role

    then

    ...

    . Then

    Responsibilities

    • ...
    . Then

    Requirements

    • ...
    . Then

    Qualifications

    • ...
    . Then

    Benefits

    • ...
    (or

    but benefits list is a list). Then

    Pay

    ...

    . Then

    Schedule

    ...

    . Then

    About NTT DATA

    ...

    . Make sure to preserve all substantive information. Let's extract details. From posting: Day-to-Day Job Duties (list): - Design, develop, and maintain scalable backend applications using Java and Spring Boot. - Develop and integrate REST APIs and microservices for enterprise applications. - Build reusable, secure, and high-performance backend services. - Develop SQL queries, stored procedures, and database integrations. - Participate in application modernization, including legacy application migration and transformation. - Analyze existing applications and recommend improvements to architecture, performance, and maintainability. - Troubleshoot application issues and provide production support for critical business applications. - Monitor application health, investigate production incidents, and drive root-cause analysis and resolution. - Collaborate with architects, business analysts, QA, DevOps, and frontend teams. - Participate in code reviews, unit testing, CI/CD, and Agile development activities. - Create and maintain technical documentation, design specifications, and support procedures. - Support deployment, release activities, and post-production validation. Basic Qualifications: - 7+ years of experience in Java/backend software development. - 5+ years of hands-on experience with Spring Boot. - 5+ years of experience developing REST APIs. - 4+ years of experience designing and developing microservices. - 5+ years of experience with SQL and relational databases. - 3+ years of experience in application modernization and legacy system transformation. - 3+ years of experience providing production support for enterprise applications. - 3+ years of experience with API integration, design patterns, error handling, and security. - 2+ years of experience with Git and CI/CD practices. - 2+ years of experience working in Agile/Scrum development environments. - 3+ years of experience troubleshooting, debugging, and performing root-cause analysis for application issues. - 3+ years of experience collaborating with architects, business analysts, QA, DevOps, and other cross-functional teams. - 2+ years of experience participating in code reviews, unit testing, deployments, and release activities. - Travel NA (maybe separate) - Education Bachelor’s degree in Computer Science, Information Technology, Engineering, or a related field, or equivalent experience. Nice to Have: - Experience with AWS/Azure/GCP and cloud-native application development. - Experience with Docker/Kubernetes and containerized microservices. - Kafka or other event-driven/messaging technologies. - Experience with NoSQL databases. - Experience with observability tools such as Splunk, Dynatrace, or AppDynamics. - Experience with legacy-to-microservices transformation. - Financial services, insurance, or other enterprise-domain experience. Benefits: - 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 - additional voluntary or legally-required benefits Pay: - NTT DATA provides a reasonable range of compensation for U.S.-based positions. - The starting pay range for this role is $96,800.00 - $145,200.00. - Actual compensation will depend on a number of factors, including the candidate’s relevant experience, technical skills, and other qualifications. - This position may also be eligible for incentive compensation based on individual and/or company performance. Schedule: - FTE / Hybrid - Location: Charlotte, North Carolina (US-NC), United States (US) - Travel NA (no travel required) - Possibly mention hybrid work options subject to change, but we can keep concise. About NTT DATA: - NTT DATA is a $30 billion business and technology services leader, serving 75% of the Fortune Global 100. - We are committed to accelerating client success and positively impacting society through responsible innovation. - We are one of the world's leading AI and digital infrastructure providers, with unmatched capabilities in enterprise-scale AI, cloud, security, connectivity, data centers and application services. - our consulting and Industry solutions help organizations and society move confidently and sustainably into the digital future. - As a Global Top Employer, we have experts in more

Similar jobs