Director Enterprise Architecture
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. No Job ID.
We must preserve all substantive information; do not invent or summarize away detail. Remove boilerplate, duplicated lines, application instructions.
We need to decide which sections to include: About the role (maybe combine company description and role summary). Responsibilities (key responsibilities + expected time allocation). Requirements (maybe qualifications required). Qualifications (maybe preferred?). Skills (maybe list of technical skills). Benefits, Pay, Schedule only if present: none present, so omit those sections.
We need to ensure we don't create empty sections.
Let's extract substantive content:
Company description: "HatchWorks AI is an enterprise AI consulting firm. We design, build, and operate production-grade AI and software systems for clients across regulated and high-growth industries. Our teams pair senior architects and engineers with AI-assisted delivery methods to move clients from discovery to execution faster, without sacrificing rigor."
Role summary: "The Director, Enterprise Architecture is a senior leadership role that sits at the intersection of client delivery, pre-sales engineering, and practice building at Hatchworks. This role carries both strategic and hands-on responsibility: leading architecture on high-value client engagements, serving as the technical voice in the sales cycle, and shaping the Enterprise Architecture practice from the ground up. The ideal candidate is a seasoned architect who can operate fluidly across the full engagement lifecycle — from scoping and estimating work alongside sellers, to architecting solutions, to enabling delivery teams for success. This role will lead the Hatchworks' Enterprise Architecture & DevOps circle, managing a team of architects and driving the standards, patterns, and mentorship that define how we deliver."
Key Responsibilities: bullet list with subpoints.
We need to format as
- each bullet. The bullet points have sub-bullets? Actually they have numbered sections with subpoints. We'll treat each numbered item as a top-level li, and subpoints as nested ul? The instruction: Use
- for any list of duties/requirements/benefits. It doesn't forbid nested lists. We'll do nested.
Responsibilities:
1. Client DeliveryTarget: up to 75% of billable time; emphasis on Strategy engagements over Build where possible. Serve as lead architect on client engagements, including both Strategy projects (AI roadmaps, architecture assessments, modernization strategies) and Build projects (implementation, migration, platform engineering).Prioritize high-leverage contribution — enabling and delegating to project teams rather than operating solely as an individual contributor.Manage the architecture workstream within client Projects, with a path toward owning entire client Programs as the practice matures.Provide hands-on technical leadership in areas such as cloud infrastructure (Azure, GCP), data architecture, DevOps, security, and AI/ML integration.
2. Pre-Sales EngineeringTarget: ~25% block (approximately 10 hours/week) dedicated to Sales Engineering. Act as the Pre-Sales Engineer in a triad with a Pre-Sales Strategist and a Seller, providing technical depth to the sales process.Participate in and facilitate discovery workshops.Lead solution architecture, technical scoping, and estimation for prospective client engagements.Own the technical narrative in proposals and presentations, ensuring that what we sell is what we can deliver.Drive a clean Sales-to-Delivery handoff by documenting architectural decisions, assumptions, risks, and context for the Delivery teams that will execute.Support staffing on projects he helps sign, ensuring continuity from sale through early delivery.
3. Practice Leadership & MentorshipTarget: 4–5 hours/week for mentorship and ad-hoc project support. Serve as the leader of the Enterprise Architecture practice (circle/tribe) at Hatchworks, defining its standards, toolkits, and career paths.Mentor junior and mid-level architects, developing them into the next generation of Enterprise Architects.Provide impromptu architectural guidance and support across other active projects as a senior technical resource.Contribute to internal initiatives that raise the bar on delivery quality, reusable frameworks, and architectural governance.
EXPECTED TIME & BILLING ALLOCATION: This role operates on a blended billing model. The approximate weekly breakdown is: Client Engagements — ~30 hrs/wk · ~75% of time · Client-billablePre-Sales Engineering — ~10 hrs/wk · ~25% of time · Sales Engineering blockMentorship & Support — ~5 hrs/wk · ~12.5% of time · Internal Client billing should be high-value: enabling teams, leading architecture, and delegating effectively — not just heads-down IC work.
We could incorporate this into Responsibilities or a separate section like "Time Allocation". But instruction: include a section ONLY when posting has real, specific content for it. This is specific content about time allocation. Could be part of Responsibilities or a separate section like "Expected Time & Billing Allocation". Since we have a heading for Responsibilities, we could embed the time allocation within Responsibilities as a paragraph after the list. But better to keep as part of Responsibilities? The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So we can have a
for the time allocation prose.
Qualifications: Required and Preferred.
Required list:
- 15+ years of progressive experience in software engineering, with at least 5 years in enterprise or principal architect roles.
- Demonstrated experience in a consulting or professional services environment, with direct client-facing delivery responsibilities.
- Deep technical expertise in cloud platforms (Azure and/or GCP), with hands-on experience in infrastructure, data, DevOps, and security.
- Proven ability to lead pre-sales activities: discovery, solution design, scoping, and estimation.
- Track record of leading and mentoring engineering teams (10+ engineers).
- Strong communication skills with the ability to translate complex technical concepts for executive and non-technical audiences.
- Experience with architecture governance, standards definition, and cross-project technical oversight.
Preferred list:
- Experience with AI/ML strategy, roadmapping, or implementation in enterprise environments.
- Background in cloud migration and application modernization at scale (50+ application portfolios).
- Familiarity with Kubernetes, microservices architecture, and event-driven systems.
- Prior experience building or leading an architecture practice or center of excellence.
- History of closing or directly contributing to new business ($1M+ engagements).
Growth Trajectory: This role is designed to scale with Hatchworks. Immediately, this Director will operate as the senior-most architect on engagements, a key voice in pre-sales, and the lead of the Enterprise Architecture & DevOps hub – owning the hiring, development, and deployment of a team of architects, and driving the standards that govern how Hatchworks delivers technical excellence.The progression from supporting individual client Projects to managing entire client Programs is a key milestone for this role, and one that Hatchworks is actively building toward.
We could put this under a section like "Growth Trajectory" but not in the prescribed headings list. The headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Growth Trajectory not in list; maybe we can incorporate into About the role or Responsibilities? Probably better to put under About the role as additional description. Or we could create a section "About the role" that includes company description, role summary, growth trajectory. That seems okay.
Skills: Not explicitly listed but we could extract technical skills from qualifications: cloud platforms (Azure, GCP), infrastructure, data, DevOps, security, AI/ML, Kubernetes, microservices, event-driven, architecture governance, etc. But we should not invent; we can create a Skills section only if posting has real, specific content for it. The posting does not have a separate "Skills" heading, but we could infer from qualifications. However instruction: "Prefer a few substantive sections over many thin ones." Might be okay to not include Skills if not explicit. But we could include Skills as a
- list derived from qualifications, but that might be considered summarizing? It's extracting specifics, not inventing. It's okay to list skills mentioned. However we already have Qualifications (Required and Preferred). Skills could be redundant. Probably better to not add Skills unless explicitly mentioned. The posting does not have a separate Skills section, so we omit.
Benefits, Pay, Schedule: none present, omit.
Thus sections: About the role (company description + role summary + growth trajectory), Responsibilities (including time allocation), Qualifications (Required and Preferred). Possibly also Requirements? The posting has "QUALIFICATIONS" with Required and Preferred. There's no separate "Requirements". So we can map Qualifications to that heading. Or we could have Requirements as required qualifications and Qualifications as preferred? But the instruction says use headings like Requirements, Qualifications, Skills, etc. We have both Required and Preferred; we could put Required under Requirements and Preferred under Qualifications. Or we could combine both under Qualifications. To follow instruction, we can have Requirements (Required) and Qualifications (Preferred). Let's do that.
Thus:
About the role
Company description...
Role summary...
Growth trajectory...
Responsibilities
- Client Delivery... (including subpoints maybe as nested ul)
...
...
Expected time & billing allocation...
(maybe as a paragraph after list)
Requirements
- Required items...
Qualifications
- Preferred items...
About the role
for prose. We must not repeat job title as heading. No Job ID. We must preserve all substantive information; do not invent or summarize away detail. Remove boilerplate, duplicated lines, application instructions. We need to decide which sections to include: About the role (maybe combine company description and role summary). Responsibilities (key responsibilities + expected time allocation). Requirements (maybe qualifications required). Qualifications (maybe preferred?). Skills (maybe list of technical skills). Benefits, Pay, Schedule only if present: none present, so omit those sections. We need to ensure we don't create empty sections. Let's extract substantive content: Company description: "HatchWorks AI is an enterprise AI consulting firm. We design, build, and operate production-grade AI and software systems for clients across regulated and high-growth industries. Our teams pair senior architects and engineers with AI-assisted delivery methods to move clients from discovery to execution faster, without sacrificing rigor." Role summary: "The Director, Enterprise Architecture is a senior leadership role that sits at the intersection of client delivery, pre-sales engineering, and practice building at Hatchworks. This role carries both strategic and hands-on responsibility: leading architecture on high-value client engagements, serving as the technical voice in the sales cycle, and shaping the Enterprise Architecture practice from the ground up. The ideal candidate is a seasoned architect who can operate fluidly across the full engagement lifecycle — from scoping and estimating work alongside sellers, to architecting solutions, to enabling delivery teams for success. This role will lead the Hatchworks' Enterprise Architecture & DevOps circle, managing a team of architects and driving the standards, patterns, and mentorship that define how we deliver." Key Responsibilities: bullet list with subpoints. We need to format as
- each bullet. The bullet points have sub-bullets? Actually they have numbered sections with subpoints. We'll treat each numbered item as a top-level li, and subpoints as nested ul? The instruction: Use
- for any list of duties/requirements/benefits. It doesn't forbid nested lists. We'll do nested.
Responsibilities:
1. Client DeliveryTarget: up to 75% of billable time; emphasis on Strategy engagements over Build where possible. Serve as lead architect on client engagements, including both Strategy projects (AI roadmaps, architecture assessments, modernization strategies) and Build projects (implementation, migration, platform engineering).Prioritize high-leverage contribution — enabling and delegating to project teams rather than operating solely as an individual contributor.Manage the architecture workstream within client Projects, with a path toward owning entire client Programs as the practice matures.Provide hands-on technical leadership in areas such as cloud infrastructure (Azure, GCP), data architecture, DevOps, security, and AI/ML integration.
2. Pre-Sales EngineeringTarget: ~25% block (approximately 10 hours/week) dedicated to Sales Engineering. Act as the Pre-Sales Engineer in a triad with a Pre-Sales Strategist and a Seller, providing technical depth to the sales process.Participate in and facilitate discovery workshops.Lead solution architecture, technical scoping, and estimation for prospective client engagements.Own the technical narrative in proposals and presentations, ensuring that what we sell is what we can deliver.Drive a clean Sales-to-Delivery handoff by documenting architectural decisions, assumptions, risks, and context for the Delivery teams that will execute.Support staffing on projects he helps sign, ensuring continuity from sale through early delivery.
3. Practice Leadership & MentorshipTarget: 4–5 hours/week for mentorship and ad-hoc project support. Serve as the leader of the Enterprise Architecture practice (circle/tribe) at Hatchworks, defining its standards, toolkits, and career paths.Mentor junior and mid-level architects, developing them into the next generation of Enterprise Architects.Provide impromptu architectural guidance and support across other active projects as a senior technical resource.Contribute to internal initiatives that raise the bar on delivery quality, reusable frameworks, and architectural governance.
EXPECTED TIME & BILLING ALLOCATION: This role operates on a blended billing model. The approximate weekly breakdown is: Client Engagements — ~30 hrs/wk · ~75% of time · Client-billablePre-Sales Engineering — ~10 hrs/wk · ~25% of time · Sales Engineering blockMentorship & Support — ~5 hrs/wk · ~12.5% of time · Internal Client billing should be high-value: enabling teams, leading architecture, and delegating effectively — not just heads-down IC work.
We could incorporate this into Responsibilities or a separate section like "Time Allocation". But instruction: include a section ONLY when posting has real, specific content for it. This is specific content about time allocation. Could be part of Responsibilities or a separate section like "Expected Time & Billing Allocation". Since we have a heading for Responsibilities, we could embed the time allocation within Responsibilities as a paragraph after the list. But better to keep as part of Responsibilities? The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So we can have a
for the time allocation prose. Qualifications: Required and Preferred. Required list: - 15+ years of progressive experience in software engineering, with at least 5 years in enterprise or principal architect roles. - Demonstrated experience in a consulting or professional services environment, with direct client-facing delivery responsibilities. - Deep technical expertise in cloud platforms (Azure and/or GCP), with hands-on experience in infrastructure, data, DevOps, and security. - Proven ability to lead pre-sales activities: discovery, solution design, scoping, and estimation. - Track record of leading and mentoring engineering teams (10+ engineers). - Strong communication skills with the ability to translate complex technical concepts for executive and non-technical audiences. - Experience with architecture governance, standards definition, and cross-project technical oversight. Preferred list: - Experience with AI/ML strategy, roadmapping, or implementation in enterprise environments. - Background in cloud migration and application modernization at scale (50+ application portfolios). - Familiarity with Kubernetes, microservices architecture, and event-driven systems. - Prior experience building or leading an architecture practice or center of excellence. - History of closing or directly contributing to new business ($1M+ engagements). Growth Trajectory: This role is designed to scale with Hatchworks. Immediately, this Director will operate as the senior-most architect on engagements, a key voice in pre-sales, and the lead of the Enterprise Architecture & DevOps hub – owning the hiring, development, and deployment of a team of architects, and driving the standards that govern how Hatchworks delivers technical excellence.The progression from supporting individual client Projects to managing entire client Programs is a key milestone for this role, and one that Hatchworks is actively building toward. We could put this under a section like "Growth Trajectory" but not in the prescribed headings list. The headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Growth Trajectory not in list; maybe we can incorporate into About the role or Responsibilities? Probably better to put under About the role as additional description. Or we could create a section "About the role" that includes company description, role summary, growth trajectory. That seems okay. Skills: Not explicitly listed but we could extract technical skills from qualifications: cloud platforms (Azure, GCP), infrastructure, data, DevOps, security, AI/ML, Kubernetes, microservices, event-driven, architecture governance, etc. But we should not invent; we can create a Skills section only if posting has real, specific content for it. The posting does not have a separate "Skills" heading, but we could infer from qualifications. However instruction: "Prefer a few substantive sections over many thin ones." Might be okay to not include Skills if not explicit. But we could include Skills as a
- list derived from qualifications, but that might be considered summarizing? It's extracting specifics, not inventing. It's okay to list skills mentioned. However we already have Qualifications (Required and Preferred). Skills could be redundant. Probably better to not add Skills unless explicitly mentioned. The posting does not have a separate Skills section, so we omit.
Benefits, Pay, Schedule: none present, omit.
Thus sections: About the role (company description + role summary + growth trajectory), Responsibilities (including time allocation), Qualifications (Required and Preferred). Possibly also Requirements? The posting has "QUALIFICATIONS" with Required and Preferred. There's no separate "Requirements". So we can map Qualifications to that heading. Or we could have Requirements as required qualifications and Qualifications as preferred? But the instruction says use headings like Requirements, Qualifications, Skills, etc. We have both Required and Preferred; we could put Required under Requirements and Preferred under Qualifications. Or we could combine both under Qualifications. To follow instruction, we can have Requirements (Required) and Qualifications (Preferred). Let's do that.
Thus:
About the role
Company description...
Role summary...
Growth trajectory...
Responsibilities
- Client Delivery... (including subpoints maybe as nested ul) ... ...
Expected time & billing allocation...
(maybe as a paragraph after list)Requirements
- Required items...
Qualifications
- Preferred items... About the role
- list derived from qualifications, but that might be considered summarizing? It's extracting specifics, not inventing. It's okay to list skills mentioned. However we already have Qualifications (Required and Preferred). Skills could be redundant. Probably better to not add Skills unless explicitly mentioned. The posting does not have a separate Skills section, so we omit.
Benefits, Pay, Schedule: none present, omit.
Thus sections: About the role (company description + role summary + growth trajectory), Responsibilities (including time allocation), Qualifications (Required and Preferred). Possibly also Requirements? The posting has "QUALIFICATIONS" with Required and Preferred. There's no separate "Requirements". So we can map Qualifications to that heading. Or we could have Requirements as required qualifications and Qualifications as preferred? But the instruction says use headings like Requirements, Qualifications, Skills, etc. We have both Required and Preferred; we could put Required under Requirements and Preferred under Qualifications. Or we could combine both under Qualifications. To follow instruction, we can have Requirements (Required) and Qualifications (Preferred). Let's do that.
Thus:
- for any list of duties/requirements/benefits, and
- for any list of duties/requirements/benefits. It doesn't forbid nested lists. We'll do nested.
Responsibilities:
1. Client DeliveryTarget: up to 75% of billable time; emphasis on Strategy engagements over Build where possible. Serve as lead architect on client engagements, including both Strategy projects (AI roadmaps, architecture assessments, modernization strategies) and Build projects (implementation, migration, platform engineering).Prioritize high-leverage contribution — enabling and delegating to project teams rather than operating solely as an individual contributor.Manage the architecture workstream within client Projects, with a path toward owning entire client Programs as the practice matures.Provide hands-on technical leadership in areas such as cloud infrastructure (Azure, GCP), data architecture, DevOps, security, and AI/ML integration.
2. Pre-Sales EngineeringTarget: ~25% block (approximately 10 hours/week) dedicated to Sales Engineering. Act as the Pre-Sales Engineer in a triad with a Pre-Sales Strategist and a Seller, providing technical depth to the sales process.Participate in and facilitate discovery workshops.Lead solution architecture, technical scoping, and estimation for prospective client engagements.Own the technical narrative in proposals and presentations, ensuring that what we sell is what we can deliver.Drive a clean Sales-to-Delivery handoff by documenting architectural decisions, assumptions, risks, and context for the Delivery teams that will execute.Support staffing on projects he helps sign, ensuring continuity from sale through early delivery.
3. Practice Leadership & MentorshipTarget: 4–5 hours/week for mentorship and ad-hoc project support. Serve as the leader of the Enterprise Architecture practice (circle/tribe) at Hatchworks, defining its standards, toolkits, and career paths.Mentor junior and mid-level architects, developing them into the next generation of Enterprise Architects.Provide impromptu architectural guidance and support across other active projects as a senior technical resource.Contribute to internal initiatives that raise the bar on delivery quality, reusable frameworks, and architectural governance.
EXPECTED TIME & BILLING ALLOCATION: This role operates on a blended billing model. The approximate weekly breakdown is: Client Engagements — ~30 hrs/wk · ~75% of time · Client-billablePre-Sales Engineering — ~10 hrs/wk · ~25% of time · Sales Engineering blockMentorship & Support — ~5 hrs/wk · ~12.5% of time · Internal Client billing should be high-value: enabling teams, leading architecture, and delegating effectively — not just heads-down IC work.
We could incorporate this into Responsibilities or a separate section like "Time Allocation". But instruction: include a section ONLY when posting has real, specific content for it. This is specific content about time allocation. Could be part of Responsibilities or a separate section like "Expected Time & Billing Allocation". Since we have a heading for Responsibilities, we could embed the time allocation within Responsibilities as a paragraph after the list. But better to keep as part of Responsibilities? The instruction: Use
HatchWorks AI is an enterprise AI consulting firm. We design, build, and operate production-grade AI and software systems for clients across regulated and high-growth industries. Our teams pair senior architects and engineers with AI-assisted delivery methods to move clients from discovery to execution faster, without sacrificing rigor.
The Director, Enterprise Architecture is a senior leadership role that sits at the intersection of client delivery, pre-sales engineering, and practice building at Hatchworks. This role carries both strategic and hands-on responsibility: leading architecture on high-value client engagements, serving as the technical voice in the sales cycle, and shaping the Enterprise Architecture practice from the ground up. The ideal candidate is a seasoned architect who can operate fluidly across the full engagement lifecycle — from scoping and estimating work alongside sellers, to architecting solutions, to enabling delivery teams for success. This role will lead the Hatchworks' Enterprise Architecture & DevOps circle, managing a team of architects and driving the standards, patterns, and mentorship that define how we deliver.
This role is designed to scale with Hatchworks. Immediately, this Director will operate as the senior-most architect on engagements, a key voice in pre-sales, and the lead of the Enterprise Architecture & DevOps hub – owning the hiring, development, and deployment of a team of architects, and driving the standards that govern how Hatchworks delivers technical excellence. The progression from supporting individual client Projects to managing entire client Programs is a key milestone for this role, and one that Hatchworks is actively building toward.
Responsibilities
- Client Delivery