ServiceNow Solution Architect

We need to output HTML fragment with sections: About the role? Actually the posting includes sections: "Who you'll work with", "What you'll do", "What you'll bring", "Qualifications", "About Us", "Compensation and Benefits". According to rules: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to map headings accordingly. We should not repeat job title. We need to include sections only when posting has real specific content. We have content for: Who you'll work with (intro about team), What you'll do (responsibilities), What you'll bring (skills/qualifications), Qualifications (certifications etc), About Us (company description), Compensation and Benefits (pay ranges, benefits). Also maybe "Skills" could be derived from "What you'll bring" but we can treat as Skills. We need to use

• for any list of duties/requirements/benefits. So we need to convert bullet-like sentences into lists. We must not include boilerplate like EEO, accommodations, application instructions, cookie/navigation/legal, duplicated lines. Also remove "We are committed to pay transparency..." etc? That's part of compensation but maybe still relevant? It's about pay range contact. Might be considered boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The EEO section is separate; we should remove it. The compensation contact line maybe not boilerplate but it's about pay range contact; could be kept? It's not EEO. Might be okay to keep as part of Compensation and Benefits. However it's a contact email; maybe keep. We need to preserve all substantive information. So we need to include details about responsibilities, qualifications, certifications, benefits, pay ranges, about us. We must not create sections with filler like "commensurate with experience". Not present. We'll produce HTML fragment with

  headings: maybe "About the team" (Who you'll work with) but the allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could map: "Who you'll work with" -> maybe "About the role"? Not exactly. Could use "About the role" for description of role and team. But we have separate sections for responsibilities etc. Let's decide: - Use

  About the role

  for the introductory paragraph about who you'll work with and role context. - Use

  Responsibilities

  for "What you'll do". - Use

  Qualifications

  for "What you'll bring" plus maybe also separate "Qualifications" heading for certifications? Actually there is a "Qualifications:" section later. Could combine? But we should not duplicate. Perhaps we treat "What you'll bring" as Skills, and the later "Qualifications:" as Qualifications (certifications, experience). The allowed headings include Skills and Qualifications. So we can have:

  Skills

  for "What you'll bring" (skills, experience, traits).

  Qualifications

  for the "Qualifications:" section (experience, certifications, etc).

  Benefits

  for benefits description.

  Pay

  for compensation ranges.

  About Us

  maybe not in allowed list but we could use "About the role"? Actually we have About Us separate; we could treat as "About the role"? Not ideal. The allowed headings list is examples, not strict? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those headings when applicable, but we can also use other headings if needed? It says use

  for section headings (e.g. ...). Likely we should stick to those headings; but we have About Us content, maybe we can put under "About the role"? Or we could create a heading "About the company" but not in list. Safer to put under "About the role"? However the instruction: "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." It doesn't forbid other headings, but gives examples. I'd include About Us as a heading maybe "About the company". But to be safe, I'll include an

  About Us

  as it's substantive. We need to output only HTML fragment, no markdown. Let's extract content. Who you'll work with paragraph: "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." That's prose. What you'll do: multiple paragraphs each starting with a bold phrase? Actually the text includes sentences each starting with a bold phrase? Let's list 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 That's a list. What you'll bring: bullet-like sentences: - 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: 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:" 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 About Us paragraph: "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." Compensation and Benefits: "Comp