Technical Director
Bounteous · United States · 1 mo ago
RemoteRemoteInformation TechnologyFull-time
We need to output HTML fragment with sections: About the role? The posting includes "Job Description Role Summary". We need to use for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real, specific content. No filler. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, etc. Also remove application instructions, subscription invites, etc.
We need to preserve all substantive information. Let's parse content.
Company description: "Bounteous is a global AI Services firm..." That's about the company, could be "About the role"? Actually "About the role" is typical heading for role summary. We'll put role summary under
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real, specific content. No filler. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, etc. Also remove application instructions, subscription invites, etc.
We need to preserve all substantive information. Let's parse content.
Company description: "Bounteous is a global AI Services firm..." That's about the company, could be "About the role"? Actually "About the role" is typical heading for role summary. We'll put role summary under About the role
with paragraph(s) containing role summary.
Then "Key Responsibilities": list bullet points. We'll put Responsibilities
with - each.
Then "Required Qualifications": list bullet points. We'll put
Requirements
(or Qualifications). The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have both Required Qualifications and Preferred Qualifications. Could combine into Requirements (required) and maybe Skills? But we have Preferred Qualifications separate. Could treat Required Qualifications as Requirements, Preferred Qualifications as Qualifications? Or we could have Requirements and Qualifications sections. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have both Requirements and Qualifications sections. We'll put Required Qualifications under Requirements, Preferred Qualifications under Qualifications.
Then "Information Security Responsibilities": that's a set of bullet points. Could be part of Responsibilities or maybe Skills? It's specific responsibilities. Could be included under Responsibilities as additional bullets. But we already have Responsibilities section; we can add those bullets there. However they are separate heading "Information Security Responsibilities". We could treat as part of Responsibilities (makes sense). We'll incorporate them into Responsibilities list.
We must not include boilerplate like EEO, visa sponsorship, AI tools, etc. Also remove subscription invitation line. Also remove "We invite you to stay connected..." etc. Also remove "#BI-Remote". Also remove lines about AI tools in hiring process. Also remove "Bounteous is proud to be an equal opportunity employer..." etc. Also remove "Bounteous does not discriminate..." etc. Also remove "Bounteous is willing to sponsor eligible candidates for employment visas." Also remove "We may use artificial intelligence (AI) tools..." etc.
Also remove "Job Description Role Summary" maybe we just use content.
Now we need to ensure we preserve all substantive information: company description, role summary, responsibilities list, required qualifications, preferred qualifications, information security responsibilities.
We must not invent or summarize away detail. Keep exact phrasing? We should preserve substance but can rephrase slightly? Probably keep as is.
Let's extract role summary paragraph:
"Role Summary The Tech Delivery Leader is the senior-most executive on the ground for the account. This person carries dual accountability: they are the final authority representing the account to the client's leadership (CTO/VP-Technical equivalents), and they own end-to-end delivery execution — schedule, budget, quality, and margin — across every workstream. The Tech Delivery Lead runs the delivery organization day-to-day through the Technical Delivery Manager(s), Program/Project Manager(s), Architect(s), and Product Manager(s), translating technical trust and stakeholder alignment into shipped, credible work."
We'll put that as paragraph(s) under About the role.
Now responsibilities list: Let's extract each bullet from "Key Responsibilities". They are sentences starting with verbs.
List:
- Maintain on-site presence with the client's integration teams and build rapport at the client's leadership level.
- Represent the account to the client's CTO/VP-Technical equivalents, acting as the final word on credibility and positioning.
- Validate that solution direction is credible before it reaches the client; hold authority to redirect solution approach before client presentation.
- Resolve technical escalations that require executive-level authority, partnering with the Principal Architect(s) as needed.
- Own end-to-end delivery execution for the account: schedule, budget, staffing, quality, and margin across all workstreams.
- Run the delivery organization day-to-day via Technical Delivery Leaders, Project Manager(s), Architect(s), and Product Manager(s), setting direction and removing blockers.
- Stay accountable for the account's core delivery KPIs: on-time/on-budget delivery, quality, and team utilization.
- Approve or reject resourcing and staffing changes; hold authority to re-plan scope or timeline within account guardrails.
- Champion the adoption of agentic/AI-assisted development practices across the delivery organization, ensuring the account's agent-orchestrated development model is executed responsibly and effectively.
- Conduct once a month on-site visits to the client to maintain visibility, strengthen relationships, and stay close to emerging needs across the account.
- Proactively mine the account for expansion opportunities — new workstreams, adjacent problems, or additional scope — surfacing them early rather than waiting for the client to ask.
- Assist the Client Partner in pursuing account-mining opportunities, providing the credibility and solutioning support needed to convert them into scoped work.
- Represent the account in growth, expansion, and renewal conversations with client leadership where credibility is the deciding factor.
- Mentor and provide executive-level backing to Technical Delivery Managers, Architects, Program/Project Managers, and Product Managers across the account.
Now Information Security Responsibilities bullets:
- Promote and enforce awareness of key information security practices, including acceptable use of information assets, malware protection, and password security protocols
- Identify, assess, and report security risks, focusing on how these risks impact the confidentiality, integrity, and availability of information assets
- Understand and evaluate how data is stored, processed, or transmitted, ensuring compliance with data privacy and protection standards (GDPR, CCPA, etc.)
- Ensure data protection measures are integrated throughout the information lifecycle to safeguard sensitive information
We can add these to Responsibilities list as well, maybe as separate sublist? But we can just append them to the same ul.
Now Required Qualifications bullets:
- 15+ years of experience in technology delivery, with substantial time in a senior leadership role (Sr Director or Director) at a consultancy, systems integrator, or enterprise technology organization.
- Proven track record owning end-to-end delivery execution — schedule, budget, quality, and margin — for large, multi-workstream client engagements.
- Demonstrated ability to build and sustain technical trust at the client's executive level (CTO/VP-Technical), including representing decisions directly to that audience.
- Experience serving as the final authority on an account's technical direction, including the judgment to redirect a solution approach before it reaches the client.
- Strong track record managing distributed onshore/offshore delivery organizations at scale.
- Comfortable holding dual accountability for both technical credibility and commercial/delivery outcomes simultaneously — this is not a purely technical or purely operational role.
- Experience mentoring and providing escalation support to Technical Delivery Managers, Architects, Program/Project Managers, and Product Managers.
- Demonstrated ability to work effectively with offshore delivery teams, coordinating across time zones, delivery locations, and reporting lines.
- Comfortable operating in a business-development-adjacent capacity — spotting account-mining opportunities during client conversations and partnering with the Client Partner to shape them into pursuits.
- Willingness and ability to travel to client sites frequently to maintain the on-the-ground presence this role requires.
Preferred Qualifications bullets:
- Prior title of Sr Director/Director/Technical Director or equivalent at a consulting or systems-integration firm.
- Experience in healthcare, or another regulated industry is good to have.
- Track record of driving account growth or expansion on the strength of demonstrated credibility.
- Experience operating within an agent-orchestrated or AI-augmented development delivery model.
Now we need to output HTML fragment only, no extra markup.
We'll structure:
About the role
... role summary ...
Responsibilities
- ... each bullet ...
...
Requirements
- ... required qualifications ...
...
Qualifications
- ... preferred qualifications ...
...
We should not include Benefits, Pay, Schedule sections because not present.
Check for any duplicated lines: we must not repeat. Ensure we didn't include any boilerplate.
Now ensure we preserve all substantive information: company description? The initial paragraph about Bounteous being a global AI Services firm etc. Should we include that? It's not under a heading but it's substantive info about the company. The instruction: "Preserve ALL substantive information". Should we include it? It could go under About the role maybe as a preamble. The role summary already includes some. The company description is separate. We could include a short paragraph under About the role before the role summary, or we could make a separate section like "About the company". But headings list only includes About the role, Responsibilities, etc. Not About the company. However we could incorporate it into About the role as part of the role summary? Might be okay to add a paragraph about the company before the role summary. The instruction says use for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but we should follow the examples. Probably we should include company description as part of About the role paragraph.
Thus About the role will have two paragraphs: first about Bounteous, second role summary.
Let's extract company description:
"Bounteous is a global AI Services firm where agentic engineering and human experience converge to deliver transformative business outcomes for the enterprise. We help organizations design, build, and scale AI-driven products, platforms, and processes. With more than 5,000 team members worldwide, Bounteous delivers AI that sticks, powering adoption and outcomes that move organizations from experimentation to true transformation. Bounteous is backed by New Mountain Capital, a New York-based growth-oriented investment firm that emphasizes business building."
We'll put that as a paragraph.
Now role summary paragraph as second paragraph.
Now ensure we didn't include any lines like "We invite you to stay connected..." etc.
Now output HTML.
Let's craft.
Check for any stray punctuation.
We'll produce:
About the role
Bounteous is a global AI Services firm where agentic engineering and human experience converge to deliver transformative business outcomes for the enterprise. We help organizations design, build, and scale AI-driven products, platforms, and processes. With more than 5,000 team members worldwide, Bounteous delivers AI that sticks, powering adoption and outcomes that move organizations from experimentation to true transformation. Bounteous is backed by New Mountain Capital, a New York-based growth-oriented investment firm that emphasizes business building.
The Tech Delivery Leader is the senior-most executive on the ground for the account. This person carries dual accountability: they are the final authority representing the account to the client's leadership (CTO/VP-Technical equivalents), and they own end-to-end delivery execution — schedule, budget, quality, and margin — across every workstream. The Tech Delivery Lead runs the delivery organization day-to-day through the Technical Delivery Manager(s), Program/Project Manager(s), Architect(s), and Product Manager(s), translating technical trust and stakeholder alignment into shipped, credible work.
Responsibilities
- Maintain on-site presence with the client's integration teams and build rapport at the client's leadership level.
- Represent the account to the client's CTO/VP-Technical equivalents, acting as the final word on credibility and positioning.
- Validate that solution direction is credible before it reaches the client; hold authority to redirect solution approach before client presentation.
- Resolve technical
Requirements
(or Qualifications). The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have both Required Qualifications and Preferred Qualifications. Could combine into Requirements (required) and maybe Skills? But we have Preferred Qualifications separate. Could treat Required Qualifications as Requirements, Preferred Qualifications as Qualifications? Or we could have Requirements and Qualifications sections. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have both Requirements and Qualifications sections. We'll put Required Qualifications under Requirements, Preferred Qualifications under Qualifications.
Then "Information Security Responsibilities": that's a set of bullet points. Could be part of Responsibilities or maybe Skills? It's specific responsibilities. Could be included under Responsibilities as additional bullets. But we already have Responsibilities section; we can add those bullets there. However they are separate heading "Information Security Responsibilities". We could treat as part of Responsibilities (makes sense). We'll incorporate them into Responsibilities list.
We must not include boilerplate like EEO, visa sponsorship, AI tools, etc. Also remove subscription invitation line. Also remove "We invite you to stay connected..." etc. Also remove "#BI-Remote". Also remove lines about AI tools in hiring process. Also remove "Bounteous is proud to be an equal opportunity employer..." etc. Also remove "Bounteous does not discriminate..." etc. Also remove "Bounteous is willing to sponsor eligible candidates for employment visas." Also remove "We may use artificial intelligence (AI) tools..." etc.
Also remove "Job Description Role Summary" maybe we just use content.
Now we need to ensure we preserve all substantive information: company description, role summary, responsibilities list, required qualifications, preferred qualifications, information security responsibilities.
We must not invent or summarize away detail. Keep exact phrasing? We should preserve substance but can rephrase slightly? Probably keep as is.
Let's extract role summary paragraph:
"Role Summary The Tech Delivery Leader is the senior-most executive on the ground for the account. This person carries dual accountability: they are the final authority representing the account to the client's leadership (CTO/VP-Technical equivalents), and they own end-to-end delivery execution — schedule, budget, quality, and margin — across every workstream. The Tech Delivery Lead runs the delivery organization day-to-day through the Technical Delivery Manager(s), Program/Project Manager(s), Architect(s), and Product Manager(s), translating technical trust and stakeholder alignment into shipped, credible work."
We'll put that as paragraph(s) under About the role.
Now responsibilities list: Let's extract each bullet from "Key Responsibilities". They are sentences starting with verbs.
List:
- Maintain on-site presence with the client's integration teams and build rapport at the client's leadership level.
- Represent the account to the client's CTO/VP-Technical equivalents, acting as the final word on credibility and positioning.
- Validate that solution direction is credible before it reaches the client; hold authority to redirect solution approach before client presentation.
- Resolve technical escalations that require executive-level authority, partnering with the Principal Architect(s) as needed.
- Own end-to-end delivery execution for the account: schedule, budget, staffing, quality, and margin across all workstreams.
- Run the delivery organization day-to-day via Technical Delivery Leaders, Project Manager(s), Architect(s), and Product Manager(s), setting direction and removing blockers.
- Stay accountable for the account's core delivery KPIs: on-time/on-budget delivery, quality, and team utilization.
- Approve or reject resourcing and staffing changes; hold authority to re-plan scope or timeline within account guardrails.
- Champion the adoption of agentic/AI-assisted development practices across the delivery organization, ensuring the account's agent-orchestrated development model is executed responsibly and effectively.
- Conduct once a month on-site visits to the client to maintain visibility, strengthen relationships, and stay close to emerging needs across the account.
- Proactively mine the account for expansion opportunities — new workstreams, adjacent problems, or additional scope — surfacing them early rather than waiting for the client to ask.
- Assist the Client Partner in pursuing account-mining opportunities, providing the credibility and solutioning support needed to convert them into scoped work.
- Represent the account in growth, expansion, and renewal conversations with client leadership where credibility is the deciding factor.
- Mentor and provide executive-level backing to Technical Delivery Managers, Architects, Program/Project Managers, and Product Managers across the account.
Now Information Security Responsibilities bullets:
- Promote and enforce awareness of key information security practices, including acceptable use of information assets, malware protection, and password security protocols
- Identify, assess, and report security risks, focusing on how these risks impact the confidentiality, integrity, and availability of information assets
- Understand and evaluate how data is stored, processed, or transmitted, ensuring compliance with data privacy and protection standards (GDPR, CCPA, etc.)
- Ensure data protection measures are integrated throughout the information lifecycle to safeguard sensitive information
We can add these to Responsibilities list as well, maybe as separate sublist? But we can just append them to the same ul.
Now Required Qualifications bullets:
- 15+ years of experience in technology delivery, with substantial time in a senior leadership role (Sr Director or Director) at a consultancy, systems integrator, or enterprise technology organization.
- Proven track record owning end-to-end delivery execution — schedule, budget, quality, and margin — for large, multi-workstream client engagements.
- Demonstrated ability to build and sustain technical trust at the client's executive level (CTO/VP-Technical), including representing decisions directly to that audience.
- Experience serving as the final authority on an account's technical direction, including the judgment to redirect a solution approach before it reaches the client.
- Strong track record managing distributed onshore/offshore delivery organizations at scale.
- Comfortable holding dual accountability for both technical credibility and commercial/delivery outcomes simultaneously — this is not a purely technical or purely operational role.
- Experience mentoring and providing escalation support to Technical Delivery Managers, Architects, Program/Project Managers, and Product Managers.
- Demonstrated ability to work effectively with offshore delivery teams, coordinating across time zones, delivery locations, and reporting lines.
- Comfortable operating in a business-development-adjacent capacity — spotting account-mining opportunities during client conversations and partnering with the Client Partner to shape them into pursuits.
- Willingness and ability to travel to client sites frequently to maintain the on-the-ground presence this role requires.
Preferred Qualifications bullets:
- Prior title of Sr Director/Director/Technical Director or equivalent at a consulting or systems-integration firm.
- Experience in healthcare, or another regulated industry is good to have.
- Track record of driving account growth or expansion on the strength of demonstrated credibility.
- Experience operating within an agent-orchestrated or AI-augmented development delivery model.
Now we need to output HTML fragment only, no extra markup.
We'll structure:
About the role
... role summary ...
Responsibilities
- ... each bullet ... ...
Requirements
- ... required qualifications ... ...
Qualifications
- ... preferred qualifications ... ...
for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but we should follow the examples. Probably we should include company description as part of About the role paragraph.
Thus About the role will have two paragraphs: first about Bounteous, second role summary.
Let's extract company description:
"Bounteous is a global AI Services firm where agentic engineering and human experience converge to deliver transformative business outcomes for the enterprise. We help organizations design, build, and scale AI-driven products, platforms, and processes. With more than 5,000 team members worldwide, Bounteous delivers AI that sticks, powering adoption and outcomes that move organizations from experimentation to true transformation. Bounteous is backed by New Mountain Capital, a New York-based growth-oriented investment firm that emphasizes business building."
We'll put that as a paragraph.
Now role summary paragraph as second paragraph.
Now ensure we didn't include any lines like "We invite you to stay connected..." etc.
Now output HTML.
Let's craft.
Check for any stray punctuation.
We'll produce:
About the role
Bounteous is a global AI Services firm where agentic engineering and human experience converge to deliver transformative business outcomes for the enterprise. We help organizations design, build, and scale AI-driven products, platforms, and processes. With more than 5,000 team members worldwide, Bounteous delivers AI that sticks, powering adoption and outcomes that move organizations from experimentation to true transformation. Bounteous is backed by New Mountain Capital, a New York-based growth-oriented investment firm that emphasizes business building.
The Tech Delivery Leader is the senior-most executive on the ground for the account. This person carries dual accountability: they are the final authority representing the account to the client's leadership (CTO/VP-Technical equivalents), and they own end-to-end delivery execution — schedule, budget, quality, and margin — across every workstream. The Tech Delivery Lead runs the delivery organization day-to-day through the Technical Delivery Manager(s), Program/Project Manager(s), Architect(s), and Product Manager(s), translating technical trust and stakeholder alignment into shipped, credible work.
Responsibilities
- Maintain on-site presence with the client's integration teams and build rapport at the client's leadership level.
- Represent the account to the client's CTO/VP-Technical equivalents, acting as the final word on credibility and positioning.
- Validate that solution direction is credible before it reaches the client; hold authority to redirect solution approach before client presentation.
- Resolve technical