ServiceNow Architect

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate like About Us? Actually "About Us" is a section; we can treat as "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. The posting includes "About Us" (company description). Could map to "About the role"? Actually "About Us" is about company, not role. But we could still include as "About the role"? Might be okay. However we need to include only sections with real content. Let's identify sections: - About Us (company overview) -> could be "About the role"? Might be better to use "About the role" heading and put company description there? But the instruction says use those headings as examples; we can use others? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those exact headings if content exists. We have content for About the role? There's a "The Role" section describing role. That could be "About the role". Yes. - Responsibilities: there is a list under "To Be Successful Here You Will ..." which are responsibilities/duties. Also earlier "The Role" includes responsibilities. We'll combine. - Requirements: there is "Required Qualifications". That's qualifications. - Qualifications: maybe same as Required Qualifications? Could separate "Qualifications" and "Skills"? But we have both qualifications and skills listed. We could put qualifications under "Qualifications" and skills under "Skills". However the posting includes "Required Qualifications" with bullet-like paragraphs. Also includes "Relevant ServiceNow and industry certifications". That's qualifications. - Skills: we could extract skills like client-facing, stakeholder management, communication, collaboration, etc. Might be covered in qualifications. But we can still create a Skills section if there is explicit skill list. The posting includes "Strong client-facing and stakeholder management skills..." etc. That's skill. We'll put under Skills. - Benefits: there is "Our Benefits" section with list: Ongoing personal and professional development opportunities. Flexible paid time off, plus 12 paid holidays. Premium healthcare plans — Medical, Dental, Vision — including HSA and FSA options. Qualified 401(k) program. - Pay: not mentioned. So we should NOT include Pay section. - Schedule: not mentioned (no mention of full-time/part-time, hours). So omit. We also need to include maybe "About the role" from "The Role" paragraph. We must not include boilerplate like "Physical Demands", "Work Environment", "Equal Opportunity Employer", "Disclaimer". Remove those. Also remove navigation, cookie, legal, EEO, scam-warning, duplicated lines, application instructions. We must preserve all substantive information. So we need to keep the content from About Us, The Role, To Be Successful Here You Will..., Required Qualifications, Our Benefits. We need to format as HTML: use

for each section heading, then content: either

for prose,

