Sr. Director - Microsoft Data & AI
SHI International Corp. · Texas, United States · 1 mo ago
RemoteRemoteEngineering$225k–$325k/yrFull-time
We need to output only HTML fragment, using for section headings,
for section headings, - for lists,
for prose. No markdown fences. No html/body tags. Need to include sections only when posting has real specific content. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate etc.
We need to parse the job posting content.
We have sections: About Us (company description) – but we should not repeat job title as heading. The page already shows it. Should we include About Us? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So they suggest typical headings. But we can also include other headings if they have content? The instruction says: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can include sections like About Us if it's substantive. However they gave examples of headings; but we can use any heading as long as it's appropriate. Probably we should follow typical sections: About the role (Job Summary), Responsibilities (Role Description broken into subparts), Requirements (Skill Level Requirements, Other Requirements), Qualifications maybe same as Requirements, Skills maybe part of Requirements, Benefits, Pay, Schedule.
We need to decide what to include.
Let's extract content:
- About Us: description of SHI International Corp. This is substantive. Should we include as a section? Possibly "About the company" but not in list. Could use About SHI
. But they didn't list that as example but it's okay. However they said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests they expect those headings. But they didn't forbid other headings. Safer to stick to those headings. So we can map content to those headings.
- Job Summary: we can put under About the role
(or maybe "Job Summary").
- Responsibilities: The Role Description includes many bullet-like paragraphs. We can extract responsibilities as list items.
- Requirements: Skill Level Requirements and Other Requirements.
- Qualifications: maybe same as Requirements; but we could combine.
- Skills: maybe part of Requirements.
- Benefits: The posting mentions "Health, wellness, and financial benefits to offer peace of mind to you and your family." Also "World-class facilities and the technology you need to thrive – in our offices or yours." Also "Continuous professional growth and leadership opportunities." Also "If You Join Our Team, You’ll Enjoy Our commitment to diversity, as the largest minority- and woman-owned enterprise in the U.S." That's benefits. So we can include Benefits section.
- Pay: The posting includes "The estimated annual pay range for this position is $225,000 - $325,000 which includes a base salary and bonus." Also "The compensation for this position is dependent on job-related kn" (cut off). We have pay range. So we can include Pay.
- Schedule: Not mentioned explicitly. There's remote position with home office setup based in certain cities. No schedule like full-time, part-time. Not given. So we should not include Schedule section.
We must not include placeholder like "commensurate with experience". We have actual pay range.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include details from About Us, Job Summary, Responsibilities (the role description paragraphs), Requirements (skill level, other requirements), Benefits, Pay.
We must not repeat job title as heading. Not include Job ID etc.
We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting didn't have those obviously.
We need to output only HTML fragment.
Let's structure:
About SHI
maybe but they said About the role. However About Us is not about the role. Could we put About Us under About the role? Might be confusing. Perhaps we should include a section "About the company" but not in examples. The instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but they gave examples. Safer to stick to those examples. So we could treat About Us as part of "About the role"? Not ideal. Maybe we can omit About Us because it's not strictly about the role, but it's substantive. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must include About Us info somewhere. If we don't have a heading for it, we could put it in a
without heading? But they said use
for section headings (e.g. About the role, Responsibilities...). It doesn't say every paragraph must be under a heading; we could have a
at top without heading? Probably they expect sections with headings. But we could include a heading like "About SHI" even if not in examples; it's still a section heading. The instruction didn't forbid other headings; it just gave examples. So I think it's okay.
Thus we will include:
About SHI
Since 1989, SHI International Corp. has helped organizations change the world through technology. We’ve grown every year since, and today we’re proud to be a $16 billion global provider of IT solutions and services. Over 17,000 Organizations Worldwide Rely On SHI’s Concierge Approach To Help Them Solve What’s Next. But The Heartbeat Of SHI Is Our Employees – All 7,000 Of Them. If You Join Our Team, You’ll Enjoy Our commitment to diversity, as the largest minority- and woman-owned enterprise in the U.S. Continuous professional growth and leadership opportunities. Health, wellness, and financial benefits to offer peace of mind to you and your family. World-class facilities and the technology you need to thrive – in our offices or yours.
Note: The text includes some capitalization weirdness; we preserve as is.
Next, About the role
with Job Summary.
Job Summary paragraph: "The Senior Director, Data & AI leads SHI's AI + Infrastructure organization within the Microsoft Services Practice. This leader brings together Agentic Solutions, Cloud Platform, Data & Intelligence, and AI Security & Governance to build and deliver connected Microsoft solutions across Azure, Microsoft Fabric, Microsoft Foundry, agents, data platforms, and the security and governance capabilities required to operate them responsibly. The Senior Director runs the organization as a business, with ownership of service maturity, solution development, headcount planning, utilization, delivery quality, capacity, pipeline support, and measurable client outcomes. This role leads managers and practice leaders responsible for Agentic Solutions, Cloud Platform, Data & Intelligence, and AI Security & Governance and remains accountable for their effectiveness, development, and delivery performance. Aligned to Microsoft's Fabric IQ and Foundry IQ investments, this role connects cloud foundation, business data, enterprise knowledge, agentic experiences, and trust. The Senior Director helps SHI move clients from isolated pilots to secure, governed, production-ready platforms and solutions while creating repeatable paths for growth. This role sits at the center of SHI's Microsoft Services growth plan, turning Fabric IQ and Foundry IQ alignment into a working operating model that builds stronger solutions, improves delivery execution, develops talent, and creates repeatable paths for growth. This is a remote position with a Home Office setup based in New York City, Charlotte, Chicago, Atlanta, Austin, Denver, Los Angeles, San Francisco, or Seattle."
We'll put that in .
Next,
Responsibilities
. We need to extract responsibilities from Role Description. The Role Description includes several subheadings: Strategic Leadership and Practice Development, People Leadership Through Managers and Directors, Technical Direction Across Data, AI, and Security, Delivery Excellence and Client Outcomes, Business Growth and Market Development, Executive and Cross-Functional Communication. Each has multiple sentences. We can turn each sentence or clause into list items. Must preserve all substantive info; we should not lose detail. We'll create with - for each distinct responsibility.
Let's parse:
Strategic Leadership and Practice Development:
- Set and execute a unified direction for AI + Infrastructure, connecting Agentic Solutions, Cloud Platform, Data & Intelligence, and AI Security & Governance through one operating model.
- Translate Microsoft's Fabric IQ, Foundry IQ, Azure, and agent investments into a clear SHI services roadmap, capability plan, and investment agenda.
- Establish clear ownership, decision rights, handoffs, delivery standards, and quality expectations across the organization.
- Build modular, repeatable offerings that combine cloud, data, AI, and governance capabilities around defined customer outcomes.
- Use portfolio, pipeline, delivery, and capacity data to prioritize investments, manage tradeoffs, and improve practice health.
People Leadership Through Managers and Directors:
- Lead, coach, and develop the leaders responsible for Agentic Solutions, Cloud Platform, Data & Intelligence, and AI Security & Governance.
- Set measurable expectations for customer experience, delivery quality, utilization, capability development, financial performance, and team health.
- Build leadership depth through regular one-on-ones, development planning, succession planning, and clear career paths.
- Own workforce planning across the organization, including hiring, onboarding, retention, skills development, and capacity alignment to backlog and pipeline.
- Create a culture of shared accountability in which teams solve for the full customer outcome rather than optimize isolated technology workstreams.
Technical Direction Across Data, AI, and Security:
- Maintain a platform-aware perspective across Agent 365, Copilot Studio, Microsoft Foundry, Model Context Protocol, Azure, landing zones, platform engineering, FinOps, Microsoft Fabric, OneLake, data engineering, data visualization, and data readiness.
- Embed Entra Agent ID, Microsoft Purview, Defender for Cloud and AI, Security Copilot, Microsoft Sentinel, and Defender XDR into AI and platform solutions where those capabilities strengthen identity, data protection, observability, governance, and threat protection.
- Sponsor reusable reference architectures, delivery frameworks, statements of work, work breakdown structures, templates, and accelerators.
- Rely on practice leaders and principal architects for deep technical direction while maintaining alignment across disciplines.
- Create a practical path from assessment and platform readiness through implementation, adoption, optimization, and transition to managed services.
Delivery Excellence and Client Outcomes:
- Provide executive oversight for complex, multi-workstream engagements that span cloud, data, AI, agents, security, and governance.
- Hold leaders accountable for scope quality, staffing readiness, delivery methodology, risk management, timelines, budgets, and customer communication.
- Review project health, utilization, realization, margin, capacity, and quality signals and act early when performance moves off plan.
- Protect customer trust by ensuring teams make supportable commitments, apply appropriate governance, and transition solutions into sustainable operations.
- Serve as an executive sponsor and trusted advisor for strategic clients, connecting platform decisions to measurable business outcomes.
Business Growth and Market Development:
- Grow AI + Infrastructure services revenue by improving solution relevance, supporting strategic pursuits, expanding enterprise client relationships, and developing repeatable offers.
- Partner with Solution Architecture, Sales, Project Management, Digital Workplace, and Managed Services to shape opportunities and deliver connected customer outcomes.
- Manage utilization, capacity, backlog, pipeline health, and delivery performance to improve profitability and support sustainable growth.
- Build strong relationships with Microsoft field, engineering, and partner teams to align priorities, improve co-sell execution, and strengthen SHI's market credibility.
- Capture customer evidence, references, and measurable outcomes that support retention, expansion, and market recognition.
Executive and Cross-Functional Communication:
- Serve as an executive advisor to enterprise clients, connecting business priorities to Microsoft cloud, data, AI, agent, security, and governance strategies.
- Communicate practice priorities, portfolio health, performance, risks, and investment needs to senior leadership
for prose. No markdown fences. No html/body tags. Need to include sections only when posting has real specific content. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate etc. We need to parse the job posting content. We have sections: About Us (company description) – but we should not repeat job title as heading. The page already shows it. Should we include About Us? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So they suggest typical headings. But we can also include other headings if they have content? The instruction says: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can include sections like About Us if it's substantive. However they gave examples of headings; but we can use any heading as long as it's appropriate. Probably we should follow typical sections: About the role (Job Summary), Responsibilities (Role Description broken into subparts), Requirements (Skill Level Requirements, Other Requirements), Qualifications maybe same as Requirements, Skills maybe part of Requirements, Benefits, Pay, Schedule.
We need to decide what to include.
Let's extract content:
- About Us: description of SHI International Corp. This is substantive. Should we include as a section? Possibly "About the company" but not in list. Could use About SHI
. But they didn't list that as example but it's okay. However they said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests they expect those headings. But they didn't forbid other headings. Safer to stick to those headings. So we can map content to those headings.
- Job Summary: we can put under About the role
(or maybe "Job Summary").
- Responsibilities: The Role Description includes many bullet-like paragraphs. We can extract responsibilities as list items.
- Requirements: Skill Level Requirements and Other Requirements.
- Qualifications: maybe same as Requirements; but we could combine.
- Skills: maybe part of Requirements.
- Benefits: The posting mentions "Health, wellness, and financial benefits to offer peace of mind to you and your family." Also "World-class facilities and the technology you need to thrive – in our offices or yours." Also "Continuous professional growth and leadership opportunities." Also "If You Join Our Team, You’ll Enjoy Our commitment to diversity, as the largest minority- and woman-owned enterprise in the U.S." That's benefits. So we can include Benefits section.
- Pay: The posting includes "The estimated annual pay range for this position is $225,000 - $325,000 which includes a base salary and bonus." Also "The compensation for this position is dependent on job-related kn" (cut off). We have pay range. So we can include Pay.
- Schedule: Not mentioned explicitly. There's remote position with home office setup based in certain cities. No schedule like full-time, part-time. Not given. So we should not include Schedule section.
We must not include placeholder like "commensurate with experience". We have actual pay range.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include details from About Us, Job Summary, Responsibilities (the role description paragraphs), Requirements (skill level, other requirements), Benefits, Pay.
We must not repeat job title as heading. Not include Job ID etc.
We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting didn't have those obviously.
We need to output only HTML fragment.
Let's structure:
About SHI
maybe but they said About the role. However About Us is not about the role. Could we put About Us under About the role? Might be confusing. Perhaps we should include a section "About the company" but not in examples. The instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but they gave examples. Safer to stick to those examples. So we could treat About Us as part of "About the role"? Not ideal. Maybe we can omit About Us because it's not strictly about the role, but it's substantive. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must include About Us info somewhere. If we don't have a heading for it, we could put it in a
About the role
(or maybe "Job Summary"). - Responsibilities: The Role Description includes many bullet-like paragraphs. We can extract responsibilities as list items. - Requirements: Skill Level Requirements and Other Requirements. - Qualifications: maybe same as Requirements; but we could combine. - Skills: maybe part of Requirements. - Benefits: The posting mentions "Health, wellness, and financial benefits to offer peace of mind to you and your family." Also "World-class facilities and the technology you need to thrive – in our offices or yours." Also "Continuous professional growth and leadership opportunities." Also "If You Join Our Team, You’ll Enjoy Our commitment to diversity, as the largest minority- and woman-owned enterprise in the U.S." That's benefits. So we can include Benefits section. - Pay: The posting includes "The estimated annual pay range for this position is $225,000 - $325,000 which includes a base salary and bonus." Also "The compensation for this position is dependent on job-related kn" (cut off). We have pay range. So we can include Pay. - Schedule: Not mentioned explicitly. There's remote position with home office setup based in certain cities. No schedule like full-time, part-time. Not given. So we should not include Schedule section. We must not include placeholder like "commensurate with experience". We have actual pay range. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include details from About Us, Job Summary, Responsibilities (the role description paragraphs), Requirements (skill level, other requirements), Benefits, Pay. We must not repeat job title as heading. Not include Job ID etc. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting didn't have those obviously. We need to output only HTML fragment. Let's structure:About SHI
maybe but they said About the role. However About Us is not about the role. Could we put About Us under About the role? Might be confusing. Perhaps we should include a section "About the company" but not in examples. The instruction says "usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but they gave examples. Safer to stick to those examples. So we could treat About Us as part of "About the role"? Not ideal. Maybe we can omit About Us because it's not strictly about the role, but it's substantive. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must include About Us info somewhere. If we don't have a heading for it, we could put it in a
without heading? But they said use
for section headings (e.g. About the role, Responsibilities...). It doesn't say every paragraph must be under a heading; we could have a
at top without heading? Probably they expect sections with headings. But we could include a heading like "About SHI" even if not in examples; it's still a section heading. The instruction didn't forbid other headings; it just gave examples. So I think it's okay. Thus we will include:
About SHI
Since 1989, SHI International Corp. has helped organizations change the world through technology. We’ve grown every year since, and today we’re proud to be a $16 billion global provider of IT solutions and services. Over 17,000 Organizations Worldwide Rely On SHI’s Concierge Approach To Help Them Solve What’s Next. But The Heartbeat Of SHI Is Our Employees – All 7,000 Of Them. If You Join Our Team, You’ll Enjoy Our commitment to diversity, as the largest minority- and woman-owned enterprise in the U.S. Continuous professional growth and leadership opportunities. Health, wellness, and financial benefits to offer peace of mind to you and your family. World-class facilities and the technology you need to thrive – in our offices or yours.
Note: The text includes some capitalization weirdness; we preserve as is. Next,About the role
with Job Summary. Job Summary paragraph: "The Senior Director, Data & AI leads SHI's AI + Infrastructure organization within the Microsoft Services Practice. This leader brings together Agentic Solutions, Cloud Platform, Data & Intelligence, and AI Security & Governance to build and deliver connected Microsoft solutions across Azure, Microsoft Fabric, Microsoft Foundry, agents, data platforms, and the security and governance capabilities required to operate them responsibly. The Senior Director runs the organization as a business, with ownership of service maturity, solution development, headcount planning, utilization, delivery quality, capacity, pipeline support, and measurable client outcomes. This role leads managers and practice leaders responsible for Agentic Solutions, Cloud Platform, Data & Intelligence, and AI Security & Governance and remains accountable for their effectiveness, development, and delivery performance. Aligned to Microsoft's Fabric IQ and Foundry IQ investments, this role connects cloud foundation, business data, enterprise knowledge, agentic experiences, and trust. The Senior Director helps SHI move clients from isolated pilots to secure, governed, production-ready platforms and solutions while creating repeatable paths for growth. This role sits at the center of SHI's Microsoft Services growth plan, turning Fabric IQ and Foundry IQ alignment into a working operating model that builds stronger solutions, improves delivery execution, develops talent, and creates repeatable paths for growth. This is a remote position with a Home Office setup based in New York City, Charlotte, Chicago, Atlanta, Austin, Denver, Los Angeles, San Francisco, or Seattle." We'll put that in. Next,
Responsibilities
. We need to extract responsibilities from Role Description. The Role Description includes several subheadings: Strategic Leadership and Practice Development, People Leadership Through Managers and Directors, Technical Direction Across Data, AI, and Security, Delivery Excellence and Client Outcomes, Business Growth and Market Development, Executive and Cross-Functional Communication. Each has multiple sentences. We can turn each sentence or clause into list items. Must preserve all substantive info; we should not lose detail. We'll create- with
- for each distinct responsibility. Let's parse: Strategic Leadership and Practice Development: - Set and execute a unified direction for AI + Infrastructure, connecting Agentic Solutions, Cloud Platform, Data & Intelligence, and AI Security & Governance through one operating model. - Translate Microsoft's Fabric IQ, Foundry IQ, Azure, and agent investments into a clear SHI services roadmap, capability plan, and investment agenda. - Establish clear ownership, decision rights, handoffs, delivery standards, and quality expectations across the organization. - Build modular, repeatable offerings that combine cloud, data, AI, and governance capabilities around defined customer outcomes. - Use portfolio, pipeline, delivery, and capacity data to prioritize investments, manage tradeoffs, and improve practice health. People Leadership Through Managers and Directors: - Lead, coach, and develop the leaders responsible for Agentic Solutions, Cloud Platform, Data & Intelligence, and AI Security & Governance. - Set measurable expectations for customer experience, delivery quality, utilization, capability development, financial performance, and team health. - Build leadership depth through regular one-on-ones, development planning, succession planning, and clear career paths. - Own workforce planning across the organization, including hiring, onboarding, retention, skills development, and capacity alignment to backlog and pipeline. - Create a culture of shared accountability in which teams solve for the full customer outcome rather than optimize isolated technology workstreams. Technical Direction Across Data, AI, and Security: - Maintain a platform-aware perspective across Agent 365, Copilot Studio, Microsoft Foundry, Model Context Protocol, Azure, landing zones, platform engineering, FinOps, Microsoft Fabric, OneLake, data engineering, data visualization, and data readiness. - Embed Entra Agent ID, Microsoft Purview, Defender for Cloud and AI, Security Copilot, Microsoft Sentinel, and Defender XDR into AI and platform solutions where those capabilities strengthen identity, data protection, observability, governance, and threat protection. - Sponsor reusable reference architectures, delivery frameworks, statements of work, work breakdown structures, templates, and accelerators. - Rely on practice leaders and principal architects for deep technical direction while maintaining alignment across disciplines. - Create a practical path from assessment and platform readiness through implementation, adoption, optimization, and transition to managed services. Delivery Excellence and Client Outcomes: - Provide executive oversight for complex, multi-workstream engagements that span cloud, data, AI, agents, security, and governance. - Hold leaders accountable for scope quality, staffing readiness, delivery methodology, risk management, timelines, budgets, and customer communication. - Review project health, utilization, realization, margin, capacity, and quality signals and act early when performance moves off plan. - Protect customer trust by ensuring teams make supportable commitments, apply appropriate governance, and transition solutions into sustainable operations. - Serve as an executive sponsor and trusted advisor for strategic clients, connecting platform decisions to measurable business outcomes. Business Growth and Market Development: - Grow AI + Infrastructure services revenue by improving solution relevance, supporting strategic pursuits, expanding enterprise client relationships, and developing repeatable offers. - Partner with Solution Architecture, Sales, Project Management, Digital Workplace, and Managed Services to shape opportunities and deliver connected customer outcomes. - Manage utilization, capacity, backlog, pipeline health, and delivery performance to improve profitability and support sustainable growth. - Build strong relationships with Microsoft field, engineering, and partner teams to align priorities, improve co-sell execution, and strengthen SHI's market credibility. - Capture customer evidence, references, and measurable outcomes that support retention, expansion, and market recognition. Executive and Cross-Functional Communication: - Serve as an executive advisor to enterprise clients, connecting business priorities to Microsoft cloud, data, AI, agent, security, and governance strategies. - Communicate practice priorities, portfolio health, performance, risks, and investment needs to senior leadership