Lead Solutions Architect
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we must map content to appropriate headings. The instructions: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
Thus we need to decide which sections to include based on content. The posting includes:
- About Acuative (company description) – could be "About the role"? Actually "About the role" is typical but we have "About Acuative". Could map to "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should use those exact headings if we have content. But we have content that doesn't exactly match those headings; we need to map content to appropriate headings. For example:
- About the role: could include description of role, opportunity, what you'll be working on, what you'll do. That seems like responsibilities.
- Responsibilities: list of duties (What You'll Do). Could be bullet list.
- Requirements: required qualifications (What We're Looking For: Required). Could be bullet list.
- Qualifications: maybe preferred qualifications.
- Skills: maybe technology stack.
- Benefits: Why Join Acuative? Could be benefits.
- Pay: not present, so omit.
- Schedule: not present, omit.
We must not create sections with filler. So include only those with real content.
Thus sections: About the role (maybe combine About Acuative and The Opportunity?), Responsibilities, Requirements, Qualifications, Skills, Benefits.
We need to ensure we don't repeat job title.
We need to use
for each section heading.
Inside each section, we can have
for prose and
- for lists.
We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them.
We must remove boilerplate: cookie/navigation/legal/EEO etc. There's none.
We must not include application instructions (like "If you're a hands-on architect...") Actually that is part of Why Join? It's okay.
We need to be careful not to duplicate lines.
Let's extract content:
About Acuative: "Acuative is a leading provider of managed networking, field services, and technology solutions supporting enterprise and public-sector customers throughout North America.As we continue to evolve our technology platform and modernize our business systems, we are seeking a Lead Solutions Architect to serve as the senior technical leader for our Information Systems organization."
The Opportunity: "This role combines the responsibilities of a software architect, lead developer, technical mentor, and strategic technology advisor.You will work closely with our IS Manager, Business Analysts, and development teams to define technical strategy, guide solution architecture, mentor developers, and drive modernization initiatives across our application ecosystem.Unlike many architecture roles, this position remains hands-on. You’ll have the opportunity to solve complex technical challenges, influence platform direction, and help shape the future of our development organization."
What You’ll Be Working On: bullet list (actually sentences separated by periods). Items:
- A proprietary ERP platform supporting core business operations.
- Enterprise workflow automation initiatives.
- ITSM platform strategy and ServiceNow evaluation efforts.
- System integrations and API development.
- Application modernization and technical debt reduction.
- DevOps and CI/CD process improvements.
- AI-enabled productivity and automation initiatives.
- Growth and mentorship of domestic and offshore development teams.
What You’ll Do: sections with bullet-like sentences:
Technical Leadership:
- Serve as the senior technical leader for Acuative’s application ecosystem.
- Establish architecture standards, development practices, and engineering guidelines.
- Mentor developers and help grow technical capabilities across the organization.
- Conduct architecture reviews, design reviews, and code reviews.
Architecture & Solution Design:
- Design scalable, secure, and maintainable enterprise solutions.
- Define integration strategies between internal and external systems.
- Guide long-term application and technology roadmaps.
- Ensure solutions align with business objectives and operational requirements.
Development Leadership:
- Participate in hands-on software development for strategic initiatives.
- Lead modernization efforts and platform evolution.
- Solve complex application, integration, and data challenges.
- Improve application quality, reliability, and performance.
DevOps & Engineering Excellence:
- Lead GitLab-based source control and CI/CD strategy.
- Promote DevOps and DevSecOps practices.
- Improve deployment automation, testing, and release management.
- Establish standards for maintainability, observability, and operational support.
Technology Environment: prose plus list:
"Our current technology stack includes:
C#..NET Framework and modern .NET.
Angular.
SQL Server / T-SQL.
GitLab.
REST APIs.
Proprietary ERP platform.
Cherwell ITSM.
ServiceNow (evaluation and future planning).
Our environment is predominantly on-premises due to customer and regulatory requirements, with selective adoption of cloud and hybrid technologies where appropriate."
What We’re Looking For:
Required:
- 10+ years of software development experience.
- 5+ years in architecture or technical leadership roles.
- Deep expertise with C#, .NET, Angular, and SQL Server.
- Strong experience with GitLab and CI/CD pipelines.
- Experience designing enterprise application architectures.
- Experience leading or mentoring software development teams.
- Excellent communication and stakeholder management skills.
- U.S. Citizenship.
- Ability to obtain and maintain a U.S. Government Public Trust clearance.
Preferred:
- Experience with ERP platforms or highly customized enterprise applications.
- Experience with ServiceNow or enterprise ITSM platforms.
- Experience in managed services, telecommunications, networking, or field services.
- Experience supporting public-sector or regulated environments.
- Experience with AI-assisted software development and automation technologies.
- Familiarity with ITIL and service management processes.
Why Join Acuative? bullet list:
- Lead architecture for business-critical enterprise systems.
- Influence technology strategy and modernization efforts.
- Partner directly with business leadership and product stakeholders.
- Help shape a growing development organization.
- Work with modern Microsoft technologies and enterprise-scale systems.
- Opportunity to make a measurable impact on business operations and customer success.
Also closing sentence: "If you’re a hands-on architect who enjoys solving complex problems, mentoring teams, and building enterprise software that directly impacts business outcomes, we’d like to hear from you." This could be part of Benefits or a final paragraph.
We need to avoid duplication. Some content appears in multiple places (e.g., technology stack appears also in required). We'll keep all.
Now decide sections:
- About the role: could combine About Acuative + The Opportunity + What You’ll Be Working On? But that may be too much. Better to have sections: About the role (company description + opportunity), Responsibilities (What You’ll Do), Requirements (Required), Qualifications (Preferred), Skills (Technology Environment), Benefits (Why Join Acuative + closing). That seems reasonable.
We must not create Pay/Schedule sections.
Now produce HTML:
About the role
Acuative is a leading provider of managed networking, field services, and technology solutions supporting enterprise and public-sector customers throughout North America. As we continue to evolve our technology platform and modernize our business systems, we are seeking a Lead Solutions Architect to serve as the senior technical leader for our Information Systems organization. This role combines the responsibilities of a software architect, lead developer, technical mentor, and strategic technology advisor. You will work closely with our IS Manager, Business Analysts, and development teams to define technical strategy, guide solution architecture, mentor developers, and drive modernization initiatives across our application ecosystem. Unlike many architecture roles, this position remains hands-on. You’ll have the opportunity to solve complex technical challenges, influence platform direction, and help shape the future of our development organization.
What you’ll be working on:
- A proprietary ERP platform supporting core business operations.
- Enterprise workflow automation initiatives.
- ITSM platform strategy and ServiceNow evaluation efforts.
- System integrations and API development.
- Application modernization and technical debt reduction.
- DevOps and CI/CD process improvements.
- AI-enabled productivity and automation initiatives.
- Growth and mentorship of domestic and offshore development teams.
Responsibilities
What you’ll do:
- Technical Leadership: Serve as the senior technical leader for Acuative’s application ecosystem; establish architecture standards, development practices, and engineering guidelines; mentor developers and help grow technical capabilities across the organization; conduct architecture reviews, design reviews, and code reviews.
- Architecture & Solution Design: Design scalable, secure, and maintainable enterprise solutions; define integration strategies between internal and external systems; guide long-term application and technology roadmaps; ensure solutions align with business objectives and operational requirements.
- Development Leadership: Participate in hands-on software development for strategic initiatives; lead modernization efforts and platform evolution; solve complex application, integration, and data challenges; improve application quality, reliability, and performance.
- DevOps & Engineering Excellence: Lead GitLab-based source control and CI/CD strategy; promote DevOps and DevSecOps practices; improve deployment automation, testing, and release management; establish standards for maintainability, observability, and operational support.
Requirements
- 10+ years of software development experience.
- 5+ years in architecture or technical leadership roles.
- Deep expertise with C#, .NET, Angular, and SQL Server.
- Strong experience with GitLab and CI/CD pipelines.
- Experience designing enterprise application architectures.
- Experience leading or mentoring software development teams.
- Excellent communication and stakeholder management skills.
- U.S. Citizenship.
- Ability to obtain and maintain a U.S. Government Public Trust clearance.
Qualifications
- Experience with ERP platforms or highly customized enterprise applications.
- Experience with ServiceNow or enterprise ITSM platforms.
- Experience in managed services, telecommunications, networking, or field services.
- Experience supporting public-sector or regulated environments.
- Experience with AI-assisted software development and automation technologies.
- Familiarity with ITIL and service management processes.
Skills
Our current technology stack includes:
- C#/.NET Framework and modern .NET
- Angular
- SQL Server / T-SQL
- GitLab
- REST APIs
- Proprietary
- for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to decide which sections to include based on content. The posting includes: - About Acuative (company description) – could be "About the role"? Actually "About the role" is typical but we have "About Acuative". Could map to "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should use those exact headings if we have content. But we have content that doesn't exactly match those headings; we need to map content to appropriate headings. For example: - About the role: could include description of role, opportunity, what you'll be working on, what you'll do. That seems like responsibilities. - Responsibilities: list of duties (What You'll Do). Could be bullet list. - Requirements: required qualifications (What We're Looking For: Required). Could be bullet list. - Qualifications: maybe preferred qualifications. - Skills: maybe technology stack. - Benefits: Why Join Acuative? Could be benefits. - Pay: not present, so omit. - Schedule: not present, omit. We must not create sections with filler. So include only those with real content. Thus sections: About the role (maybe combine About Acuative and The Opportunity?), Responsibilities, Requirements, Qualifications, Skills, Benefits. We need to ensure we don't repeat job title. We need to use
for each section heading. Inside each section, we can have
for prose and
- for lists.
We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them.
We must remove boilerplate: cookie/navigation/legal/EEO etc. There's none.
We must not include application instructions (like "If you're a hands-on architect...") Actually that is part of Why Join? It's okay.
We need to be careful not to duplicate lines.
Let's extract content:
About Acuative: "Acuative is a leading provider of managed networking, field services, and technology solutions supporting enterprise and public-sector customers throughout North America.As we continue to evolve our technology platform and modernize our business systems, we are seeking a Lead Solutions Architect to serve as the senior technical leader for our Information Systems organization."
The Opportunity: "This role combines the responsibilities of a software architect, lead developer, technical mentor, and strategic technology advisor.You will work closely with our IS Manager, Business Analysts, and development teams to define technical strategy, guide solution architecture, mentor developers, and drive modernization initiatives across our application ecosystem.Unlike many architecture roles, this position remains hands-on. You’ll have the opportunity to solve complex technical challenges, influence platform direction, and help shape the future of our development organization."
What You’ll Be Working On: bullet list (actually sentences separated by periods). Items:
- A proprietary ERP platform supporting core business operations.
- Enterprise workflow automation initiatives.
- ITSM platform strategy and ServiceNow evaluation efforts.
- System integrations and API development.
- Application modernization and technical debt reduction.
- DevOps and CI/CD process improvements.
- AI-enabled productivity and automation initiatives.
- Growth and mentorship of domestic and offshore development teams.
What You’ll Do: sections with bullet-like sentences:
Technical Leadership:
- Serve as the senior technical leader for Acuative’s application ecosystem.
- Establish architecture standards, development practices, and engineering guidelines.
- Mentor developers and help grow technical capabilities across the organization.
- Conduct architecture reviews, design reviews, and code reviews.
Architecture & Solution Design:
- Design scalable, secure, and maintainable enterprise solutions.
- Define integration strategies between internal and external systems.
- Guide long-term application and technology roadmaps.
- Ensure solutions align with business objectives and operational requirements.
Development Leadership:
- Participate in hands-on software development for strategic initiatives.
- Lead modernization efforts and platform evolution.
- Solve complex application, integration, and data challenges.
- Improve application quality, reliability, and performance.
DevOps & Engineering Excellence:
- Lead GitLab-based source control and CI/CD strategy.
- Promote DevOps and DevSecOps practices.
- Improve deployment automation, testing, and release management.
- Establish standards for maintainability, observability, and operational support.
Technology Environment: prose plus list:
"Our current technology stack includes:
C#..NET Framework and modern .NET.
Angular.
SQL Server / T-SQL.
GitLab.
REST APIs.
Proprietary ERP platform.
Cherwell ITSM.
ServiceNow (evaluation and future planning).
Our environment is predominantly on-premises due to customer and regulatory requirements, with selective adoption of cloud and hybrid technologies where appropriate."
What We’re Looking For:
Required:
- 10+ years of software development experience.
- 5+ years in architecture or technical leadership roles.
- Deep expertise with C#, .NET, Angular, and SQL Server.
- Strong experience with GitLab and CI/CD pipelines.
- Experience designing enterprise application architectures.
- Experience leading or mentoring software development teams.
- Excellent communication and stakeholder management skills.
- U.S. Citizenship.
- Ability to obtain and maintain a U.S. Government Public Trust clearance.
Preferred:
- Experience with ERP platforms or highly customized enterprise applications.
- Experience with ServiceNow or enterprise ITSM platforms.
- Experience in managed services, telecommunications, networking, or field services.
- Experience supporting public-sector or regulated environments.
- Experience with AI-assisted software development and automation technologies.
- Familiarity with ITIL and service management processes.
Why Join Acuative? bullet list:
- Lead architecture for business-critical enterprise systems.
- Influence technology strategy and modernization efforts.
- Partner directly with business leadership and product stakeholders.
- Help shape a growing development organization.
- Work with modern Microsoft technologies and enterprise-scale systems.
- Opportunity to make a measurable impact on business operations and customer success.
Also closing sentence: "If you’re a hands-on architect who enjoys solving complex problems, mentoring teams, and building enterprise software that directly impacts business outcomes, we’d like to hear from you." This could be part of Benefits or a final paragraph.
We need to avoid duplication. Some content appears in multiple places (e.g., technology stack appears also in required). We'll keep all.
Now decide sections:
- About the role: could combine About Acuative + The Opportunity + What You’ll Be Working On? But that may be too much. Better to have sections: About the role (company description + opportunity), Responsibilities (What You’ll Do), Requirements (Required), Qualifications (Preferred), Skills (Technology Environment), Benefits (Why Join Acuative + closing). That seems reasonable.
We must not create Pay/Schedule sections.
Now produce HTML:
About the role
Acuative is a leading provider of managed networking, field services, and technology solutions supporting enterprise and public-sector customers throughout North America. As we continue to evolve our technology platform and modernize our business systems, we are seeking a Lead Solutions Architect to serve as the senior technical leader for our Information Systems organization. This role combines the responsibilities of a software architect, lead developer, technical mentor, and strategic technology advisor. You will work closely with our IS Manager, Business Analysts, and development teams to define technical strategy, guide solution architecture, mentor developers, and drive modernization initiatives across our application ecosystem. Unlike many architecture roles, this position remains hands-on. You’ll have the opportunity to solve complex technical challenges, influence platform direction, and help shape the future of our development organization.
What you’ll be working on:
- A proprietary ERP platform supporting core business operations.
- Enterprise workflow automation initiatives.
- ITSM platform strategy and ServiceNow evaluation efforts.
- System integrations and API development.
- Application modernization and technical debt reduction.
- DevOps and CI/CD process improvements.
- AI-enabled productivity and automation initiatives.
- Growth and mentorship of domestic and offshore development teams.
Responsibilities
What you’ll do:
- Technical Leadership: Serve as the senior technical leader for Acuative’s application ecosystem; establish architecture standards, development practices, and engineering guidelines; mentor developers and help grow technical capabilities across the organization; conduct architecture reviews, design reviews, and code reviews.
- Architecture & Solution Design: Design scalable, secure, and maintainable enterprise solutions; define integration strategies between internal and external systems; guide long-term application and technology roadmaps; ensure solutions align with business objectives and operational requirements.
- Development Leadership: Participate in hands-on software development for strategic initiatives; lead modernization efforts and platform evolution; solve complex application, integration, and data challenges; improve application quality, reliability, and performance.
- DevOps & Engineering Excellence: Lead GitLab-based source control and CI/CD strategy; promote DevOps and DevSecOps practices; improve deployment automation, testing, and release management; establish standards for maintainability, observability, and operational support.
Requirements
- 10+ years of software development experience.
- 5+ years in architecture or technical leadership roles.
- Deep expertise with C#, .NET, Angular, and SQL Server.
- Strong experience with GitLab and CI/CD pipelines.
- Experience designing enterprise application architectures.
- Experience leading or mentoring software development teams.
- Excellent communication and stakeholder management skills.
- U.S. Citizenship.
- Ability to obtain and maintain a U.S. Government Public Trust clearance.
Qualifications
- Experience with ERP platforms or highly customized enterprise applications.
- Experience with ServiceNow or enterprise ITSM platforms.
- Experience in managed services, telecommunications, networking, or field services.
- Experience supporting public-sector or regulated environments.
- Experience with AI-assisted software development and automation technologies.
- Familiarity with ITIL and service management processes.
Skills
Our current technology stack includes:
- C#/.NET Framework and modern .NET
- Angular
- SQL Server / T-SQL
- GitLab
- REST APIs
- Proprietary
- for lists.
We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them.
We must remove boilerplate: cookie/navigation/legal/EEO etc. There's none.
We must not include application instructions (like "If you're a hands-on architect...") Actually that is part of Why Join? It's okay.
We need to be careful not to duplicate lines.
Let's extract content:
About Acuative: "Acuative is a leading provider of managed networking, field services, and technology solutions supporting enterprise and public-sector customers throughout North America.As we continue to evolve our technology platform and modernize our business systems, we are seeking a Lead Solutions Architect to serve as the senior technical leader for our Information Systems organization."
The Opportunity: "This role combines the responsibilities of a software architect, lead developer, technical mentor, and strategic technology advisor.You will work closely with our IS Manager, Business Analysts, and development teams to define technical strategy, guide solution architecture, mentor developers, and drive modernization initiatives across our application ecosystem.Unlike many architecture roles, this position remains hands-on. You’ll have the opportunity to solve complex technical challenges, influence platform direction, and help shape the future of our development organization."
What You’ll Be Working On: bullet list (actually sentences separated by periods). Items:
- A proprietary ERP platform supporting core business operations.
- Enterprise workflow automation initiatives.
- ITSM platform strategy and ServiceNow evaluation efforts.
- System integrations and API development.
- Application modernization and technical debt reduction.
- DevOps and CI/CD process improvements.
- AI-enabled productivity and automation initiatives.
- Growth and mentorship of domestic and offshore development teams.
What You’ll Do: sections with bullet-like sentences:
Technical Leadership:
- Serve as the senior technical leader for Acuative’s application ecosystem.
- Establish architecture standards, development practices, and engineering guidelines.
- Mentor developers and help grow technical capabilities across the organization.
- Conduct architecture reviews, design reviews, and code reviews.
Architecture & Solution Design:
- Design scalable, secure, and maintainable enterprise solutions.
- Define integration strategies between internal and external systems.
- Guide long-term application and technology roadmaps.
- Ensure solutions align with business objectives and operational requirements.
Development Leadership:
- Participate in hands-on software development for strategic initiatives.
- Lead modernization efforts and platform evolution.
- Solve complex application, integration, and data challenges.
- Improve application quality, reliability, and performance.
DevOps & Engineering Excellence:
- Lead GitLab-based source control and CI/CD strategy.
- Promote DevOps and DevSecOps practices.
- Improve deployment automation, testing, and release management.
- Establish standards for maintainability, observability, and operational support.
Technology Environment: prose plus list:
"Our current technology stack includes:
C#..NET Framework and modern .NET.
Angular.
SQL Server / T-SQL.
GitLab.
REST APIs.
Proprietary ERP platform.
Cherwell ITSM.
ServiceNow (evaluation and future planning).
Our environment is predominantly on-premises due to customer and regulatory requirements, with selective adoption of cloud and hybrid technologies where appropriate."
What We’re Looking For:
Required:
- 10+ years of software development experience.
- 5+ years in architecture or technical leadership roles.
- Deep expertise with C#, .NET, Angular, and SQL Server.
- Strong experience with GitLab and CI/CD pipelines.
- Experience designing enterprise application architectures.
- Experience leading or mentoring software development teams.
- Excellent communication and stakeholder management skills.
- U.S. Citizenship.
- Ability to obtain and maintain a U.S. Government Public Trust clearance.
Preferred:
- Experience with ERP platforms or highly customized enterprise applications.
- Experience with ServiceNow or enterprise ITSM platforms.
- Experience in managed services, telecommunications, networking, or field services.
- Experience supporting public-sector or regulated environments.
- Experience with AI-assisted software development and automation technologies.
- Familiarity with ITIL and service management processes.
Why Join Acuative? bullet list:
- Lead architecture for business-critical enterprise systems.
- Influence technology strategy and modernization efforts.
- Partner directly with business leadership and product stakeholders.
- Help shape a growing development organization.
- Work with modern Microsoft technologies and enterprise-scale systems.
- Opportunity to make a measurable impact on business operations and customer success.
Also closing sentence: "If you’re a hands-on architect who enjoys solving complex problems, mentoring teams, and building enterprise software that directly impacts business outcomes, we’d like to hear from you." This could be part of Benefits or a final paragraph.
We need to avoid duplication. Some content appears in multiple places (e.g., technology stack appears also in required). We'll keep all.
Now decide sections:
- About the role: could combine About Acuative + The Opportunity + What You’ll Be Working On? But that may be too much. Better to have sections: About the role (company description + opportunity), Responsibilities (What You’ll Do), Requirements (Required), Qualifications (Preferred), Skills (Technology Environment), Benefits (Why Join Acuative + closing). That seems reasonable.
We must not create Pay/Schedule sections.
Now produce HTML: