Sr 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: - Intro: "Your opportunity At Schwab..." maybe about the role. Could be "About the role" section. - Then description of role uniqueness: "Why is this role unique..." includes responsibilities: lead CCAT initiatives, lead team, deliver greenfield functionality, etc. So we can put responsibilities. - Then "What you have" includes required qualifications: bullet list of qualifications. That's "Requirements" or "Qualifications". We need to decide which sections to use. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). So we can have both Requirements and Qualifications? Might be redundant. Usually Requirements = qualifications. But we can separate: Requirements (experience) and Qualifications (education). However we need to avoid thin sections. Let's see content: Required Qualifications includes Bachelor's degree, 8+ years experience with Java etc, 4-6 years experience with distributed DBs, 4+ years real-time data, etc. That's a mix of education and experience. Could put under "Requirements". Could also have "Qualifications" for education only. But we have only education bullet: Bachelor's degree. That's thin. Better to combine into one section "Requirements". The instruction says prefer a few substantive sections over many thin ones. So we will have sections: About the role, Responsibilities, Requirements, Benefits. Possibly Skills? The posting includes skills like interpersonal, analytical, etc. Those could be under Skills. But we already have many skill-like items in Requirements. Could separate: Requirements (hard technical qualifications) and Skills (soft skills). Let's see: after the list of technical qualifications, there is: "Knowledge of the Agile methodology... Experience with the Atlassian tool stack... Project delivery with ability to drive projects... Prior experience interfacing with various partners... Strong interpersonal, analytical, problem-solving, influencing, prioritization, decision- making and conflict resolution skills Excellent written/verbal communication skills Applicants must be currently authorized to work in the United States on a full-time basis without employer sponsorship. In addition to the salary range, this role is also eligible for bonus or incentive opportunities". So we have soft skills, Agile, Atlassian, project delivery, interpersonal, communication, work authorization, bonus eligibility. Those could go under Skills or Requirements. Since we already have a Requirements section for technical qualifications, we can put soft skills etc under Skills. Benefits: The posting lists benefits: 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. That's benefits. Pay: The posting mentions "In addition to the salary range, this role is also eligible for bonus or incentive opportunities". No actual salary range given. So we cannot create Pay section because no specific salary range. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits we have specific content, so we can include Benefits. Pay we do not have specific salary range, only mention bonus eligibility but no numbers. So we should not include Pay section. Schedule: The posting mentions Hybrid Work and Flexibility approach, but not specific schedule like full-time, hours. It says "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." That's somewhat schedule info but not explicit. Might be considered schedule? The instruction: only create Schedule if posting actually states them. It does mention hybrid work flexibility, but not specific schedule like "full-time", "Monday-Friday". Could be considered schedule info but it's vague. Safer to omit Schedule. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits. Now we need to format: Use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not include boilerplate like EEO etc. The posting didn't have explicit boilerplate besides maybe some generic statements but we must remove cookie/navigation/legal/EEO etc. The given text seems clean. We need to ensure we include all substantive info: Let's extract. About the role: The first paragraph: "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. Schwab Technology Services enables the future of how clients manage their money by providing innovative and reliable technology products and services as part of our ongoing commitment to democratize access to investing and financial planning. CCAT (Corporate Customer & Account Technology) is a tower in CDT (Client Data Technology), with a mission to establish unified customer identifier to support comprehensive 360 view of Schwab client across all line of business. CCAT identifies the same customer across different Schwab affiliates and bring each instance under the umbrella of single Schwab Customer Identifier (SCID) that enables the enterprise to take holistic view of customer to drive more focused service and offerings." That's about the role and context. We'll put that as prose in

  maybe multiple paragraphs. Then "Why is this role unique and how it differentiates with other opportunities" followed by bullet-like sentences: "Lead CCAT initiatives that enables the enterprise to grow and offer new capabilities to its clients.Lead a motivated team to deliver net-new, greenfield functionality that directly impacts clientsThis role sits at the intersection of velocity, ownership, and growth: you’ll lead a motivated team inside a fast paced organization where decisions are made quickly and great ideas ship.You’ll lead greenfield initiatives, learn and applyOwn end-to-end delivery of client-facing functionality (from scoping to production rollout) that materially advances product and business goals.Provide technical guidance to the team of developers and support them over come implementation & delivery challengesDelivery Java Projects on cloud (GCP)". This is a bit run-on but we can split into list items. We'll create

  • for each duty. Then "What you have" section: list of qualifications. We'll separate into Requirements (hard technical) and Skills (soft). Let's parse. Required Qualifications bullet list: - Bachelor’s degree in Engineering, Computer Science, or related field. - 8+ years of experience with the following: Java, Spring framework, cloud development, and Web Services (REST and SOAP) supporting high volume transactions in a Highly Available environment - 4-6 years of experience in Distributed Databases and NoSQL databases; PostgresSQL (preferred), MongoDB, Yugabyte. - 4+ year experience working on real-time data and streaming applications - 4+ years of experience with continuous build process using Bamboo, Bitbucket/Git, or similar tools - 3+ years of experience with GCP and /or AWS / Azure - 3+ years of experience with event-driven systems (Kafka, RabbitMQ, message queues, etc.) - 2+ years of experience in Cloud deployment in a CI/CD delivery model. - 1+ years of experience with batch jobs or data pipeline frameworks like Spring Batch, PySpark etc. - Knowledge of the Agile methodology and experience in an Agile working environment - Experience with the Atlassian tool stack (JIRA et alia) - Project delivery with ability to drive projects to successful completion; ability to anticipate project risks/issues and propose creative solutions. - Prior experience interfacing with various partners, including vendors, offshore development teams, and internal groups - Strong interpersonal, analytical, problem-solving, influencing, prioritization, decision- making and conflict resolution skills - Excellent written/verbal communication skills - Applicants must be currently authorized to work in the United States on a full-time basis without employer sponsorship. - In addition to the salary range, this role is also eligible for bonus or incentive opportunities We need to split: Requirements (hard technical) maybe include education + years of experience with specific tech. Skills: Agile, Atlassian, project delivery, interpersonal, communication, work authorization, bonus eligibility. But the instruction: "Prefer a few substantive sections over many thin ones." Could combine all into Requirements and not have Skills. However we have many items; still one section may be long but okay. But we also have Benefits separate. We could have Requirements (includes education, experience, technical, Agile, Atlassian, project delivery, interpersonal, communication, work auth, bonus). That's one big section. Then Benefits separate. But we also have About the role and Responsibilities. Thus sections: About the role, Responsibilities, Requirements, Benefits. That's four sections, each substantive. Let's verify we have content for each. About the role: we have the introductory paragraphs. Responsibilities: we have the unique role bullets. Requirements: we have all qualifications list. Benefits: we have the benefits list. Now we must not include Pay or Schedule. Now format. We need to output only HTML fragment, no /, no markdown fences. We'll produce:

    About the role

    ...

    maybe multiple

    for readability. But we can combine multiple sentences into one

    if we want. The instruction: use

    for prose. So each paragraph can be a

    . We'll split logically. Let's craft About the role content: Paragraph 1: "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." Paragraph 2: "Schwab Technology Services enables the future of how clients manage their money by providing innovative and reliable technology products and services as part of our ongoing commitment to democratize access to investing and financial planning." Paragraph 3: "CCAT (Corporate Customer & Account Technology) is a tower in CDT (Client Data Technology), with a mission to establish unified customer identifier to support comprehensive 360 view of Schwab client across all line of business. CCAT identifies the same customer across different Schwab affiliates and bring each instance under the umbrella of single Schwab Customer Identifier (SCID) that enables the enterprise to take holistic view of customer to drive more focused service and offerings." Now Responsibilities: we need list items. We'll extract each duty: - Lead CCAT initiatives that enables the enterprise to grow and offer new capabilities to its clients. - Lead a motivated team to deliver net-new, greenfield functionality that directly impacts clients. - This role sits at the intersection of velocity, ownership, and growth: you’ll lead a motivated team inside a fast paced organization where decisions are made quickly and great ideas ship. - You’ll lead greenfield initiatives, learn and apply. - Own end-to-end delivery of client-facing functionality (from scoping to production rollout) that materially advances product and business goals. - Provide technical guidance to the team of developers and support them overcome implementation & delivery challenges. - Delivery Java Projects on cloud (GCP). We need to ensure we preserve all info; some sentences are fragmented but we keep as is. Now Requirements: list items. We'll list each qualification as

  • . Must preserve exact wording. Let's list: - Bachelor’s degree in Engineering, Computer Science, or related field. - 8+ years of experience with the following: Java, Spring framework, cloud development, and Web Services (REST and SOAP) supporting high volume transactions in a Highly Available environment