(SR) Director Product Infrastructure Arch - REMOTE
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information, remove boilerplate (cookie/navigation/legal/EEO etc). There's none.
We need to include sections only when posting has real specific content. So we will have sections: About the Company (maybe combine Who We Are, What We Do, Our People Matter Most). Could be separate sections but we can combine to avoid thin sections. However the instruction: "Prefer a few substantive sections over many thin ones." So we can create sections like "About HHS Tech Group", "Role Overview", "Responsibilities", "Required Experience", "Preferred Experience", "Leadership Attributes", "What Success Looks Like", "Education and Certification", "Benefits". That's many but each substantive. Could combine some: maybe "About HHS Tech Group" includes Who We Are, What We Do, Our People Matter Most. "Role Overview" includes What You Will Do. Then Responsibilities, Required Experience, Preferred Experience, Leadership Attributes, What Success Looks Like, Education and Certification, Benefits.
We need to ensure we don't create empty sections.
Let's extract content.
Who We Are: "At HHS Tech Group (HTG), our work matters, and each of us makes a difference in the lives of people every day. HTG is a leader in the development and delivery of innovative, purpose-built modular software and technology solutions to clients in the commercial and government sectors."
What We Do: "HHS Tech Group creates innovative, purpose-built technology products and solutions, resulting in value and positive, quantifiable impact for our clients and the people they serve. Our people bring our software to life through collaborative relationships with our clients, working as a team, helping to solve complex problems that create positive personal and community impact for the people our clients serve. Each day, our software products and our people are making a difference."
Our People Matter Most: "Improving the lives of others and making an impact daily is no simple task. We are dedicated to our team’s professional and personal growth and well-being. Some key rewards and benefits include: Generously sponsored Medical Insurance Fully paid premiums on dental, vision, life and disability insurance. Generous 401k matching program Flexible PTO policy Join us!"
But note "Join us!" maybe part of benefits. We'll treat benefits separately.
Then "WHO WE ARE HIRING: (Senior) Director – Product Infrastructure Architecture (Cloud & SaaS Platforms) - Hybrid/Remote" - we don't repeat job title as heading, but we could include location/hybrid remote in a short p maybe.
Then "What You Will Do": paragraph about hands-on director.
Then Responsibilities: list of bullet points (multiple paragraphs each starting with bold headings). We need to convert each bullet into
- . The responsibilities section includes multiple sub-sections: Product Infrastructure Architecture (Hands-On), Cloud-Centric & Multi-Tenant SaaS Design, Data Virtualization & Platform Data Architecture, Modern DevOps & Platform Enablement, Modular, Open & Integration-Ready Platforms, Innovation & Out-of-the-Box Thinking, Architecture Leadership, Team Building & Knowledge Sharing, Governance, Security & Compliance. Each has a bold heading and then sentences. We'll treat each as a list item containing the heading and description.
We need to preserve all substantive info. So each
- will contain the heading (maybe as strong) and the description.
Then Required Experience: list of bullet points (each line). We'll make
- .
Preferred Experience: list.
Leadership Attributes: list.
What Success Looks Like: list of bullet points (maybe 4 items). We'll make
.
Education and Certification: paragraph(s). We'll make .
Benefits: list of benefits: Generously sponsored Medical Insurance, Fully paid premiums on dental, vision, life and disability insurance, Generous 401k matching program, Flexible PTO policy.
We also have location hybrid/remote maybe include in a short p under Role Overview.
We must not include Job ID/requisition numbers (none). No application instructions.
Now produce HTML fragment.
Let's craft.
Structure:
About HHS Tech Group
... combine Who We Are, What We Do, Our People Matter Most (excluding benefits line? We'll keep benefits separate). Actually we included benefits line in Our People Matter Most; we should separate benefits. So we can keep the sentence about dedication and then benefits separate.
So About HHS Tech Group paragraph: combine Who We Are, What We Do, Our People Matter Most (first two sentences about dedication). We'll exclude the benefits list.
Thus:
At HHS Tech Group (HTG), our work matters, and each of us makes a difference in the lives of people every day. HTG is a leader in the development and delivery of innovative, purpose-built modular software and technology solutions to clients in the commercial and government sectors. HHS Tech Group creates innovative, purpose-built technology products and solutions, resulting in value and positive, quantifiable impact for our clients and the people they serve. Our people bring our software to life through collaborative relationships with our clients, working as a team, helping to solve complex problems that create positive personal and community impact for the people our clients serve. Each day, our software products and our people are making a difference. Improving the lives of others and making an impact daily is no simple task. We are dedicated to our team’s professional and personal growth and well-being.
Then maybe a short p for location/hybrid remote: Position: (Senior) Director – Product Infrastructure Architecture (Cloud & SaaS Platforms) – Hybrid/Remote
but we shouldn't repeat job title as heading; but we can include it in a p as metadata. It's okay.
Then Role Overview: Role Overview
What You Will Do: Our hands-on (Senior) Director of Product Infrastructure Architecture will define, build, and evolve the cloud-native infrastructure foundation for world-class, multi-tenant SaaS products. This role requires a builder’s mindset and a product-first approach to infrastructure — designing platforms that are secure, scalable, modular, and open to integrations, while enabling rapid product innovation. The ideal candidate is an out-of-the-box thinker, a hands-on technologist, and a people leader who actively mentors and elevates other architects. This role leads Infrastructure & Platform Architects (direct and matrix).
Then Responsibilities: Responsibilities
with each li.
We need to extract each responsibility block.
Let's list them:
1. Product Infrastructure Architecture (Hands-On)
- Serve as lead infrastructure and platform architect for cloud-based SaaS products
- Design and evolve scalable, resilient, and secure infrastructure architectures
- Translate product and business requirements into infrastructure and platform capabilities
- Stay hands-on through design reviews, reference implementations, and architectural spikes
- Balance immediate delivery needs with long-term platform scalability and cost efficiency
2. Cloud-Centric & Multi-Tenant SaaS Design
- Architect cloud-first solutions (AWS, Azure, or GCP) using managed and cloud-native services
- Design and govern multi-tenancy strategies (isolation models, scaling patterns, tenant lifecycle management)
- Ensure platforms support high availability, disaster recovery, and global scalability
- Optimize for cost efficiency, performance, and operational excellence
- Establish patterns for secure tenant onboarding and runtime isolation
3. Data Virtualization & Platform Data Architecture
- Design data virtualization and federated data access layers
- Enable real-time and near-real-time access to data across distributed systems
- Minimize data duplication while maintaining performance and security
- Support analytics, reporting, and integration use cases through standardized data access
- Ensure data architectures align with compliance, privacy, and audit requirements
4. Modern DevOps & Platform Enablement
- Lead architecture for CI/CD pipelines, Infrastructure as Code, and automation-first platforms
- Promote DevOps and Platform Engineering best practices
- Enable self-service environments for product teams
- Partner with SRE and Security teams to ensure reliability and resilience
- Embed observability, monitoring, and automated recovery into the platform
5. Modular, Open & Integration-Ready Platforms
- Champion modular infrastructure and platform designs
- Enable API-first and event-driven integration patterns
- Design platforms that support rapid integration with third-party and ecosystem partners
- Define standards for extensibility without sacrificing governance
- Reduce friction for internal and external product innovation
6. Innovation & Out-of-the-Box Thinking
- Challenge legacy infrastructure and deployment models
- Evaluate emerging cloud and platform technologies
- Identify opportunities to simplify operations through architectural innovation
- Turn experimental ideas into production-grade, scalable solutions
7. Architecture Leadership, Team Building & Knowledge Sharing
- Build, mentor, and grow a high-performing community of infrastructure and platform architects
- Establish architecture forums, guilds, and best-practice communities
- Promote knowledge sharing and architectural consistency across teams
- Influence technical direction across multiple product teams
- Partner closely with Product, Engineering, Security, and Operations leadership
8. Governance, Security & Compliance
- Ensure platforms meet security, privacy, and regulatory requirements
- Define and enforce infrastructure standards and guardrails
- Support audit readiness and operational risk management
- Balance governance with speed and developer autonomy
We'll make each - contain the heading (maybe bold) and then the sub-bullets as a nested
or as sentences separated by semicolons. Simpler: we can put heading as and then a inside? But instruction: use - for any list of duties/requirements/benefits. It didn't forbid nested lists. We can do nested
inside each - . That's okay.
Thus each top-level
- will have Heading then a
- ... etc.
Alternatively we could flatten all responsibilities into a single list but that would lose grouping. Better to nest.
Proceed.
Then Required Experience:
Required Experience
- 12+ years of experience in infrastructure, platform, or cloud architecture
- 5+ years in a Director / Senior technical leadership role
- Deep hands-on experience building multi-tenant SaaS platforms
- Strong expertise in cloud-native architecture (AWS, Azure, or GCP)
- Proven experience with data virtualization and distributed data access
- Extensive experience with modern DevOps practices (CI/CD, IaC, automation)
- Demonstrated success mentoring and leading architecture teams or communities
- Strong communication skills across technical and executive audiences
Preferred Experience: similar.
Leadership Attributes: list.
What Success Looks Like: list.
Education and Certification: paragraph(s). We'll combine: "Bachelor’s degree in Computer Science, Engineering, Information Systems, or related field. One or more professional-level cloud architecture certification (e.g., AWS Solutions Architect – Professional,
for prose. We need to preserve all substantive information, remove boilerplate (cookie/navigation/legal/EEO etc). There's none. We need to include sections only when posting has real specific content. So we will have sections: About the Company (maybe combine Who We Are, What We Do, Our People Matter Most). Could be separate sections but we can combine to avoid thin sections. However the instruction: "Prefer a few substantive sections over many thin ones." So we can create sections like "About HHS Tech Group", "Role Overview", "Responsibilities", "Required Experience", "Preferred Experience", "Leadership Attributes", "What Success Looks Like", "Education and Certification", "Benefits". That's many but each substantive. Could combine some: maybe "About HHS Tech Group" includes Who We Are, What We Do, Our People Matter Most. "Role Overview" includes What You Will Do. Then Responsibilities, Required Experience, Preferred Experience, Leadership Attributes, What Success Looks Like, Education and Certification, Benefits. We need to ensure we don't create empty sections. Let's extract content. Who We Are: "At HHS Tech Group (HTG), our work matters, and each of us makes a difference in the lives of people every day. HTG is a leader in the development and delivery of innovative, purpose-built modular software and technology solutions to clients in the commercial and government sectors." What We Do: "HHS Tech Group creates innovative, purpose-built technology products and solutions, resulting in value and positive, quantifiable impact for our clients and the people they serve. Our people bring our software to life through collaborative relationships with our clients, working as a team, helping to solve complex problems that create positive personal and community impact for the people our clients serve. Each day, our software products and our people are making a difference." Our People Matter Most: "Improving the lives of others and making an impact daily is no simple task. We are dedicated to our team’s professional and personal growth and well-being. Some key rewards and benefits include: Generously sponsored Medical Insurance Fully paid premiums on dental, vision, life and disability insurance. Generous 401k matching program Flexible PTO policy Join us!" But note "Join us!" maybe part of benefits. We'll treat benefits separately. Then "WHO WE ARE HIRING: (Senior) Director – Product Infrastructure Architecture (Cloud & SaaS Platforms) - Hybrid/Remote" - we don't repeat job title as heading, but we could include location/hybrid remote in a short p maybe. Then "What You Will Do": paragraph about hands-on director. Then Responsibilities: list of bullet points (multiple paragraphs each starting with bold headings). We need to convert each bullet into
- .
Preferred Experience: list.
Leadership Attributes: list.
What Success Looks Like: list of bullet points (maybe 4 items). We'll make
- .
Education and Certification: paragraph(s). We'll make
- contain the heading (maybe bold) and then the sub-bullets as a nested
- or as sentences separated by semicolons. Simpler: we can put heading as and then a
- for any list of duties/requirements/benefits. It didn't forbid nested lists. We can do nested
- inside each
- . That's okay. Thus each top-level
- will have Heading then a
- ... etc.
Alternatively we could flatten all responsibilities into a single list but that would lose grouping. Better to nest.
Proceed.
Then Required Experience:
Required Experience
- 12+ years of experience in infrastructure, platform, or cloud architecture
- 5+ years in a Director / Senior technical leadership role
- Deep hands-on experience building multi-tenant SaaS platforms
- Strong expertise in cloud-native architecture (AWS, Azure, or GCP)
- Proven experience with data virtualization and distributed data access
- Extensive experience with modern DevOps practices (CI/CD, IaC, automation)
- Demonstrated success mentoring and leading architecture teams or communities
- Strong communication skills across technical and executive audiences
Bachelor’s degree in Computer Science, Engineering, Information Systems, or related field. One or more professional-level cloud architecture certification (e.g., AWS Solutions Architect – Professional,
- ... etc.
Alternatively we could flatten all responsibilities into a single list but that would lose grouping. Better to nest.
Proceed.
Then Required Experience:
- inside? But instruction: use
- for any list of duties/requirements/benefits. It didn't forbid nested lists. We can do nested
. Benefits: list of benefits: Generously sponsored Medical Insurance, Fully paid premiums on dental, vision, life and disability insurance, Generous 401k matching program, Flexible PTO policy. We also have location hybrid/remote maybe include in a short p under Role Overview. We must not include Job ID/requisition numbers (none). No application instructions. Now produce HTML fragment. Let's craft. Structure:
About HHS Tech Group
... combine Who We Are, What We Do, Our People Matter Most (excluding benefits line? We'll keep benefits separate). Actually we included benefits line in Our People Matter Most; we should separate benefits. So we can keep the sentence about dedication and then benefits separate. So About HHS Tech Group paragraph: combine Who We Are, What We Do, Our People Matter Most (first two sentences about dedication). We'll exclude the benefits list. Thus:
At HHS Tech Group (HTG), our work matters, and each of us makes a difference in the lives of people every day. HTG is a leader in the development and delivery of innovative, purpose-built modular software and technology solutions to clients in the commercial and government sectors. HHS Tech Group creates innovative, purpose-built technology products and solutions, resulting in value and positive, quantifiable impact for our clients and the people they serve. Our people bring our software to life through collaborative relationships with our clients, working as a team, helping to solve complex problems that create positive personal and community impact for the people our clients serve. Each day, our software products and our people are making a difference. Improving the lives of others and making an impact daily is no simple task. We are dedicated to our team’s professional and personal growth and well-being.
Then maybe a short p for location/hybrid remote:Position: (Senior) Director – Product Infrastructure Architecture (Cloud & SaaS Platforms) – Hybrid/Remote
but we shouldn't repeat job title as heading; but we can include it in a p as metadata. It's okay. Then Role Overview:Role Overview
What You Will Do: Our hands-on (Senior) Director of Product Infrastructure Architecture will define, build, and evolve the cloud-native infrastructure foundation for world-class, multi-tenant SaaS products. This role requires a builder’s mindset and a product-first approach to infrastructure — designing platforms that are secure, scalable, modular, and open to integrations, while enabling rapid product innovation. The ideal candidate is an out-of-the-box thinker, a hands-on technologist, and a people leader who actively mentors and elevates other architects. This role leads Infrastructure & Platform Architects (direct and matrix).
Then Responsibilities:Responsibilities
- with each li.
We need to extract each responsibility block.
Let's list them:
1. Product Infrastructure Architecture (Hands-On)
- Serve as lead infrastructure and platform architect for cloud-based SaaS products
- Design and evolve scalable, resilient, and secure infrastructure architectures
- Translate product and business requirements into infrastructure and platform capabilities
- Stay hands-on through design reviews, reference implementations, and architectural spikes
- Balance immediate delivery needs with long-term platform scalability and cost efficiency
2. Cloud-Centric & Multi-Tenant SaaS Design
- Architect cloud-first solutions (AWS, Azure, or GCP) using managed and cloud-native services
- Design and govern multi-tenancy strategies (isolation models, scaling patterns, tenant lifecycle management)
- Ensure platforms support high availability, disaster recovery, and global scalability
- Optimize for cost efficiency, performance, and operational excellence
- Establish patterns for secure tenant onboarding and runtime isolation
3. Data Virtualization & Platform Data Architecture
- Design data virtualization and federated data access layers
- Enable real-time and near-real-time access to data across distributed systems
- Minimize data duplication while maintaining performance and security
- Support analytics, reporting, and integration use cases through standardized data access
- Ensure data architectures align with compliance, privacy, and audit requirements
4. Modern DevOps & Platform Enablement
- Lead architecture for CI/CD pipelines, Infrastructure as Code, and automation-first platforms
- Promote DevOps and Platform Engineering best practices
- Enable self-service environments for product teams
- Partner with SRE and Security teams to ensure reliability and resilience
- Embed observability, monitoring, and automated recovery into the platform
5. Modular, Open & Integration-Ready Platforms
- Champion modular infrastructure and platform designs
- Enable API-first and event-driven integration patterns
- Design platforms that support rapid integration with third-party and ecosystem partners
- Define standards for extensibility without sacrificing governance
- Reduce friction for internal and external product innovation
6. Innovation & Out-of-the-Box Thinking
- Challenge legacy infrastructure and deployment models
- Evaluate emerging cloud and platform technologies
- Identify opportunities to simplify operations through architectural innovation
- Turn experimental ideas into production-grade, scalable solutions
7. Architecture Leadership, Team Building & Knowledge Sharing
- Build, mentor, and grow a high-performing community of infrastructure and platform architects
- Establish architecture forums, guilds, and best-practice communities
- Promote knowledge sharing and architectural consistency across teams
- Influence technical direction across multiple product teams
- Partner closely with Product, Engineering, Security, and Operations leadership
8. Governance, Security & Compliance
- Ensure platforms meet security, privacy, and regulatory requirements
- Define and enforce infrastructure standards and guardrails
- Support audit readiness and operational risk management
- Balance governance with speed and developer autonomy
We'll make each
- contain the heading (maybe bold) and then the sub-bullets as a nested