ServiceNow Solution Architect

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real specific content. We must not repeat job title. No Job ID etc. Remove boilerplate. Preserve all substantive info. We need to parse the posting. Sections present: - "Who you'll work with": description about company, could be "About the role"? Actually "Who you'll work with" is more about team. Could map to "About the role" maybe. But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content: - "What you'll do": responsibilities list. - "What you'll bring": requirements/qualifications/skills. - "Qualifications": specific qualifications (experience, certifications). - "Architecture & Platform Expertise": more skills. - "About Us": company description (maybe About the role? Actually about company). Could be "About the role"? Not exactly. But we have "About Us" describing Slalom. Could be placed under "About the role"? Might be better as "About the role" includes description of role and team. But we have "Who you'll work with" describing team. Could combine. - "Compensation and Benefits": includes pay ranges and benefits. - No explicit schedule. Thus we will create sections:

About the role

: combine "Who you'll work with" and maybe "About Us"? But "About Us" is company description, not role. However we could still put under About the role as description of the role context. The instruction: use headings only when posting has real specific content for it. We have content for About the role? The posting includes "Who you'll work with:" which describes team and environment. That's relevant to role. So we can put that. Responsibilities: from "What you'll do:" bullet list. Requirements: maybe from "What you'll bring:" (experience, skills). But also there is a separate "Qualifications:" section with certifications etc. We could treat Requirements as experience/skills, Qualifications as certifications/education. But we need to avoid duplication. Let's map: - Requirements: "What you'll bring:" (the paragraph about architect with depth, 4+ years consulting, etc.) plus maybe "Architecture & Platform Expertise:" (skills). Could be combined. - Qualifications: the "Qualifications:" section (experience, certifications) plus maybe "Required Certifications:" etc. - Skills: maybe we could separate but we have many skill details; we could put under Skills heading. But we must not create thin sections. Better to have few substantive sections: About the role, Responsibilities, Qualifications (including experience, certifications, skills), Benefits and Pay (combined). Schedule not present, omit. We need to use

• for any list of duties/requirements/benefits. So we need to turn bullet points into lists. Let's extract content. About the role: combine "Who you'll work with:" and maybe "About Us". Let's include both paragraphs. 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." We can combine into a few paragraphs. Responsibilities: list from "What you'll do:" bullet points (the paragraph after that). Let's extract each sentence as a bullet. The text after "What you'll do:" includes: "As a ServiceNow Solution Architect, you will own solution architecture on ServiceNow engagements across a range of product areas. You already have two or three areas where you are genuinely strong, and you will use those as your base while building working knowledge in others. In the near term the role asks for real breadth, because our demand moves and we need architects who can pick up an unfamiliar module and become effective in it with support from the practice around them. Over time you will settle into a home base and take on growing at least one center of excellence area, developing it into practice-level depth that colleagues and clients can draw on. Some degree of flexibility stays part of the role throughout. You will engage with both business and technology stakeholders, demonstrating strong technical proficiency, professional maturity, and growing executive presence. This is a hands-on architecture role: you design the solution, you defend the design, and you stay close enough to the build to configure and develop when an engagement calls for it." Then a list of bullet-like sentences starting with "Own solution architecture on ServiceNow engagements, translating business requirements into designs that are scalable, maintainable, and aligned to platform standards" etc. Those are separate bullet points. We'll treat each line as
• . Let's list them: - 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 Now Requirements/Skills/Qualifications. We have "What you'll bring:" paragraph: "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" We can turn each sentence into bullet under Requirements or Skills. Then we have "Qualifications:" section: "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" Then "Architecture & Platform Expertise:" 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" We need to avoid duplication. We could combine all skill/experience/qualification content under a single "Qualifications" section, using lists for certifications, experience, skills. But the instruction: Use headings only when posting has real specific content for it. We have content for Qualifications (certifications, experience, education). We also have content for Skills (maybe we could merge). To avoid many thin sections, we can have: - About the role - Responsibilities - Qualifications (includes experience, skills, certifications, education) - Benefits and Pay (combined) We should not create