Jobs · Florida

Senior Java Test Automation Engineer

Full-time
We need to output HTML fragment with sections: About the role? The posting includes intro paragraphs about DTCC, mission, etc. We need to decide sections: maybe "About the role" (intro), "Responsibilities", "Qualifications", "Skills"? The posting includes "Qualifications" and "Nice to Have Skills". Also "Pay And Benefits" section. Also schedule: flexible/hybrid model. Also "The Impact You Will Have in This Role" could be part of About the role or separate? We need to include sections only when there is real specific content. We must not repeat job title as heading. No Job ID. Remove boilerplate like EEO, equal opportunity, accommodation request, etc. Also remove application instructions (none). Remove duplicated lines. We need to preserve all substantive information. So we need to include content about DTCC mission, IT group, etc. That could go under "About the role" or maybe "About DTCC". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map. We have content: "Are you ready to make an impact at DTCC? ..." That's introductory marketing. Could be under About the role. Then "The Impact You Will Have in This Role" could be part of About the role or maybe separate "Impact". But not in list; we could incorporate into About the role. Responsibilities: list under "Your Primary Responsibilities". That's a big list. Qualifications: includes Bachelor's degree, 6-8+ years experience, etc. Also "Talent Needed for Success" which is basically required skills. Could be under Qualifications or Skills. The instruction says we can have Qualifications and Skills sections. We'll put required qualifications under Qualifications, and maybe Skills under Skills (like Nice to Have Skills). But we also have "Strong hands‑on Core Java programming experience..." etc. Those are required skills. Could go under Skills. But we have both Qualifications and Skills sections; we need to decide. We have "Qualifications" heading in posting: "Qualifications Bachelor’s degree...". Then "Talent Needed for Success" which is basically required skills. Then "Nice to Have Skills". So we can map: - Qualifications: education + years experience. - Skills: required skills (Core Java, Selenium, TestNG/JUnit, etc.) - Nice to Have Skills: could be under Skills as a subsection? But we should not create extra headings not in list. Could put them under Skills as a list with note "Nice to have". Or we could have separate Skills section and include both required and nice-to-have, but we need to preserve all info. Could split: Skills (required) and maybe another heading? Not allowed. Better to put required skills under Skills, and nice-to-have under Skills as a sublist with label? But we cannot add extra headings; we can embed within
    with a preceding

    saying "Nice to have:" but that's okay. Pay: we have "Pay And Benefits" section with details: Competitive compensation, health insurance, pension, PTO, flexible/hybrid model. So we need Pay and Benefits sections? The instruction says include Pay and Benefits sections only if posting actually states them. It does state Pay And Benefits. So we should have a

    Pay

    and

    Benefits

    ? Or combine? The list includes both Pay and Benefits as separate possible headings. We could make a Pay section with compensation details, and Benefits section with health, pension, PTO, flexible/hybrid. However the posting lumps them together under "Pay And Benefits". We could split: Pay: "Competitive compensation, including base pay and annual incentive". Benefits: health insurance, life insurance, well-being benefits, pension/retirement, PTO, personal/family care, leaves, flexible/hybrid model. That seems reasonable. Schedule: we have flexible/hybrid model details. Could go under Schedule heading. But we already used that info in Benefits. Might be better to put schedule under Schedule heading. The posting says: "DTCC offers a flexible/hybrid model of 3 days onsite and 2 days remote (onsite Tuesdays, Wednesdays and a third day unique to each team or employee)." That's schedule info. So we should have a Schedule section. Thus we will have sections: About the role, Responsibilities, Qualifications, Skills, Pay, Benefits, Schedule. We must not include empty sections. Ensure each has substantive content. Now we need to strip boilerplate: EEO, equal opportunity, accommodation request, etc. Also remove "We are an equal opportunity employer..." lines. Also remove "Please contact us to request accommodation." Also remove "The salary range is indicative..." maybe keep? It's about salary range indicative; it's part of Pay? Might be considered boilerplate but it's substantive about salary determination. Could keep under Pay. But it's generic; still it's part of posting. We'll keep. Also remove duplicated lines: none. Now craft HTML. Structure:

    About the role

    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. The Impact You Will Have in This Role As a Senior Software Development Engineer in Test (SDET), you will play a critical role in modernizing Java‑based, cloud‑ready platforms that support DTCC’s financial risk management and daily settlement operations. You will be embedded within a business‑aligned development squad and work at the center of DTCC’s multi‑year enterprise modernization program (through 2028), contributing directly to the stability, resilience, and integrity of the clearing ecosystem. In this role, you will design, build, and own engineering‑grade test automation frameworks that ensure the quality, reliability, and scalability of mission‑critical systems. You will partner closely with software engineers, architects, product managers, and platform teams to embed quality throughout the SDLC, influence technical direction, and support the transition from legacy platforms to scalable, resilient, cloud‑ready architectures. This is a hands‑on, code‑driven role requiring strong Core Java programming skills and deep Selenium automation expertise. You will actively develop automation frameworks, write reusable Java components, and solve complex testing and system‑stability challenges across UI, API, and backend layers. This is not a manual QA or scripting‑only position—it is a technical leadership role focused on building scalable automation solutions and driving engineering excellence at enterprise scale.

    But we need to avoid repeating "The Impact You Will Have in This Role" as heading; we can just keep as paragraph. Now Responsibilities:

    Responsibilities

    • Lead the strategy, design, and evolution of enterprise-grade test automation frameworks, seamlessly integrated into modern CI/CD pipelines
    • Champion an “automation-first” quality engineering mindset, driving comprehensive test coverage across API, UI, integration, and end-to-end layers
    • Leverage AI-driven testing capabilities (e.g., intelligent test generation, self-healing automation, test optimization, anomaly detection, and defect pattern analysis) to enhance efficiency, reliability, and coverage
    • Serve as a technical leader and mentor, accelerating adoption of automation and AI-driven practices across the quality engineering community
    • Design, build, and scale robust Java-based automation frameworks using tools such as Selenium WebDriver, TestNG, and JUnit
    • Develop high-quality, reusable, and maintainable code (utilities, base classes, and shared components) using strong object-oriented principles
    • Implement modern automation design patterns (e.g., Page Object Model) to ensure scalability, maintainability, and extensibility
    • Build automation solutions for UI, API, and backend systems, including database validation using JDBC/JPA and SQL
    • Diagnose and resolve test issues by debugging, refactoring, and optimizing automation suites, addressing flakiness, synchronization, and locator strategies
    • Integrate automated test suites into CI/CD pipelines (e.g., Jenkins, Bitbucket) to enable continuous testing and rapid feedback loops
    • Actively contribute to architecture discussions, code reviews, and solution design, driving best practices in quality engineering
    • Partner closely with engineering, product, and DevOps teams in Agile environments to continuously improve product quality, delivery velocity, and overall engineering excellence
    Qualifications:

    Qualifications

    • Bachelor’s degree in computer science, Software Engineering, or a related field, or equivalent professional experience
    • 6–8+ years of experience in test automation, SDET, or quality engineering roles with a strong engineering focus
    Skills: We need to list required skills: Strong hands‑on Core Java programming experience, demonstrated through automation framework development — not just test scripting. Proven ability to apply Core Java concepts in real automation code, including: - Object‑Oriented Programming (inheritance, polymorphism, encapsulation) Java Collections (List, Map, Set) Exception handling Basic concurrency / multithreading concepts Deep hands‑on experience with Selenium WebDriver, including: - Writing and maintaining Page Objects Effective locator strategies (XPath, CSS) Synchronization and test stability best practices Experience completing hands‑on Java and Selenium coding exercises, including live technical interviews. Hands‑on experience with TestNG and/or JUnit, Maven/Gradle, Git, and CI/CD pipelines. Experience with API testing using Rest Assured and SQL‑based backend validation. Strong understanding of software testing methodologies and TDD/BDD principles. We can format as
      with items; for sub-items we can nest
        or just include in same
      • with dash. Let's do:

        Skills

        • Strong hands‑on Core Java programming experience, demonstrated through automation framework development — not just test scripting. Proven ability to apply Core Java concepts in real automation code, including:
          • Object‑Oriented Programming (inheritance, polymorphism, encapsulation)
          • Java Collections (List, Map, Set)
          • Exception handling
          • Basic concurrency / multithreading concepts
        • Deep hands‑on experience with Selenium WebDriver, including:
          • Writing and maintaining Page Objects
          • Effective locator strategies (XPath, CSS)
          • Synchronization and test stability best practices
        • Experience completing hands‑on Java and Selenium coding exercises, including live technical interviews
        • Hands‑on experience with TestNG and/or JUnit, Maven/Gradle, Git, and CI/CD pipelines
        • Experience with API testing using Rest Assured and SQL‑based backend validation
        • Strong understanding of software testing methodologies and TDD/BDD principles
        Nice to have skills: we can include as a note within Skills or separate? Since we don't have a separate heading for nice-to-have, we can add a
      • with "Nice to have:" and nested list. Add after required skills:
      • Nice to have:
        • Exposure to cloud environments and containerization (Docker, Kubernetes)
        • Experience with performance testing tools such as JMeter
        • Experience working in Agile / DevOps environments with continuous integration and delivery
      • Now Pay:

        Pay

Similar jobs