ServiceNow Solution Architect

We need to produce HTML fragment with sections: About the role (maybe from "Who you'll work with" and "What you'll do"? Actually "Who you'll work with" is a description of company culture; could be "About the role" or "About the team". We need to use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We need to extract content accordingly. We have: - Title: ServiceNow Solution Architect (not to be repeated as heading) - Who you'll work with: description of Slalom Technologists, culture, etc. Could go under "About the role" or maybe "About the team". We'll put under "About the role". - What you'll do: list of responsibilities (bulleted). So "Responsibilities" section. - What you'll bring: qualifications, skills, etc. This includes required experience, certifications, etc. Could split into "Requirements", "Qualifications", "Skills". The posting has a "Qualifications:" heading with bullet list of required certifications etc. Also there is "Architecture & Platform Expertise:" etc. Also "About Us" etc. Also "Compensation and Benefits" with pay ranges and benefits. We need to map content to sections: - About the role: combine "Who you'll work with" and maybe "About Us"? Actually "About Us" is company description; could be part of About the role. But we need to avoid duplication. We'll include "Who you'll work with" and maybe "About Us" as part of About the role. - Responsibilities: bullet list from "What you'll do". We'll extract each bullet as

. - Requirements: maybe the "What you'll bring" includes required experience, certifications, etc. But there is also a separate "Qualifications:" heading with required certifications. We'll treat "Requirements" as the mandatory experience and certifications (like 4+ years consulting, 4+ years ServiceNow, at least 3 full-lifecycle implementations, required certifications). Also "Qualifications" could be the "Architecture & Platform Expertise:" etc. But we need to avoid thin sections. Perhaps combine Requirements and Qualifications into one? But instructions: use headings for those categories if content exists. We'll create both if they have distinct content. Let's parse: "What you'll bring:" paragraph: You are an architect with real depth... etc. Then bullet list: - 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 Then "Qualifications:" heading with bullet list: - 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 Then "Architecture & Platform Expertise:" heading with bullet list: - 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 Then "About Us" paragraph. Then "Compensation and Benefits" with pay ranges and benefits description. We need to map to sections: - About the role: Could combine "Who you'll work with" and "About Us". But "About Us" is more company overview; still fits. - Responsibilities: from "What you'll do". - Requirements: maybe the mandatory experience and certifications (the "Qualifications:" required certifications and experience). Could be "Requirements". - Qualifications: maybe the "Architecture & Platform Expertise:" and "What you'll bring:" (skills). But we already used "What you'll bring:" for requirements? Hmm. We need to avoid duplication. Let's think: The posting has sections: Who you'll work with, What you'll do, What you'll bring, Qualifications, Architecture & Platform Expertise, About Us, Compensation and Benefits. We can map: - About the role: Who you'll work with + About Us (company description). Could be two paragraphs. - Responsibilities: What you'll do. - Requirements: What you'll bring (the bullet list of experience, depth, etc.)? Actually "What you'll bring" seems like qualifications/skills. But there is also a separate "Qualifications:" heading with certifications. So maybe: - Requirements: the bullet list under "What you'll bring:" (experience, depth, etc.)? Or maybe Requirements = the mandatory experience and certifications (the "Qualifications:" required). But we need to decide. Better to follow typical job posting: Requirements = mandatory experience, education, certifications. Qualifications = preferred or additional qualifications. Skills = technical skills. Thus: - Requirements: 4+ years consulting experience, 4+ years ServiceNow, at least 3 full-lifecycle implementations, required certifications (CSA, CAD, ArchX, at least three CIS including ITSM and DF). Also maybe Bachelor's degree preferred? That's more qualification. - Qualifications: Preferred certifications (CTA, CIS-ITOM, CIS-asset, CIS-RC, additional CIS/micro). Also maybe "Architecture & Platform Expertise:" could be considered Skills. - Skills: The bullet list under "Architecture & Platform Expertise:" (platform expertise, CMDB knowledge, depth in areas, integration experience, source control, communication, degree). Also maybe the hands-on platform skills from "What you'll bring:" (scripting, Flow Designer, etc.) could be skills. But we need to avoid thin sections. Let's see if we have enough content for each. We could combine Requirements and Qualifications into one "Requirements" section that includes both required and preferred? But instructions: prefer a few substantive sections over many thin ones. So maybe we have: - About the role - Responsibilities - Requirements (includes required experience, certifications, education) - Skills (includes technical skills, platform expertise, hands-on skills) - Benefits (includes compensation and benefits description) - Pay (includes salary ranges) - Schedule? Not mentioned; no schedule info, so we omit Schedule. We need to ensure we don't create sections with filler like "commensurate with experience". We have actual pay ranges. Thus: About the role: combine Who you'll work with and About Us. Responsibilities: bullet list from What you'll do. Requirements: bullet list from Qualifications required certifications + experience (4+ years consulting, 4+ years ServiceNow, at least 3 full-lifecycle implementations). Also maybe Bachelor's degree preferred? That's more qualification but could go here. Skills: bullet list from Architecture & Platform Expertise + hands-on platform skills from What you'll bring (scripting, Flow Designer, etc.) + communication skills. Benefits: bullet list from Compensation and Benefits description (meaningful time off, paid holidays, parental leave, 401(k) match, health/dental/vision, adoption/fertility assistance, short/long-term disability, $350 well-being reimbursement, discounted home/auto/pet insurance). Pay: bullet list or maybe a paragraph with salary ranges per location. We'll present as

• for each location range. We must not repeat job title. No markdown. Let's extract exact text. Who you'll work with: "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." About Us: "Slalom is a fiercely human business and technology consulting company that leads with outcomes to bring more value, in all ways, always. From strategy through delivery, our agile teams across 52 offices in 12 countries partner with clients to co-create powerful customer experiences, modern ways of working, and meaningful impact. What sets us apart? We believe work should be challenging and fulfilling, not perfect, but possible. That’s why we prioritize purpose, flexibility, connection, and recognition, so our people can thrive and love what they do, most days." Combine into About the role section: maybe two paragraphs. Responsibilities: list from What you'll do: - 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