ServiceNow Solution 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 include only sections that have real specific content. The posting includes: "Who you'll work with" (maybe About the role), "What you'll do" (Responsibilities), "What you'll bring" (Requirements/Qualifications/Skills), "Qualifications" (maybe duplicate), "About Us" (maybe not needed), "Compensation and Benefits" (Pay and Benefits). Also there is "Required Certifications", "Preferred Certifications", "Architecture & Platform Expertise". Those could be part of Requirements/Skills. We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, accommodations, application instructions, etc. Also remove "We are committed to pay transparency..." etc? That's part of compensation but maybe keep? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove EEO and accommodations paragraphs. Also remove "We will accept applicants until September 21, 2026..." maybe that's application instruction? It's a deadline; could be considered application instruction. Probably remove. Also remove contact email for pay questions? Might be considered part of compensation but maybe keep? It's not boilerplate; it's contact for pay questions. Might keep? Safer to keep compensation details but remove contact email? The instruction: remove application instructions. The email for pay questions is not exactly application instruction but could be considered contact. I'd keep it? Might be safer to remove as it's not required content. However we need to preserve ALL substantive information; contact email is substantive? It's about compensation questions. Might be considered not essential. I'd keep compensation ranges and benefits; maybe drop the contact email. We need to produce sections: About the role (maybe from "Who you'll work with" and intro). Responsibilities (What you'll do). Requirements (What you'll bring + Qualifications + Required Certifications + Preferred Certifications + Architecture & Platform Expertise). Skills maybe separate? Could combine. Benefits (from Compensation and Benefits). Pay (salary ranges). Schedule? Not mentioned, so omit. We must not create sections with filler like "commensurate with experience". Not present. We need to use

