Senior Full Stack Software Engineer - Java/AWS

We need to output HTML fragment with sections: headings

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 etc. Include only sections when posting has real specific content. We need to parse the job posting. Key sections: - About the role: The intro paragraphs about DTCC, mission, etc. Could be "About the role" or maybe "About DTCC". The posting includes: "Are you ready to make an impact at DTCC? ..." then description of DTCC, IT group, etc. That could be "About the role" or "About DTCC". We'll use "About the role". Provide prose in

  . - Responsibilities: The "Your Primary Responsibilities" section with bullet points under subheadings (Technical Leadership & Engineering Excellence, Cloud-Native Application Development, Event-Driven & Platform Engineering, DevOps, Reliability & Operational Excellence, Collaboration & Delivery). We need to output a list of duties/requirements. Likely each bullet point is a duty. We'll create a

  with
  • items summarizing each bullet. Must preserve all substantive info; we can keep the bullet text as is. - Qualifications: There's a "Qualifications" heading with bullet list: Bachelor's Degree..., 8+ years..., Proven experience leading..., Talent Needed for Success (which seems like subcategories). Actually after Qualifications heading, there is a list: Bachelor's Degree..., 8+ years..., Proven experience leading..., Talent Needed for Success (which then has subcategories: Full Stack Engineering, Cloud & DevOps Experience, Data & Platform Engineering, Leadership & Professional Skills). Then Preferred Qualifications list. We need to decide sections: Qualifications (required) and maybe Skills? The posting includes many skill details under "Talent Needed for Success". Could treat that as Skills. But we can also combine under Qualifications. However instruction: Use sections like Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content. We have Pay and Benefits: The posting includes "Pay And Benefits" section with bullet points: Competitive compensation..., Comprehensive health..., Pension..., Paid Time Off..., flexible/hybrid model. So we can have Benefits section (maybe also Pay). The instruction: Prefer a few substantive sections over many thin ones. Could combine Pay and Benefits into one section "Benefits" that includes pay and benefits details. Or separate Pay and Benefits if both present. The posting includes both pay and benefits details. We could have a Benefits section that includes compensation, health, retirement, PTO, flexible model. Pay details: "Competitive compensation, including base pay and annual incentive". That's part of benefits. So we can have a single Benefits section. Schedule: The posting includes flexible/hybrid model: 3 days onsite, 2 days remote (onsite Tuesdays, Wednesdays and a third day unique). That's schedule info. Could be included in Benefits or separate Schedule section. Since we have schedule info, we could create a Schedule section. But instruction: prefer few substantive sections over many thin ones. Could embed schedule within Benefits. However they said include a section ONLY when posting has real specific content for it — never emit heading followed by filler. So we can include Schedule if we have specific content. We have schedule details. Could make a Schedule section. But we also have Benefits details. Could we combine Benefits and Schedule into one "Benefits and Schedule"? But headings are predefined: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose to use Benefits and Schedule separately. That's fine. We need to avoid repeating job title as heading. Not needed. We need to remove boilerplate: EEO, equal opportunity, scam warning, etc. At end there is EEO statement. Remove that. Also remove "Please contact us to request accommodation." That's part of EEO? Might be considered boilerplate; remove. Also remove "We are an equal opportunity employer..." etc. Also remove "The salary range is indicative for roles at the same level within DTCC across all US locations. Actual salary is determined based on the role, location, individual experience, skills, and other considerations." That's pay info but it's generic; still it's substantive? It's about pay determination. Could keep as part of Pay section. But we might not have a separate Pay section; we could include in Benefits. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the details about compensation, health, pension, PTO, flexible model. Also the statement about salary range indicative etc. That's substantive about pay. So we should include it. Thus we could have a Pay section with that paragraph, and Benefits section with health, pension, PTO, flexible model. Or combine. Given we have both pay and benefits details, we can make two sections: Pay and Benefits. Schedule: we have flexible/hybrid model details; could be part of Benefits or Schedule. Since we already have Benefits, we could put schedule under Benefits as well. But we have a Schedule section possible. To avoid thin sections, maybe combine schedule into Benefits. However the instruction: "Prefer a few substantive sections over many thin ones." So if we can combine schedule into Benefits, we avoid an extra thin section. So we will not create a separate Schedule section; we will include schedule info within Benefits. Thus sections: About the role, Responsibilities, Qualifications, Skills (maybe we treat Talent Needed for Success as Skills), Benefits (including pay, health, pension, PTO, flexible model). Possibly also Requirements? The posting has "Qualifications" and "Talent Needed for Success" which includes skill details. There's no separate "Requirements" heading besides Qualifications. Could we treat Qualifications as Requirements? The instruction includes Requirements as a possible heading. But we have Qualifications heading already. We could map Qualifications to Requirements? But better to follow the posting: there is a "Qualifications" heading. So we will use Qualifications. Skills: The "Talent Needed for Success" includes detailed skill categories. Could be considered Skills. We'll create a Skills section with subcategories maybe as
    with
    • for each category and within each maybe nested? But we can just list each bullet as a skill area. However we need to preserve all detail; we could keep the subheadings as part of
    • text. Simplify: We'll create a Skills section with
      where each
      • contains the heading (e.g., "Full Stack Engineering: Deep expertise in Java, J2EE, Spring Boot, Spring MVC, Spring Security, and Hibernate. Strong experience building modern front-end applications using Angular and/or React. Proficiency with TypeScript, JavaScript, HTML, and CSS. Hands-on experience developing RESTful APIs, microservices, distributed systems, and event-driven architectures. Experience building highly scalable, high-performance enterprise applications. Strong understanding of object-oriented design principles, design patterns, and software architecture best practices. Experience with Apache Kafka or Confluent Kafka.") etc. Similarly for Cloud & DevOps, Data & Platform Engineering, Leadership & Professional Skills. We also have Preferred Qualifications list; we could include under Qualifications as optional? Or maybe under Skills? But Preferred Qualifications are extra; we could include them under Qualifications as a separate
        with heading "Preferred Qualifications". However we must not invent sections; we can include them as part of Qualifications. Thus Qualifications section will have required qualifications (Bachelor's, 8+ years, Proven experience leading...) plus maybe a sublist for Talent Needed for Success? Actually Talent Needed for Success is more like skills. We'll separate. Thus: - About the role: prose paragraphs from intro up to "The Impact You Will Have in This Role". Actually that is a separate section maybe "Impact". But we don't have a heading for Impact; we could treat as part of About the role or Responsibilities. The posting includes a section "The Impact You Will Have in This Role". That's descriptive; could be part of About the role. We'll incorporate. Thus About the role will include paragraphs: "Are you ready to make an impact at DTCC? ..." up to "The Impact You Will Have in This Role" paragraph(s). We'll keep them as prose. - Responsibilities: list of duties from "Your Primary Responsibilities" and its subheadings. - Skills: from "Talent Needed for Success" subcategories. - Qualifications: from "Qualifications" heading (Bachelor's, 8+ years, Proven experience leading...) plus maybe also "Preferred Qualifications" as a sublist. - Benefits: from "Pay And Benefits" section plus flexible/hybrid model. We need to ensure we don't repeat content. Let's extract text. Intro: "Are you ready to make an impact at DTCC? Do you want to work on innovative projects, collaborate with a dynamic and supportive team, and receive investment in your professional development? At DTCC, we are at the forefront of innovation in the financial markets. We are committed to helping our employees grow and succeed. We believe that you have the skills and drive to make a real impact. We foster a thriving internal community and are committed to creating a workplace that looks like the world that we serve. The Information Technology group delivers secure, reliable technology solutions that enable DTCC to be the trusted infrastructure of the global capital markets. The team delivers high-quality information through activities that include development of essential, building infrastructure capabilities to meet client needs and implementing data standards and governance." Then "Pay And Benefits" section. Then "The Impact You Will Have in This Role At DTCC, your work will directly contribute to the stability, resiliency, and efficiency of the global financial markets. As the industry's premier post-trade market infrastructure, DTCC processes and safeguards trillions of dollars in securities transactions annually. As a Senior Full Stack Software Engineer, you will play a key role in modernizing mission-critical platforms that enable the secure, reliable, and high-volume movement of business transactions across DTCC's enterprise ecosystem. Leveraging technologies including Java, Spring Boot, AWS, Kafka, Angular, React, Docker, and Kubernetes, you will design and build cloud-native applications, scalable microservices, modern user experiences, and real-time event-driven solutions. This is an opportunity to solve complex engineering challenges at enterprise scale, influence technical design decisions, and contribute to a multi-year cloud and application modernization journey. If you're passionate about building highly scalable, resilient, and secure platforms that power global financial services, you'll have the opportunity to make a meaningful impact while accelerating your technical growth." Then "Your Primary Responsibilities" with subheadings and bullet points. Then "Qualifications" heading with bullet points: Bachelor's Degree..., 8+ years..., Proven experience leading..., Talent Needed for Success (which then has subcategories). Then "Preferred Qualifications" list. We need to avoid repeating "Talent Needed for Success" as a heading; we will treat its subcategories as Skills. Thus Qualifications section will contain the three bullet points: Bachelor's..., 8+ years..., Proven experience leading... (maybe also "Talent Needed for Success" is not a qualification but skill). We'll not include Talent Needed for Success there. Skills section will contain the four subcategories under Talent Needed for Success. Preferred Qualifications could be placed under Qualifications as a separate list labeled "Preferred Qualifications". Or we could add a separate section but we don't have a heading for Preferred Qualifications; we could incorporate into Qualifications. Thus Qualifications will have two sub-sections: Required Qualifications and Preferred Qualifications. But we cannot add extra headings beyond the allowed list? The instruction says use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should stick to those. However we can still use

        for Qual