Sr. Manager Data Management
Charles Schwab · Southlake, TX · 3 wk ago
HybridInformation TechnologyFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. No placeholder like "commensurate with experience". We must not repeat job title as heading. No Job ID etc. Remove boilerplate.
We need to parse the posting.
Let's extract sections:
- About the role: The introductory paragraphs describing Schwab, Data Risk Enhancement team, role description. That's prose.
- Responsibilities: The bullet list of duties: "In this role, you will help shape and operationalize..." Actually that's a paragraph with multiple sentences describing responsibilities. Could be considered responsibilities. Also bullet list? Not explicit bullet list but sentences. Could treat as
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. No placeholder like "commensurate with experience". We must not repeat job title as heading. No Job ID etc. Remove boilerplate.
We need to parse the posting.
Let's extract sections:
- About the role: The introductory paragraphs describing Schwab, Data Risk Enhancement team, role description. That's prose.
- Responsibilities: The bullet list of duties: "In this role, you will help shape and operationalize..." Actually that's a paragraph with multiple sentences describing responsibilities. Could be considered responsibilities. Also bullet list? Not explicit bullet list but sentences. Could treat as - each responsibility.
Let's list responsibilities from text:
"You will help shape and operationalize how Schwab uses data lineage to drive risk based decision making.
You will work across business and technology teams to identify critical data flows, assess risk exposure across end to end lineages, and translate those insights into clear prioritization signals and actionable roadmaps.
You will define and apply risk criteria, surface tradeoffs, and mobilize teams to address the most material risks first.
You will also partner with stakeholders to operationalize metrics, track progress through targeted reporting, and escalate emerging risks to senior management—ensuring data lineage is not just documented, but actively used to improve the firm’s data risk posture."
That's responsibilities.
- Requirements: The "What you have Required Qualifications" list. That's a list of qualifications. Could be Requirements or Qualifications. We have both Requirements and Qualifications sections possible. The posting lumps them as "Required Qualifications". We could put under
Requirements
with - each bullet.
- Preferred Qualifications: separate list.
- Skills: maybe combine some skills from required qualifications? But we already have required qualifications covering skills. Could still have Skills section but might duplicate. The instruction: prefer few substantive sections over many thin ones. So we could combine Required Qualifications and Preferred Qualifications into one Qualifications section? But they ask to use headings like Qualifications, Skills, Benefits, Pay, Schedule. We can decide to have sections: About the role (maybe as
About the role
), Responsibilities, Requirements (or Qualifications), Preferred Qualifications, Benefits. Pay and Schedule not mentioned (no salary range given, only mention bonus eligibility). There's a line: "In addition to the salary range, this role is also eligible for bonus or incentive opportunities." That mentions salary range but not actual numbers, so we cannot create Pay section because no specific pay info. So we omit Pay. Schedule: not mentioned (they mention hybrid work flexibility but not schedule specifics). Could we create Schedule? The posting mentions Hybrid Work and Flexibility approach, but not specific schedule. Might be considered schedule info? It says "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." That's somewhat schedule but not explicit. Might be considered schedule but it's vague. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does mention benefits later. So we can include Benefits. For Schedule, we have mention of hybrid work flexibility but not specific schedule like "full-time", "Monday-Friday". Might be considered schedule info but it's not explicit. Safer to omit Schedule.
Thus sections: About the role, Responsibilities, Requirements (maybe combine required qualifications), Preferred Qualifications, Benefits.
We need to use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information, not invent or summarize away detail. So we need to include all bullet points exactly as given (or close). Must not drop any.
Let's extract required qualifications bullet points (they are sentences separated by periods). We'll turn each into
- .
Required Qualifications list:
- Experience identifying, analyzing, and mitigating data risk, particularly related to data integrity, quality, security, and privacy, with a pragmatic approach to balancing risk and business outcomes.
- Demonstrated ability to gather, analyze, and interpret data lineage and data flows across complex systems to understand how data is created, transformed, and consumed, and to identify where data risk concentrates across end to end processes.
- Strong analytical and critical thinking skills, with experience translating lineage and risk signals into clear prioritization insights that guide where remediation efforts should be focused.
- Ability to work through ambiguity to drive toward actionable outcomes, including mobilizing cross functional teams to address data risks across business and technology domains.
- Strong communication skills, with the ability to explain complex data lineage and data risk concepts to both technical and non technical stakeholders and influence decisions through clear, concise messaging.
- Experience operationalizing data risk metrics and indicators, monitoring trends, identifying root cause, and escalating emerging risks in a structured and timely manner.
- Proficiency with data governance, risk management, and metadata related tools and methodologies; familiarity with SQL, data structures, and data management policies.
- Strong attention to detail, sound judgment, and the ability to prioritize effectively in a fast paced, highly matrixed environment.
- Bachelor’s degree or 5+ years in data related fields.
- 5+ year hands on experience in on data strategy, data analytics, data science, data governance, and / or data engineering (note typo "in on". We'll preserve as is.)
- 5+ year hands on experience delivery of reporting solutions that quantify risk
- Proven track record leading and developing business change initiatives
We need to keep exactly as written, maybe preserve punctuation.
Preferred Qualifications list:
- Experience with and understanding of project management, agile planning and change management process in Schwab along with related tools like Jira.
- Ability to navigate and be successful in a highly matrixed organization
- Focused and versatile team player that is comfortable under pressure and with evolving objectives
- Excellent problem-solving and critical-thinking skills
Now Benefits list from "What’s in it for you" section:
- 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 earlier they mention: "We offer a competitive benefits package that takes care of the whole you – both today and in the future:" then list.
We should include that as Benefits.
Now About the role prose: combine introductory paragraphs up to "In this role, you will help shape..." Actually that part is responsibilities. So About the role includes paragraphs before responsibilities: "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(s). 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. Schwab Data is critical to the future of Schwab, as we seek to embrace and support new ways of using data (GenAI), embed additional insights and data-driven processes in our business, and respond to evolving needs and expectations in data governance. The Schwab Data organization collectively focuses on data strategy, data analytics, data science, data governance, and data engineering, while simultaneously enhancing data impact and data safety for our business and our clients. We will advance our impact in line with evolving data/analytics/AI technology and reinforce our ability to safely, responsibly, intentionally, and broadly utilize data, analytics, and AI. Within Schwab Data, the Data Risk Enhancement team’s purpose is to strengthen the firm’s ability to proactively identify, prioritize, and mitigate data risk. The team focuses on making data risk visible and actionable by leveraging data lineage and related insights to illuminate how data flows across the firm, where risk concentrates, and where intervention will have the greatest impact. Acting as a first line of defense, the team partners closely with data, analytics, and AI professionals to ensure data risks are understood in context and addressed in a way that supports both safety and business outcomes."
We need to preserve that as prose (
). Might be long but okay.
Now Responsibilities prose: we could either keep as
with sentences or
- . Since it's a list of duties, better to use
- . We'll split each sentence as
- . Ensure we keep the exact wording.
Responsibilities sentences:
- You will help shape and operationalize how Schwab uses data lineage to drive risk based decision making.
- You will work across business and technology teams to identify critical data flows, assess risk exposure across end to end lineages, and translate those insights into clear prioritization signals and actionable roadmaps.
- You will define and apply risk criteria, surface tradeoffs, and mobilize teams to address the most material risks first.
- You will also partner with stakeholders to operationalize metrics, track progress through targeted reporting, and escalate emerging risks to senior management—ensuring data lineage is not just documented, but actively used to improve the firm’s data risk posture.
Note the em dash; we keep.
Now Benefits list as
- .
Now we need to output only HTML fragment, no markdown fences.
Let's craft.
We'll start with
About the role
...
Then Responsibilities
...
Then Requirements
...
Then Preferred Qualifications
...
Then Benefits
...
Check for any duplicate or boilerplate: we removed EEO etc.
Check that we didn't include Job ID etc.
Now ensure we didn't miss any substantive info: The line "In addition to the salary range, this role is also eligible for bonus or incentive opportunities." This is about Pay/Bonus. Since we are not making Pay section (no specific salary), but we could include this sentence somewhere maybe under Benefits? It's about compensation. Could be placed under Benefits? But Benefits section is for benefits like 401k etc. The bonus eligibility is compensation, not benefit. Since we don't have Pay section, maybe we could add a short under Benefits or after Responsibilities? But instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state bonus eligibility, which is pay-related. However we don't have exact salary range, but we have mention of bonus eligibility. Should we create a Pay section? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state bonus eligibility, which is part of pay. So we could create a Pay section with that sentence. However the rule also says: "Prefer a few substantive sections over many thin ones." Adding a Pay section with just one sentence might be thin. But we could incorporate that sentence into Benefits? It's not a benefit but compensation. Could we add a
after Benefits? The instruction says to use
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So if we include Pay, we need heading Pay
. The content would be the sentence about bonus eligibility. That's substantive (not placeholder). It's okay to have a thin section if it's real content. The instruction says prefer few substantive sections over many thin ones, but not forbid thin ones if they have real content. So we could add Pay section.
Similarly, Schedule: they mention hybrid work flexibility but not explicit schedule. Could we create Schedule section with that description? It's about hybrid work and flexibility. That is schedule-related. The posting says: "Our Hybrid Work and
Requirements
with- each bullet.
- Preferred Qualifications: separate list.
- Skills: maybe combine some skills from required qualifications? But we already have required qualifications covering skills. Could still have Skills section but might duplicate. The instruction: prefer few substantive sections over many thin ones. So we could combine Required Qualifications and Preferred Qualifications into one Qualifications section? But they ask to use headings like Qualifications, Skills, Benefits, Pay, Schedule. We can decide to have sections: About the role (maybe as
About the role
), Responsibilities, Requirements (or Qualifications), Preferred Qualifications, Benefits. Pay and Schedule not mentioned (no salary range given, only mention bonus eligibility). There's a line: "In addition to the salary range, this role is also eligible for bonus or incentive opportunities." That mentions salary range but not actual numbers, so we cannot create Pay section because no specific pay info. So we omit Pay. Schedule: not mentioned (they mention hybrid work flexibility but not schedule specifics). Could we create Schedule? The posting mentions Hybrid Work and Flexibility approach, but not specific schedule. Might be considered schedule info? It says "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." That's somewhat schedule but not explicit. Might be considered schedule but it's vague. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does mention benefits later. So we can include Benefits. For Schedule, we have mention of hybrid work flexibility but not specific schedule like "full-time", "Monday-Friday". Might be considered schedule info but it's not explicit. Safer to omit Schedule. Thus sections: About the role, Responsibilities, Requirements (maybe combine required qualifications), Preferred Qualifications, Benefits. We need to usefor each section heading. Use
- for any list of duties/requirements/benefits. Use
for prose. We must preserve all substantive information, not invent or summarize away detail. So we need to include all bullet points exactly as given (or close). Must not drop any. Let's extract required qualifications bullet points (they are sentences separated by periods). We'll turn each into
- .
Required Qualifications list:
- Experience identifying, analyzing, and mitigating data risk, particularly related to data integrity, quality, security, and privacy, with a pragmatic approach to balancing risk and business outcomes.
- Demonstrated ability to gather, analyze, and interpret data lineage and data flows across complex systems to understand how data is created, transformed, and consumed, and to identify where data risk concentrates across end to end processes.
- Strong analytical and critical thinking skills, with experience translating lineage and risk signals into clear prioritization insights that guide where remediation efforts should be focused.
- Ability to work through ambiguity to drive toward actionable outcomes, including mobilizing cross functional teams to address data risks across business and technology domains.
- Strong communication skills, with the ability to explain complex data lineage and data risk concepts to both technical and non technical stakeholders and influence decisions through clear, concise messaging.
- Experience operationalizing data risk metrics and indicators, monitoring trends, identifying root cause, and escalating emerging risks in a structured and timely manner.
- Proficiency with data governance, risk management, and metadata related tools and methodologies; familiarity with SQL, data structures, and data management policies.
- Strong attention to detail, sound judgment, and the ability to prioritize effectively in a fast paced, highly matrixed environment.
- Bachelor’s degree or 5+ years in data related fields.
- 5+ year hands on experience in on data strategy, data analytics, data science, data governance, and / or data engineering (note typo "in on". We'll preserve as is.)
- 5+ year hands on experience delivery of reporting solutions that quantify risk
- Proven track record leading and developing business change initiatives
We need to keep exactly as written, maybe preserve punctuation.
Preferred Qualifications list:
- Experience with and understanding of project management, agile planning and change management process in Schwab along with related tools like Jira.
- Ability to navigate and be successful in a highly matrixed organization
- Focused and versatile team player that is comfortable under pressure and with evolving objectives
- Excellent problem-solving and critical-thinking skills
Now Benefits list from "What’s in it for you" section:
- 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 earlier they mention: "We offer a competitive benefits package that takes care of the whole you – both today and in the future:" then list.
We should include that as Benefits.
Now About the role prose: combine introductory paragraphs up to "In this role, you will help shape..." Actually that part is responsibilities. So About the role includes paragraphs before responsibilities: "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(s). 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. Schwab Data is critical to the future of Schwab, as we seek to embrace and support new ways of using data (GenAI), embed additional insights and data-driven processes in our business, and respond to evolving needs and expectations in data governance. The Schwab Data organization collectively focuses on data strategy, data analytics, data science, data governance, and data engineering, while simultaneously enhancing data impact and data safety for our business and our clients. We will advance our impact in line with evolving data/analytics/AI technology and reinforce our ability to safely, responsibly, intentionally, and broadly utilize data, analytics, and AI. Within Schwab Data, the Data Risk Enhancement team’s purpose is to strengthen the firm’s ability to proactively identify, prioritize, and mitigate data risk. The team focuses on making data risk visible and actionable by leveraging data lineage and related insights to illuminate how data flows across the firm, where risk concentrates, and where intervention will have the greatest impact. Acting as a first line of defense, the team partners closely with data, analytics, and AI professionals to ensure data risks are understood in context and addressed in a way that supports both safety and business outcomes."
We need to preserve that as prose (
). Might be long but okay. Now Responsibilities prose: we could either keep as
with sentences or
- . Since it's a list of duties, better to use
- . We'll split each sentence as
- . Ensure we keep the exact wording.
Responsibilities sentences:
- You will help shape and operationalize how Schwab uses data lineage to drive risk based decision making.
- You will work across business and technology teams to identify critical data flows, assess risk exposure across end to end lineages, and translate those insights into clear prioritization signals and actionable roadmaps.
- You will define and apply risk criteria, surface tradeoffs, and mobilize teams to address the most material risks first.
- You will also partner with stakeholders to operationalize metrics, track progress through targeted reporting, and escalate emerging risks to senior management—ensuring data lineage is not just documented, but actively used to improve the firm’s data risk posture.
Note the em dash; we keep.
Now Benefits list as
- .
Now we need to output only HTML fragment, no markdown fences.
Let's craft.
We'll start with
About the role
...
ThenResponsibilities
- ...
Requirements
- ...
Preferred Qualifications
- ...
Benefits
- ...
under Benefits or after Responsibilities? But instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state bonus eligibility, which is pay-related. However we don't have exact salary range, but we have mention of bonus eligibility. Should we create a Pay section? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state bonus eligibility, which is part of pay. So we could create a Pay section with that sentence. However the rule also says: "Prefer a few substantive sections over many thin ones." Adding a Pay section with just one sentence might be thin. But we could incorporate that sentence into Benefits? It's not a benefit but compensation. Could we add a
after Benefits? The instruction says to use
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So if we include Pay, we need heading
Pay
. The content would be the sentence about bonus eligibility. That's substantive (not placeholder). It's okay to have a thin section if it's real content. The instruction says prefer few substantive sections over many thin ones, but not forbid thin ones if they have real content. So we could add Pay section. Similarly, Schedule: they mention hybrid work flexibility but not explicit schedule. Could we create Schedule section with that description? It's about hybrid work and flexibility. That is schedule-related. The posting says: "Our Hybrid Work and
- .
Now we need to output only HTML fragment, no markdown fences.
Let's craft.
We'll start with
- . Since it's a list of duties, better to use
- for any list of duties/requirements/benefits. Use