• for any list of duties/requirements/benefits. So we need to turn bullet-like sentences into lists. We need to preserve all substantive information; not invent or summarize away detail. So we need to keep specifics like years, certifications, etc. Let's extract content. First, "Who you'll work with:" paragraph: As a modern technology company... We have passion... We surround our technologists... This is descriptive about company. Could be About the role. Second, "What you'll do:" bullet list of responsibilities (many sentences). We'll turn each sentence into
• . Third, "What you'll bring:" list of attributes and experience. Then "Qualifications:" repeats some of the same but we need to include all specifics, not duplicate? We should preserve all substantive information; if duplicate, we could still include but maybe deduplicate? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't say to deduplicate duplicates. But we could keep both; but better to avoid redundancy? Might be okay to keep both as they are separate sections. However we need to avoid creating thin sections. Could combine Qualifications into Requirements. We'll create sections:

  About the role

  As a modern technology company, our Slalom Technologists are disrupting the market and bringing to life the art of the possible for our clients. We have passion for building strategies, solutions, and creative products to help our clients solve their most complex and interesting business problems. We surround our technologists with interesting challenges, innovative minds, and emerging technologies.

  Responsibilities

  • Own solution architecture on ServiceNow engagements, translating business requirements into designs that are scalable, maintainable, and aligned to platform standards
  • Architect across the product areas an engagement requires, working outward from your core strengths into adjacent areas as the work calls for it
  • Build working knowledge of ServiceNow products that are new to you, drawing on product documentation, training, a personal developer instance, and the architects around you
  • Grow toward ownership of a center of excellence area over time, deepening one of your core strengths into practice-level expertise that colleagues and client teams can rely on
  • Lead technical design workshops and produce the artifacts that come out of them, including solution design documents, data models, integration designs, and architectural decision records
  • Ensure solutions align to out-of-the-box capabilities and leading practices, challenging customization requests with configuration-first alternatives
  • Design and oversee integrations between ServiceNow and adjacent enterprise systems using REST and SOAP, IntegrationHub, MID Server, transform maps, and scheduled imports
  • Own CMDB and CSDM alignment on your engagements, making sure the data foundation actually supports the workflows being built on top of it
  • Partner with business process consultants and technical consultants, reviewing designs and providing technical direction through build, test, and deployment
  • Contribute hands-on configuration and development when an engagement calls for it, which is a normal part of this role rather than an exception
  • Support testing cycles, defect triage, deployment readiness, cutover, and hypercare with an architectural lens on what the fixes do to the design
  • Advise clients on technical debt, upgrade readiness, platform performance, and the long-term maintainability of what is being built
  • Contribute technical approach, assumptions, risks, and estimation inputs to pre-sales pursuits and RFI/RFP responses
  • Mentor consultants on configuration, scripting, and integration patterns, and actively seek mentorship from senior architects in areas where you are still building depth
  • Grow your certification portfolio deliberately, adding CIS certifications, micro-certifications, and delivery accreditations in areas that are new to you
  • Stay current on platform releases and new products, and form a view on what is worth bringing to clients
  • Contribute to practice development through reusable components, reference designs, patterns, and documented lessons from engagements

  Requirements

  • You are an architect with real depth in a few areas and genuine curiosity about the rest of the platform. You enjoy learning a new module about as much as applying what you already know. You are comfortable being the technical authority in a client conversation, and equally comfortable saying you need a little time to get up to speed on something.
  • 4+ years of consulting experience and 4+ years working on the ServiceNow platform, or a track record that demonstrates equivalent breadth and intensity of platform exposure
  • Strong working depth in two to three ServiceNow areas, with IT Service Management, IT Operations Management, and IT Asset Management being the most valuable to us
  • Working knowledge of CMDB and CSDM, including class and relationship design, identification and reconciliation, and how data quality determines whether anything built on top of it holds up
  • Familiarity with, or a clear appetite for, adjacent areas such as Governance, Risk, and Compliance, Security Operations, Strategic Portfolio Management, and Enterprise Architecture
  • A track record of learning a module you had not worked in before and becoming effective in it, and enthusiasm for doing that again
  • Strong hands-on platform skills across scripting, Flow Designer, IntegrationHub, UI Builder, scoped applications, ACLs and the security model, and data imports
  • Ability to produce clear architecture artifacts that a delivery team can actually build from
  • Comfort being the most technical person in a client room, paired with the judgment to flag when something is outside your depth rather than guessing
  • Strong communication skills, with the ability to explain a technical decision and its trade-offs to a non-technical stakeholder
  • Comfort working across a variety of engagements and problem domains in the near term, paired with an interest in growing

  Qualifications

  • 4+ years of consulting experience and 4+ years on the ServiceNow platform, or equivalent breadth and intensity of platform experience gained over a shorter period
  • At least 3 full-lifecycle ServiceNow implementations in a solution architect, technical lead, or senior technical consultant capacity
  • Required Certifications:
    • ServiceNow Certified System Administrator (CSA)
    • Certified Application Developer (CAD)
    • Architecture Excellence (ArchX)
    • At least three Certified Implementation Specialist (CIS) certifications, including CIS – IT Service Management (CIS-ITSM) and CIS – Data Foundations (CIS-DF)
  • Preferred Certifications:
    • Certified Technical Architect (CTA), highly preferred
    • CIS in an IT Operations Management discipline: CIS – Discovery, CIS – Service Mapping (CIS-SM), or CIS – Event Management (CIS-EM)
    • CIS in an asset discipline: CIS – Software Asset Management (CIS-SAM) or CIS – Hardware Asset Management (CIS-HAM)
    • CIS – Risk and Compliance (CIS-RC)
    • Additional CIS certifications, micro-certifications, or delivery accreditations in areas that are new to you
  • Architecture & Platform Expertise:
    • Strong ServiceNow platform expertise (JavaScript, Flow Designer, IntegrationHub, REST/SOAP APIs, scoped applications, UI Builder, ACLs and platform security, and Reporting/Performance Analytics)
    • Working CMDB, CSDM, and Discovery knowledge, including class hierarchy design, identification and reconciliation rules, and data source precedence
    • Depth in at least two of IT Service Management, IT Operations Management, and IT Asset Management, with working familiarity across the third
    • Exposure to, or interest in building depth in, areas such as Governance, Risk, and Compliance, Security Operations, Strategic Portfolio Management, Enterprise Architecture, and DevOps
    • Experience integrating ServiceNow with enterprise systems such as monitoring and observability tools, endpoint management platforms, procurement and ERP systems, identity providers, and CRM
    • Experience with source control, update set and application repository management, and the Automated Test Framework (ATF)
    • Strong verbal and written communication skills with a developing executive presence
    • Bachelor’s degree or equivalent combination of education and professional experience preferred
  But note: we already have Requirements section; Qualifications may be redundant. However we must preserve all substantive information; we could keep both but risk duplication. The instruction: "Prefer a few substantive sections over many thin ones." Having both Requirements and Qualifications may be thin if they overlap. Could combine them into one section "Requirements and Qualifications". But the instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It lists them as possible headings; we can choose which to include. We could include Requirements and Qualifications both if they have distinct content. However Qualifications includes certifications and architecture expertise; Requirements includes experience and soft skills. They are distinct enough to keep both. We also need Benefits and Pay sections. From "Compensation and Benefits" paragraph: Slalom prides itself on helping team members thrive... benefits include meaningful time off and paid holidays, parental leave, 401(k) with a match, a range of choices for highly subsidized health, dental, & vision coverage, adoption and fertility assistance, and short