Engineer III

We need to output HTML fragment with sections only if real content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. From posting: - Intro about company: "Join a financial services firm..." etc. That's about the role? Could be "About the role" or maybe "About the company". We'll put as "About the role" (or maybe "About the role" includes description). We'll include that. - Responsibilities: bullet list under "What You'll Do". That's responsibilities. - Requirements: bullet list under "What You'll Need". That's requirements. - Qualifications: maybe same as requirements? Could separate but we can combine. The instruction: use headings for sections like Qualifications, Skills, Benefits, Pay, Schedule. We need to see if we have distinct content for Skills, Benefits, Pay, Schedule. Skills: The posting mentions many technical skills: Java, Spring Boot, REST APIs, React, JavaScript, Kubernetes, Kafka, MongoDB, Oracle, cloud-native services, AI tools, prompt engineering, etc. Could be a Skills section. But we already have responsibilities and requirements that include skills. However we can still create a Skills section if we have specific skill list not covered elsewhere. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine skills into Requirements or Responsibilities. But we need to follow headings list; we can omit sections if no real specific content. So we can omit Skills if we think it's covered. Benefits: There's a paragraph about benefits: medical, dental, vision, voluntary benefits, disability, life, AD&D, 401k, HSA, FSA, paid holidays, vacation, sick time, personal days, volunteer day, bonuses, profit sharing, EAP. That's substantive. So we need a Benefits section. Pay: No mention of salary or pay. So omit Pay. Schedule: Mentions: "Candidates that live within a commutable distance from our Tempe, AZ and St. Louis, MO home office locations are expected to work in the office four days per week." That's schedule info (hybrid). So we can include Schedule section. Also there is mention of "This job posting is anticipated to remain open for 30 days, from 10-Sep-2026. The posting may close early due to the volume of applicants." That's metadata; we can fold into a short

or drop. Probably drop as minor metadata. Also there is EEO boilerplate; we remove. Thus sections: About the role (intro), Responsibilities, Requirements, Benefits, Schedule. We need to use

for each heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from each section. Let's extract content. About the role: The paragraph(s) before "As an Engineer within the Documents Portfolio..." includes company description. Let's capture: "This job posting is anticipated to remain open for 30 days, from 10-Sep-2026. The posting may close early due to the volume of applicants. Join a financial services firm where your contributions are valued. Edward Jones is a Fortune 500¹ company where people come first. With over 9 million clients and 20,000 financial advisors across the U.S. and Canada, we’re proud to be privately-owned, placing the focus on our clients rather than shareholder returns. Behind everything we do is our purpose: We partner for positive impact to improve the lives of our clients and colleagues, and together, better our communities and society. We are an innovative, flexible, and inclusive organization that attracts, develops, and inspires performance excellence and a sense of belonging. People are at the center of our partnership. Edward Jones associates are seen, heard, respected, and supported. This is what we believe makes us the best place to start or build your career. View our Purpose, Inclusion and Citizenship Report. ¹Fortune 500, published June 2024, data as of December 2023. Compensation provided for using, not obtaining, the rating." We may keep that as About the role. However we might want to remove the "This job posting is anticipated..." as metadata; but it's not required to keep. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can drop that line or put in a short p. Probably drop it. Thus About the role paragraph: join a financial services firm... etc. We'll keep the rest. Responsibilities: bullet list from "What You'll Do". Let's capture each line: - Design, develop, and maintain document-focused applications using modern technologies including Java, Spring Boot, REST APIs, React, JavaScript, Kubernetes, and related frameworks. - Leverage AI tools and prompt engineering techniques to enhance solutions, improve efficiency, and support innovation initiatives. - Build and integrate solutions using modern platforms and technologies such as Kafka, MongoDB, Oracle, and cloud-native services. - Translate business requirements into technical designs, specifications, development estimates, and scalable system solutions. - Lead complex development efforts through design, coding, testing, debugging, deployment, and ongoing maintenance. - Troubleshoot and resolve complex production issues while ensuring system stability, reliability, and performance. - Drive engineering excellence through code reviews, SDLC best practices, test automation, and observability-focused development. - Mentor and develop team members by providing technical guidance, promoting best practices, and fostering a culture of continuous learning. We'll put each as

