Team Leader - Technology

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We need to parse the posting. Let's extract content: - Opening paragraph: "This job posting is anticipated to remain open for 30 days, from 14-Sep-2026. The posting may close early due to the volume of applicants." This is metadata; we can drop or put in short p. - "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." That's about the company; could be "About the role"? Actually "About the role" is more about the job, but we have "Team Overview" and "What You'll Do". So we can have sections: Team Overview (maybe as About the role?), Responsibilities (What You'll Do), Requirements/Qualifications (What Experience You Need), Benefits (benefits paragraph). Pay and Schedule: Not explicitly given. There's mention of schedule: "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 (office days). So we can include Schedule section with that detail. Pay: Not mentioned; no compensation specifics. So we should NOT include Pay section. Benefits: There's a paragraph describing benefits: medical, prescription drug, dental, vision, voluntary benefits, short- and long-term disability, basic life, basic AD&D, 401k, HSA, FSA, ten paid holidays, 15 days vacation, sick time, personal days, paid day for volunteerism, bonuses/profit sharing, Employee Assistance Program. That's specific; include Benefits. Also there is mention of "Team Overview" which could be considered "About the role" or maybe we can treat as "About the role". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to pick appropriate headings from that list. We can have About the role (team overview), Responsibilities (What You'll Do), Requirements (What Experience You Need), Benefits, Schedule. Possibly also Qualifications? But Requirements and Qualifications may overlap; we can combine into Requirements. We'll not duplicate. We need to use

• for any list of duties/requirements/benefits. So for responsibilities list, we need to convert the bullet-like sentences into
  • . The responsibilities are given as sentences each starting with a verb. We'll make list items. Similarly for requirements: list of bullet-like sentences. Benefits: also list. Schedule: maybe just a paragraph. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from the posting. Let's extract each piece. First, metadata: "This job posting is anticipated to remain open for 30 days, from 14-Sep-2026. The posting may close early due to the volume of applicants." We can put in a short p at top (maybe not a heading). Also "Join a financial services firm ..." paragraph about company; could be part of About the role? Actually About the role should describe the role/team. The team overview is separate. So we could have About the role: maybe combine the introductory paragraph about firm and team overview? But we need to keep all info. Let's decide: Section About the role: include the introductory paragraph about Edward Jones (the firm description) and maybe the Team Overview? But the Team Overview is more specific about the role. The instruction says use headings like About the role, Responsibilities, etc. So we can put the firm description under About the role, and then maybe also include Team Overview as part of About the role? Or we could have About the role = firm description, and then a separate section for Team Overview? But we only allowed headings from the list; we could not add custom headings like "Team Overview". So we need to map content to those headings. The list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to fit all content into those. Thus: - About the role: could contain the firm description and maybe the Team Overview (since it's about the role). We'll include both paragraphs. - Responsibilities: "What You'll Do" list. - Requirements: "What Experience You Need" list (maybe also include education etc.) - Qualifications: maybe we could split education vs experience? But we can just put all under Requirements; Qualifications may be empty; we should not create empty sections. So we omit Qualifications. - Skills: maybe we could extract specific skills like Kubernetes, CI/CD, cloud platforms, etc. But those are already in requirements. Could create Skills section for technical skills. However we must not invent sections unless there is real specific content. The posting does mention specific skills: "Hands-on experience designing, deploying, and supporting distributed applications using Kubernetes, and CI/CD (Continuous Integration/Continuous Deployment) pipelines." "Experience deploying and managing cloud-based solutions across AWS, Azure, GCP, or OCI." "Understanding of technologies related to or dependent on the team's systems." "Knowledge of business system interactions, infrastructure dependencies, system controls, monitoring, etc." "Understanding system development methodologies and processes within IS (change management, QA, Project Life Cycle, etc.)". Those could be considered skills. But we already have them in requirements. To avoid duplication, we could keep them under Requirements and not create Skills. The instruction says prefer a few substantive sections over many thin ones. So we can combine. - Benefits: benefits paragraph. - Schedule: schedule info. - Pay: not present, omit. Thus final HTML:

    This job posting is anticipated to remain open for 30 days, from 14-Sep-2026. The posting may close early due to the volume of applicants.

    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.

    The Team Leader plans, directs, and leads a team of associates and contractors responsible for operation, regulatory compliance, support, development, security, quality, disaster recovery and implementation of technologies.

    Responsibilities

    • Align team activities, strategies, responsibilities and objectives with the firm’s strategic direction.
    • Develop and execute on-going improvements for processes related to the team (e.g. resource management and support processes).
    • Ensure prudent use of the firm’s financial resources.
    • Provide leadership, development, and mentoring to associates through examples and timely feedback.
    • Develop successors for key positions on their team.
    • Ensure the execution and quality of enhancements, support and projects.
    • Understanding of the team's systems, processes and technologies.
    • Manages and develops self while internalizing leadership feedback.
    • Establish and maintain effective communications and relationships across teams, departments, countries, vendors and other divisions.
    • Must be able to establish and maintain effective relationships with vendors while aligning to the firms' objectives.

    Requirements

    • Bachelor's degree preferred or related work experience.
    • Minimum of 5 years of experience directly related to Information Systems technology with at least 1 year in a leadership role (mentoring associates, lead analyst, project leaders, etc.).
    • Hands-on experience designing, deploying, and supporting distributed applications using Kubernetes, and CI/CD (Continuous Integration/Continuous Deployment) pipelines.
    • Experience deploying and managing cloud-based solutions across Amazon Web Services (AWS), Microsoft Azure, Google Cloud Platform (GCP), or Oracle Cloud Infrastructure (OCI).
    • Required understanding of technologies related to or dependent on the team's systems.
    • Knowledge of business system interactions, infrastructure dependencies, system controls, monitoring, etc.
    • Understanding system development methodologies and processes within IS (change management, QA, Project Life Cycle, etc.).
    • 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.
    Wait, the last bullet about schedule is actually schedule info; we moved it to Requirements but it's schedule. Better to put schedule in its own section. So we should remove that from Requirements and put under Schedule. Thus Requirements list excludes schedule line. Now Schedule section:

    Schedule

    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.

    Now Benefits section: We need to extract benefits paragraph and turn into list. 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 need to preserve all substantive information; we can make list items for each benefit. Let's break down: - medical and prescription drug - dental - vision - voluntary benefits (such as accident, hospital indemnity, and critical illness) - short- and long-term disability - basic life - basic