ServiceNow Solution Architect

We need to output HTML fragment with sections: About the role? The posting includes "Who you'll work with", "What you'll do", "What you'll bring", "Qualifications", "About Us", "Compensation and Benefits". Also maybe "Pay" section from compensation. We must use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. Do not put Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove EEO and Accommodations sections. Also remove "We will accept applicants until September 21, 2026..." maybe considered application instruction? It's a deadline; maybe considered application instruction? The instruction says remove application instructions. The deadline is an application instruction? Probably yes, remove. Also remove contact email for pay questions? Might be considered not needed. But we need to preserve substantive info: compensation ranges, benefits description. We need to include sections only when posting has real specific content. So we will have sections: About the role? Actually "Who you'll work with" could be considered "About the role" or maybe "About the team". But we have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content to these headings. The posting includes: "Who you'll work with" (maybe About the role). "What you'll do" (Responsibilities). "What you'll bring" (maybe Skills/Requirements). "Qualifications" (Qualifications). "About Us" (maybe About the role? but we already have). "Compensation and Benefits" (Pay and Benefits). No schedule info. We should not create sections with filler. So we will include sections where we have content. We need to use

  for each section heading. We need to use

  • for any list of duties/requirements/benefits. We need to preserve all substantive info. Let's extract content. Who you'll work with: paragraph about Slalom Technologists, passion, etc. That's prose. What you'll do: list of bullet-like sentences each starting with a verb. We can turn into
    • . What you'll bring: list of bullet-like sentences (starting with "You are an architect..." etc). Also includes "4+ years of consulting experience..." etc. That's more like requirements. Could be split into Requirements and Skills. Qualifications: list of bullet-like sentences (4+ years..., At least 3 full-lifecycle..., Required Certifications..., Preferred Certifications..., Architecture & Platform Expertise...). We'll need to turn into lists. About Us: paragraph about Slalom. Compensation and Benefits: paragraph about benefits, then pay ranges per location, plus discretionary bonus note. We need separate Pay and Benefits sections if content exists. The posting includes both compensation (pay ranges) and benefits (time off, parental leave, 401k, health, etc). So we can have

      Benefits

      with list of benefits, and

      Pay

      with pay ranges. We must not include placeholder text like "commensurate with experience". Not present. We must not include duplicated lines. We need to remove EEO and Accommodations, also remove "We are committed to pay transparency..." maybe keep? It's about compensation but not boilerplate? It's a statement about pay transparency; could be considered substantive? Might be okay to keep but it's more legal. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. That line is legal/compliance. Might be considered boilerplate. Safer to remove. Also remove "Please note, this recipient is not able to support recruitment inquiries beyond this purpose." That's also legal. Remove "EEO and Accommodations" section entirely. Also remove "We are committed to fair and equitable compensation practices." maybe borderline but it's a statement about compensation practices; could be considered substantive? Might be okay to keep but it's somewhat generic. I'd keep it as part of Compensation and Benefits? Might be considered boilerplate. I'd remove to be safe. We need to preserve all substantive info: benefits list, pay ranges. Let's extract benefits: "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/long-term disability. We also offer yearly $350 reimbursement account for any well-being-related expenses, as well as discounted home, auto, and pet insurance." We can turn into
      • each item. Pay: ranges per location: East Bay, San Francisco, Silicon Valley: Senior Consultant: $154,000–$189,000; Principal: $190,000–$232,000. San Diego, Los Angeles, Orange County, Seattle, Boston, Houston, New Jersey, New York City, Washington DC, Westchester: Senior Consultant: $141,000–$173,000; Principal: $174,000–$213,000. All other locations: Senior Consultant: $130,000–$159,000; Principal: $160,000–$195,000. Also note: individuals may be eligible for an annual discretionary bonus. Actual compensation will depend upon... The salary pay range is subject to change... We may keep that note as prose. Now sections: - About the role (maybe combine Who you'll work with and About Us? But we have separate headings. Could use "About the role" for Who you'll work with? Actually "Who you'll work with" describes team and culture. Could be "About the role". We'll put that under

        About the role

        with paragraph. - Responsibilities:

        Responsibilities

        with
        • from What you'll do. - Requirements: maybe combine What you'll bring and Qualifications? But we have separate headings Requirements and Qualifications. We could put "What you'll bring" under Requirements (skills/experience). And Qualifications under Qualifications (certifications etc). Let's do that. - Skills: maybe not needed if we covered. But we could put technical skills under Skills. However we have many technical skills in Qualifications (Architecture & Platform Expertise). Might be better to put them under Skills. But we need to avoid thin sections. Let's see: Qualifications section already includes certifications and experience. Skills could be separate for technical skills. But we have many technical skills in the "Architecture & Platform Expertise" bullet. Could be placed under Skills. We need to avoid creating sections with filler. If we put Skills, we need actual content. We have technical skills 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...; Depth in at least two of IT Service Management, IT Operations Management, and IT Asset Management...; 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. That's substantive. So we can have Skills section. Thus sections: About the role, Responsibilities, Requirements, Skills, Qualifications, Benefits, Pay. We must not repeat job title. Now we need to ensure we don't include boilerplate like "EEO and Accommodations". Already removed. Now produce HTML. Let's craft. About the role: paragraph from Who you'll work with. Responsibilities: list items from What you'll do. Requirements: list items from What you'll bring (the bullet points). Let's extract those bullet points: - 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 That's many items. We'll put as
          • . Skills: list from Architecture & Platform Expertise plus maybe communication and degree. Let's extract: - 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'll put as list. Qualifications: list from Qualifications section. Extract bullet points: - 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