• . Requirements: bullet list from "What You'll Need". Let's capture: - Bachelor's degree in computer science, Engineering, MIS, or equivalent professional experience. - 5+ years of software engineering experience with expertise across application development, infrastructure, and full-stack solution delivery. - Strong proficiency in Java and/or JavaScript, with experience across multiple programming languages, frameworks, and development stacks. - Experience developing cloud-based, scalable, secure, and distributed solutions, preferably within Microsoft Azure environments. - Expertise in modern application architecture, including microservices, domain-driven design, design patterns, event-driven systems, and distributed caching. - Experience with relational and non-relational databases, APIs, messaging platforms, and modern integration technologies. - Experience with AI tools, AI prompting, low-code/no-code platforms, and Agile development methodologies. - Strong knowledge of test automation, distributed system testing, observability, production support, and enterprise-scale application operations. - Proven ability to mentor engineers, lead technical initiatives, communicate effectively, and drive continuous improvement across teams. We'll put each as
• . Benefits: paragraph: "Edward Jones' compensation and benefits package includes medical and prescription drug, dental, vision, voluntary benefits (such as accident, hospital indemnity, and critical illness), short- and long-term disability, basic life, and basic AD&D coverage. Short- and long-term disability, basic life, and basic AD&D coverage are provided at no cost to associates. Edward Jones offers a 401k retirement plan, and tax-advantaged accounts: health savings account, and flexible spending account. Edward Jones observes ten paid holidays and provides 15 days of vacation for new associates beginning on January 1 of each year, as well as sick time, personal days, and a paid day for volunteerism. Associates may be eligible for bonuses and profit sharing. All associates are eligible for the firm's Employee Assistance Program. For more information on the Benefits available to Edward Jones associates, please visit our benefits page." We can keep as

  or maybe break into list? The instruction: Use

  • for any list of duties/requirements/benefits. Benefits is a list; we could make a list. But we can also keep as prose. Safer to use list for benefits. Let's extract each benefit item: - medical and prescription drug - dental - vision - voluntary benefits (such as accident, hospital indemnity, and critical illness) - short- and long-term disability (provided at no cost) - basic life (provided at no cost) - basic AD&D coverage (provided at no cost) - 401k retirement plan - tax-advantaged accounts: health savings account, flexible spending account - ten paid holidays - 15 days of vacation for new associates beginning on January 1 of each year - sick time - personal days - paid day for volunteerism - bonuses and profit sharing (eligible) - Employee Assistance Program (all associates eligible) We could keep as list. Schedule: The sentence: "Candidates that live within a commutable distance from our Tempe, AZ and St. Louis, MO home office locations are expected to work in the office four days per week." That's schedule info. We'll put as

    . Now produce HTML fragment:

    About the role

    Join a financial services firm where your contributions are valued. Edward Jones is a Fortune 500¹ company where people come first. With over 9 million clients and 20,000 financial advisors across the U.S. and Canada, we’re proud to be privately-owned, placing the focus on our clients rather than shareholder returns. Behind everything we do is our purpose: We partner for positive impact to improve the lives of our clients and colleagues, and together, better our communities and society. We are an innovative, flexible, and inclusive organization that attracts, develops, and inspires performance excellence and a sense of belonging. People are at the center of our partnership. Edward Jones associates are seen, heard, respected, and supported. This is what we believe makes us the best place to start or build your career. View our Purpose, Inclusion and Citizenship Report. ¹Fortune 500, published June 2024, data as of December 2023. Compensation provided for using, not obtaining, the rating.

    Responsibilities

    • Design, develop, and maintain document-focused applications using modern technologies including Java, Spring Boot, REST APIs, React, JavaScript, Kubernetes, and related frameworks.
    • Leverage AI tools and prompt engineering techniques to enhance solutions, improve efficiency, and support innovation initiatives.
    • Build and integrate solutions using modern platforms and technologies such as Kafka, MongoDB, Oracle, and cloud-native services.
    • Translate business requirements into technical designs, specifications, development estimates, and scalable system solutions.
    • Lead complex development efforts through design, coding, testing, debugging, deployment, and ongoing maintenance.
    • Troubleshoot and resolve complex production issues while ensuring system stability, reliability, and performance.
    • Drive engineering excellence through code reviews, SDLC best practices, test automation, and observability-focused development.
    • Mentor and develop team members by providing technical guidance, promoting best practices, and fostering a culture of continuous learning.

    Requirements

    • Bachelor's degree in computer science, Engineering, MIS, or equivalent professional experience.
    • 5+ years of software engineering experience with expertise across application development, infrastructure, and full-stack solution delivery.
    • Strong proficiency in Java and/or JavaScript, with experience across multiple programming languages, frameworks, and development stacks.
    • Experience developing cloud-based, scalable, secure, and distributed solutions, preferably within Microsoft Azure environments.
    • Expertise in modern application architecture, including microservices, domain-driven design, design patterns, event-driven systems, and distributed caching.
    • Experience with relational and non-relational databases, APIs, messaging platforms, and modern integration technologies.
    • Experience with AI tools, AI prompting, low-code/no-code platforms, and Agile development methodologies.
    • Strong knowledge of test automation, distributed system testing, observability, production support, and enterprise-scale application operations.
    • Proven ability to mentor engineers, lead technical initiatives,