• for lists. We need to decide what goes into each section. Section "About the role": could include the description from "The Role" paragraph (starting "The Role The Architect serves as a trusted technical advisor...") plus maybe the "About Us"? Actually "About Us" is about company, not role. But we could treat "About the role" as the role description. The "About Us" could be omitted? But we must preserve ALL substantive information. If we omit About Us, we lose that info. However we could incorporate it into "About the role" or maybe create a separate section like "About the company". But the instruction only gave examples; we could still add other headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use

  for section headings (e.g. ...)". Likely they expect only those headings. But we need to preserve all substantive info; we could embed About Us content into About the role section as a preamble. That would preserve it. Thus About the role section will contain both company overview and role description. Now Responsibilities: we need to list duties. The "To Be Successful Here You Will ..." list includes many bullet-like sentences. Also earlier "The Role" includes some responsibilities. We'll combine them into a list. We need to extract each duty as a

  . Let's parse: From "To Be Successful Here You Will": - Serve as an architectural lead for ServiceNow implementations, providing technical guidance to client stakeholders and delivery teams. - Design scalable ServiceNow solutions aligned with business requirements, platform best practices, and customer technology standards. - Guide architectural decisions across complex, multi-module implementations, considering scalability, maintainability, security, and performance. - Design integration solutions using APIs, event-driven approaches, and other appropriate integration patterns. - Architect ServiceNow solutions across multiple areas, with a particular focus on Strategic Portfolio Management (SPM) and/or Field Service Management (FSM), along with capabilities such as ITSM, CMDB/CSDM, HRSD, Discovery & Service Mapping, Virtual Agent, GRC/IRM, SIR, and SAM/HAM. - Develop solution architectures, automation approaches, and data/service models that improve efficiency, compliance, scalability, and user experience. - Identify technical risks, dependencies, and trade-offs and communicate recommendations clearly to client and delivery stakeholders. - Support platform governance, architectural standards, and technical review practices throughout the delivery lifecycle. - Collaborate with developers, consultants, and other architects to ensure solutions are implemented in alignment with the approved architecture. - Provide technical guidance and mentorship to development and delivery team members as needed. - Support reporting, KPI, and value-realization approaches that connect delivered capabilities to customer outcomes. Also from "The Role" paragraph: "Working closely with client stakeholders, technology leaders, and delivery teams, this role translates business and technical requirements into scalable, sustainable ServiceNow solutions. The Architect provides architectural direction across the platform, including integrations, data and service models, security considerations, governance, and multi-module solution design. They guide technical decisions, identify architectural risks and dependencies, and ensure solutions align with customer requirements, ServiceNow best practices, and broader technology standards. This role combines hands-on solution architecture with strong client engagement, partnering with developers and cross-functional teams to solve complex technical challenges and successfully deliver ServiceNow capabilities." These are somewhat overlapping with responsibilities list; we can include them but avoid duplication. We'll keep the list from To Be Successful Here as responsibilities; maybe add a few unique ones not covered: "translates business and technical requirements into scalable, sustainable ServiceNow solutions" (covered by design scalable solutions). "provides architectural direction across the platform, including integrations, data and service models, security considerations, governance, and multi-module solution design" (covered). "guide technical decisions, identify architectural risks and dependencies, and ensure solutions align with customer requirements, ServiceNow best practices, and broader technology standards" (covered). "combines hands-on solution architecture with strong client engagement, partnering with developers and cross-functional teams to solve complex technical challenges and successfully deliver ServiceNow capabilities" (covered by collaborate and provide guidance). So we can stick with the list. Now Requirements: The posting has "Required Qualifications" which is a list of qualifications. We'll treat that as Requirements section? Actually they separate Requirements and Qualifications. Could treat Required Qualifications as Requirements, and maybe also include "Relevant ServiceNow and industry certifications" as Qualifications? But we have both sections. Let's decide: - Requirements: maybe the mandatory items like degree, years of experience, etc. - Qualifications: maybe the preferred experience, certifications, etc. But the instruction says use headings for Requirements, Qualifications, Skills, Benefits etc. We'll allocate content accordingly. From Required Qualifications paragraph: "Bachelor’s degree in IT or a related field with relevant professional experience, or equivalent combination of education and experience. 6+ years of relevant technology consulting, architecture, or enterprise platform experience, including experience supporting complex technology transformation initiatives. 4+ years delivering enterprise platform solutions, with strong ServiceNow experience preferred. Demonstrated experience serving as a technical or solution architect for complex ServiceNow implementations involving multiple modules, integrations, or stakeholder groups. Strong understanding of solution architecture, platform governance, and architectural design principles, with familiarity with frameworks such as TOGAF, ITIL, COBIT, Agile, or PMI. Experience architecting ServiceNow solutions, with Strategic Portfolio Management (SPM) and/or Field Service Management (FSM) experience strongly preferred. Experience designing integrations, including API-led and event-driven approaches, and data models across complex technology environments. Experience working within platform governance and architectural standards and contributing to implementation strategies. Strong client-facing and stakeholder management skills, with the ability to communicate technical concepts, risks, and recommendations to both technical and non-technical audiences. Ability to collaborate across technical and functional teams, navigate ambiguity, and balance architectural best practices with pragmatic delivery. Relevant ServiceNow and industry certifications such as CSA, CAD, CIS certifications, CTA, Architecture Excellence Accreditation, Implementation Badges, and/or ITIL certifications." We could split: Requirements: the first few items (degree, years experience). Qualifications: the rest (experience as architect, understanding, certifications). Skills: maybe the client-facing, collaboration, etc. But those are also in qualifications. Better: Use Requirements for the degree and years of experience. Qualifications for the demonstrated experience, understanding, experience architecting, etc. Skills for client-facing, stakeholder management, collaboration, communication, etc. Benefits as given. Let's craft:

  About the role

  At Intact Technology, we are driven by a shared commitment to customer success, employee fulfillment, and meaningful impact. We combine human ingenuity with intelligent tools to deliver smarter solutions, faster outcomes, and exceptional value for our clients and partners. We operate in an AI-enabled, outcome-based delivery model, where technology accelerates execution and our teams focus on judgment, problem solving, client impact, and accountability. Success at Intact requires the ability to leverage tools effectively while applying a critical, thoughtful approach to client situations and delivery outcomes. Our culture is built around individuality, autonomy, and empowerment, with the freedom to think creatively, act boldly, and make an impact. We support that with a flexible work environment, comprehensive benefits, and continued investment in learning and career growth.

  The Architect serves as a trusted technical advisor and architectural lead for complex ServiceNow implementations. Working closely with client stakeholders, technology leaders, and delivery teams, this role translates business and technical requirements into scalable, sustainable ServiceNow solutions. The Architect provides architectural direction across the platform, including integrations, data and service models, security considerations, governance, and multi-module solution design. They guide technical decisions, identify architectural risks and dependencies, and ensure solutions align with customer requirements, ServiceNow best practices, and broader technology standards. This role combines hands-on solution architecture with strong client engagement, partnering with developers and cross-functional teams to solve complex technical challenges and successfully deliver ServiceNow capabilities.

  Responsibilities

  • Serve as an architectural lead for ServiceNow implementations, providing technical guidance to client stakeholders and delivery teams.
  • Design scalable ServiceNow solutions aligned with business requirements, platform best practices, and customer technology standards.
  • Guide architectural decisions across complex, multi-module implementations, considering scalability, maintainability, security, and performance.
  • Design integration solutions using APIs, event-driven approaches, and other appropriate integration patterns.
  • Architect ServiceNow solutions across multiple areas, with a particular focus on Strategic Portfolio