Manager, Software Development & Engineering

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes description, responsibilities, qualifications, etc. There's no explicit Pay or Schedule details (except mention of hybrid work but not schedule). There's mention of benefits. So we should include sections: About the role (maybe intro), Responsibilities, Requirements (maybe combine qualifications?), Skills, Benefits. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose which headings to include. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. We need to preserve all substantive information. So we need to extract content. Let's parse the posting: Intro: "Your opportunity At Schwab, you’re empowered to make an impact on your career. Here, innovative thought meets creative problem solving, helping us “challenge the status quo” and transform the finance industry together. We believe in the importance of in-office collaboration and fully intend for the selected candidate for this role to work on site in the specified location. We are seeking an experienced Full Stack Developer to build customer-facing and backend applications for Schwab's Advisor Center Platform, delivering client-centric solutions that improve speed, quality, and efficiency. The ideal candidate brings a strong ownership, a focus on delivery, and a commitment to engineering excellence. You are energized by Test-Driven Development and apply it to build reliable, maintainable systems within modern CI/CD practices. In this role, you will influence technical direction, mentor engineers, and consistently deliver high-quality software that meets both business and client needs. In this role, you will partner closely with technical leads, product owners, and business stakeholders to define and deliver features that drive new capabilities. You will take a hands-on approach to development - writing high-quality code, performing code reviews, contributing to design decisions, and resolving production issues to ensure reliable delivery. You will apply strong software design expertise to build scalable, adaptable solutions, contributing to both new feature development and ongoing improvements. Collaboration is central to the role, working across engineering, architecture, and product teams to align on platform standards and ensure quality and consistency. A key expectation is to lead by example—mentoring junior engineers, supporting their career growth, and helping raise the overall technical bar of the team. You will stay closely connected to user needs by engaging with UX research and feedback, ensuring that what you build is client-focused and aligned to measurable business outcomes." That's basically the role description and responsibilities. Then "What you have To ensure that we have fulfilled our promise of "challenging the status quo," this role has specific qualifications that successful candidates should have." Then "Required Qualifications" list bullet points. Then "Preferred Qualifications" list. Then "In addition to the salary range, this role is also eligible for bonus or incentive opportunities" Then "What’s in it for you At Schwab, you’re empowered to shape your future. We champion your growth through meaningful work, continuous learning, and a culture of trust and collaboration—so you can build the skills to make a lasting impact. Our Hybrid Work and Flexibility approach balances our ongoing commitment to workplace flexibility, serving our clients, and our strong belief in the value of being together in person on a regular basis. We offer a competitive benefits package that takes care of the whole you – both today and in the future: 401(k) with company match and Employee stock purchase planPaid time for vacation, volunteering, and 28-day sabbatical after every 5 years of service for eligible positionsPaid parental leave and family building benefitsTuition reimbursementHealth, dental, and vision insurance" We need to extract benefits list. We need to avoid duplication. We need to output HTML with sections. Let's decide sections: - About the role: maybe the introductory paragraph(s) describing opportunity and role overview. - Responsibilities: list of duties (influence technical direction, mentor engineers, partner with leads, hands-on development, code reviews, design decisions, resolve production issues, apply software design, collaborate across teams, mentor junior engineers, stay connected to user needs). Could be bullet list. - Requirements: maybe combine Required Qualifications and Preferred Qualifications? But we have separate headings Requirements and Qualifications. The instruction list includes both Requirements and Qualifications as possible headings. We could put Required Qualifications under Requirements, and Preferred Qualifications under Qualifications (or Skills). However they said "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can include both Requirements and Qualifications if we have content. We need to decide what goes where. Typically Requirements = mandatory qualifications; Qualifications = preferred or additional qualifications. Skills could be specific technical skills list. But we have a lot of technical skills in Required Qualifications: HTML, Javascript, CSS, Angular, .NET web and service development using C#, etc. Also CI/CD, TDD, etc. Could be placed under Skills. We need to avoid filler like "commensurate with experience". Not present. We need to preserve all substantive info. So we need to include all bullet points from Required and Preferred Qualifications, maybe also the line about bonus/incentive. We also have Hybrid Work and Flexibility description; could be part of Benefits or maybe Schedule? But schedule not given. Hybrid work could be considered under Benefits or maybe a separate section like Work Arrangement but not in allowed headings. Could fold into Benefits or About the role. We should not create Pay or Schedule sections unless posting actually states them. It mentions salary range but not actual numbers, just says "In addition to the salary range, this role is also eligible for bonus or incentive opportunities". That's not a specific pay figure, but it's mention of salary range and bonus eligibility. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state that there is a salary range and bonus eligibility. So we could include a Pay section with that statement. However they said "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The posting says "In addition to the salary range, this role is also eligible for bonus or incentive opportunities". That's not a placeholder; it's a statement about eligibility. So we could include Pay section with that sentence. Schedule: Not mentioned besides hybrid work and in-office expectation. Not a specific schedule. So we should not create Schedule section. Benefits: we have details. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We need to avoid duplication: ensure we don't repeat same info across sections. Let's extract content. About the role: Could be the first paragraph(s) up to "We are seeking an experienced Full Stack Developer..." maybe include the motivational statements. Responsibilities: bullet list of duties. Requirements: Required Qualifications bullet list. Qualifications: Preferred Qualifications bullet list. Skills: maybe list of specific technical skills extracted from Required Qualifications (HTML, Javascript, CSS, Angular, .NET web and service development using C#, CI/CD, TDD, BDD, micro-services, cloud infrastructure, API test automation, etc). But we already have them in Requirements; maybe we should not duplicate. Could instead put Skills as a summary of technical competencies. But we need to preserve all substantive info; we can keep them in Requirements and not repeat in Skills. However we need to include a Skills section only if we have specific content not already covered. Could combine Required Qualifications into Skills and Requirements? Hmm. Better: Use Requirements for mandatory qualifications (including education, experience, etc). Use Qualifications for preferred qualifications. Use Skills for technical skills list (maybe extracted from both). But that would cause duplication. However the instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is not prohibited but might be redundant. It's okay to repeat? Probably better to avoid duplication but still preserve info. We could put technical skills under Skills and keep other qualifications (education, experience, mentoring, etc) under Requirements. Preferred qualifications under Qualifications. Let's parse Required Qualifications bullet points: - A passion for digital innovation and commitment to superb client experience - BS or MS degree in Engineering or Computer Science - 8+ years of full stack application development experience and experience mentoring/assisting junior team developers on team - Proven experience developing and implementing applications, particularly web-enabled applications using: HTML, Javascript, CSS, Angular. - .NET web and service development using C# - Solid understanding in web application environments and development tools, session state management, web configuration and deployment strategies, security and performance tuning, and debugging methodologies. - Prior hands-on experience in developing and deploying micro-services solutions on cloud infrastructure - Comfortable with continuous integration and continuous deployment (CI/CD) concepts, unit testing principles and implementations, API test automation techniques as well as automated deployment pipeline tools - Solid understanding of resiliency and disaster recovery using Cloud native solutions - Must have exposure to Test Driven Development and Behavior Driven Development techniques - Must possess excellent verbal and written communication skills - Effective time management. Must be able to prioritize and multi-task effectively - Have a passion for problem solving, the ability to quickly learn new concepts, and must be able to interact with all levels of technical and business teams - Be a team player, self-motivated and able to work collaboratively across organizations and geographic locations. Preferred Qualifications bullet points: - Experience with Atlassian tool suite is strongly preferred: JIRA, Confluence, Bamboo - Experience with GITHUB CI/CD tools - Experience building cloud ready applications using IAAS/PASS concepts in AWS, Azure, Private Cloud (preferably Pivotal Cloud Foundry) or similar cloud infrastructure - Strong interpersonal, analytical, problem solving and organizational skills Also note: "In addition to the salary range, this role is also eligible for bonus or incentive opportunities" - for Pay. Benefits list: - 401(k) with company match and Employee stock purchase plan - Paid time for vacation, volunteering, and 28-day sabbatical after every 5 years of service for eligible positions - Paid parental leave and family building benefits - Tuition reimbursement - Health, dental, and vision insurance Also mention Hybrid Work and Flexibility approach: "Our Hybrid Work and Flexibility approach balances our ongoing commitment to workplace flexibility, serving our clients, and our strong belief in the value of being together in person on a regular basis." Could be part of Benefits or About the role. Since Benefits section is for benefits package, we could include hybrid work as part of Benefits (work flexibility). But it's not a benefit per se; it's work arrangement. Could be placed under About the role or maybe a separate section but not allowed. We'll include it in About the role or maybe under Benefits as a note. We need to avoid boilerplate like EEO etc. Not present. Now craft HTML. We'll start with

About the role

then

containing the introductory paragraphs (maybe two paragraphs). We'll combine the opportunity statement and role description. Then

Responsibilities

then

• each duty. Then

  Requirements

  then
  • each required qualification. Then

    Qualifications

    then
    • each preferred qualification. Then

      Skills

      maybe we could list technical skills extracted: HTML, Javascript, CSS, Angular, .NET web and service development using C#, CI/CD, unit testing, API test automation, automated deployment pipeline, micro-services, cloud infrastructure, resiliency/disaster recovery, TDD, BDD. But that duplicates with Requirements. However we could keep Skills as a concise list of technical competencies, while Requirements includes education, experience, soft skills etc. That would avoid duplication of the same bullet points but still preserve info (the technical skills are still present). However the Required Qualifications bullet includes those technical skills as part of sentences; we could extract them. Let's decide