Engineer I (US)
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We have: - Work Location: New York, New York, United States of America (metadata) - Hours: 40 (maybe schedule? but schedule is not given; hours 40 per week maybe schedule? Could be schedule: 40 hours per week. The instruction: include Pay/Schedule/Benefits sections only if posting actually states them. Hours: 40 could be schedule (full-time). It says Hours: 40. That's a schedule detail. So we can include a Schedule section with
40 hours per week (full-time). Or we could embed in a short paragraph. - Pay Detail: $110,000.00 - $170,000.00 USD. So we have Pay section. - Benefits: Not explicitly listed, but there is "Our Total Rewards Package" description later. That includes health and well-being benefits, savings and retirement programs, paid time off, banking benefits, career development, reward and recognition. That's benefits info. So we can include Benefits section summarizing that. - About the role: There's a section "About The Role". We'll include that. - Responsibilities: There's "Roles And Responsibilities". We'll include that. - Qualifications & Skills: There's "Qualifications & Skills" with Mandatory Skills and Good To Have Skills. We'll include Qualifications (maybe combine Qualifications and Skills). The instruction: use headings for Requirements, Qualifications, Skills. We could have Qualifications section with mandatory skills, and Skills section with good-to-have? Or combine. Better to have Qualifications (mandatory) and Skills (good-to-have). Or we could have Requirements (maybe same as Qualifications). We'll decide: Qualifications (mandatory) and Skills (good-to-have). Also there is "Additional Information" about culture etc. Could be omitted as not required. - Also there is "Department Overview" and "Job Description" etc. Could be part of About the role? But we already have About The Role section. The department overview could be considered part of About the role or maybe we could add a section "About the team" but not required. We'll keep About the role as given. We must not repeat job title as heading. No Job ID etc. We must remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the sections we keep. We need to format lists with
- . For prose use
. We need to output only HTML fragment. Let's extract content: About The Role paragraph: It's a block of sentences. We'll keep as
about the role. Responsibilities: list of bullet points under "Roles And Responsibilities". We'll convert each sentence to
- .
Qualifications (Mandatory Skills): list of bullet points.
Skills (Good To Have Skills): list.
Pay: we have Pay Detail: $110,000.00 - $170,000.00 USD. Also note about compensation policies etc. We'll include that as prose maybe.
Schedule: Hours: 40. We'll note as 40 hours per week (full-time).
Benefits: from "Our Total Rewards Package" paragraph: includes base salary and variable compensation/incentive awards (e.g., eligibility for cash and/or equity incentive awards, generally through participation in an incentive plan) and several other key plans such as health and well-being benefits, savings and retirement programs, paid time off (including Vacation PTO, Flex PTO, and Holiday PTO), banking benefits and discounts, career development, and reward and recognition.
We'll include that as
maybe with list. We also have "Additional Information: Join in on what others..." etc. That's more cultural; could be omitted as not required but it's substantive. However we have limited sections; we could include an "Additional Information" section but not a standard heading. The instruction only mentions specific headings; we could still add other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "include a section ONLY when the posting has real, specific content for it". It doesn't restrict to those headings only, but suggests those as examples. Safer to stick to those headings. Additional info could be placed under About the role or omitted. We'll omit to keep focused. Now produce HTML. Structure:
About the role
... (the About The Role paragraph)
Responsibilities
- ... ...
Qualifications
- ... ...
Skills
- ... ...
Pay
$110,000.00 - $170,000.00 USD. The base pay actually offered may vary based upon the candidate's skills and experience, job-related knowledge, geographic location, and other specific business and organizational needs. TD is committed to providing fair and equitable compensation opportunities to all colleagues. Growth opportunities and skill development are defining features of the colleague experience at TD. Our compensation policies and practices have been designed to allow colleagues to progress through the salary range over time as they progress in their role. As a candidate, you are encouraged to ask compensation related questions and have an open dialogue with your recruiter who can provide you more specific details for this role.
Schedule
40 hours per week (full-time).
Benefits
TD’s Total Rewards package includes base salary and variable compensation/incentive awards (e.g., eligibility for cash and/or equity incentive awards, generally through participation in an incentive plan) and several other key plans such as health and well-being benefits, savings and retirement programs, paid time off (including Vacation PTO, Flex PTO, and Holiday PTO), banking benefits and discounts, career development, and reward and recognition.
We need to ensure we didn't miss any substantive info from About The Role: Let's copy that paragraph exactly: "As a Senior Java Full Stack Developer, demonstrate ownership, accountability, and long-term thinking by delivering secure, reliable, maintainable, and business-aligned technology solutions. Provides a broad range of system solutions to support business growth and operational functions through the development and programming of applications systems. Design, develop, and maintain high-quality Java full stack solutions that are scalable, resilient, maintainable, and aligned with enterprise standards.Write clean, efficient, well-tested code and ensure defect-free delivery through strong engineering discipline, peer reviews, and adherence to coding best practices.Provide application maintenance and production support during testing cycles, deployment activities, and post-production stabilization.Actively participate in peer code reviews, offering constructive feedback to improve code quality, performance, readability, and long-term maintainability.Follow secure coding standards and application security practices to reduce common vulnerabilities and strengthen the overall security posture of the application.Identify, evaluate, and recommend development, automation, and testing tools that support project objectives, improve delivery efficiency, and enhance engineering quality.Complete unit, integration, and regression testing to validate conformance with design specifications, quality standards, and functional requirements.Comply with enterprise technology delivery practices, governance standards, and project management disciplines, including participation in scope assessment, risk analysis, impact assessment, and cost estimation.Support the development and continuous improvement of processes that prevent recurring issues, improve operational stability, and strengthen service reliability.Participate in incident investigation, root-cause analysis, and timely resolution of production issues while applying appropriate quality controls and documentation practices.Perform application and environment support activities for systems owned by the line of business, including monitoring service performance, managing configuration, supporting backups, validating authentication controls, and contributing to performance tuning.Take ownership of outcomes by proactively managing technical risks, communicating dependencies, and ensuring solutions support business value, client experience, and long-term platform health." We'll put that as. Now Responsibilities list: Let's extract each bullet from "Roles And Responsibilities": - Analyze a broad range of business and technology requirements, conduct application and system research, and identify key solution components required for successful delivery and problem resolution. - Design, develop, enhance, and maintain applications aligned to business needs, enterprise architecture standards, and secure engineering practices. - Develop new application capabilities and perform unit, component, and integration testing to ensure quality, reliability, and adherence to design specifications. - Translate business requirements into effective technical solutions in collaboration with Business Analysts, Systems Analysts, Solution Designers, and other technology partners. - Contribute to project planning by providing technical input into scope, solution approach, estimation, delivery timelines, risks, dependencies, and implementation considerations. - Communicate solution requirements, technical decisions, project status, risks, and issues clearly to stakeholders, management teams, and business partners. - Identify issues that may impact project scope, delivery timelines, application stability, or dependent teams, and resolve or escalate them in a timely and appropriate manner. - Support business inquiries, operational requests, small enhancements, and break/fix implementations, including source code changes, configuration updates, and production support activities. - Work closely with application support, infrastructure, QA, and business teams to ensure custom components and configurations meet functional requirements, non-functional requirements, and performance goals. - Drive continuous improvement by recommending enhancements to development practices, automation, testing coverage, deployment processes, and application maintainability. We'll put each as
- . Qualifications (Mandatory Skills): - Strong hands-on experience with Java (11 or later) and Spring boot, including core Java, object-oriented design principles, collections, concurrency, and modern development practices. - Solid understanding of relational databases, data modeling, query optimization, and SQL development. - Proven experience designing, developing, and consuming RESTful APIs and service-oriented integrations. - Strong experience with microservices architecture, including service decomposition, API contracts, resiliency, observability, and deployment considerations. - Hands-on experience with React and modern front-end development practices, including reusable components, state management, and integration with back-end services. - Experience with reference data handling like security master management, corporate action processing, data reconciliation and exception handling. - Experience with Broadridge demonstrating strong understanding of BPS, Gloss, and Impact data model. We'll list those. Skills (Good To Have Skills): - Experience working as a Java Developer within a financial institution, with an understanding of enterprise controls, regulatory expectations, and production support requirements. - Experience with Python is preferred and considered an advantage for automation, scripting, data analysis, or support tooling. - Experience in Prime Brokerage, Securities Finance, or related capital markets business domains is preferred. - Experience with Broadridge BPSA or similar brokerage processing platforms is considered a plus. Now Pay section: we included some prose from the posting about compensation policies. Ensure we don't invent. The posting includes: "Pay Detail: $110,000.00 - $170,000.00 USD TD is committed to providing fair and equitable compensation opportunities to all colleagues. Growth opportunities and skill development are defining features of the colleague experience at TD. Our compensation policies and practices have been designed to allow colleagues to progress through the salary range over time as they progress in their role. The base pay actually offered may vary based upon the candidate's skills and experience, job-related knowledge, geographic location, and other specific business and organizational needs. As a candidate, you are encouraged to ask compensation related questions and have an open dialogue with your recruiter who can provide you more specific details for this role." We'll include that as a paragraph. Schedule: "Hours: 40". We'll phrase as "40 hours per week (full-time)". That's derived.