ServiceNow Solution Architect
Slalom · Columbus, OH · 1 mo ago
Engineering$154k–$189k/yrFull-time
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 "Responsibilities" etc. We need to use for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections that have real specific content. We need to map content to appropriate headings.
We have:
- Who you'll work with: description of company culture, team. Could be "About the role"? Actually "Who you'll work with" is more about team context. Could be "About the role" or maybe "About the team". But allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use About the role for that intro.
- What you'll do: responsibilities. Use
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections that have real specific content. We need to map content to appropriate headings.
We have:
- Who you'll work with: description of company culture, team. Could be "About the role"? Actually "Who you'll work with" is more about team context. Could be "About the role" or maybe "About the team". But allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use About the role for that intro.
- What you'll do: responsibilities. Use Responsibilities
with - items.
- What you'll bring: qualifications/skills/experience. Could be Requirements or Qualifications. We have a separate "Qualifications:" section later. So we can split: "What you'll bring" could be Skills or Requirements. The posting also has a "Qualifications:" section with bullet points. So we can map:
- Skills: maybe "What you'll bring" (skills, experience). Use
Skills
with list.
- Qualifications: the later "Qualifications:" section with required certifications etc. Use Qualifications
.
- About Us: could be About the role? Already used. Could be omitted or maybe we can include as "About the role" already includes who you'll work with. The About Us is company description; could be omitted as boilerplate? It's not EEO/legal but it's about company. Might be considered relevant but not required. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About Us is not boilerplate; it's company description. Could keep as a section maybe "About the company"? Not in allowed headings. Could incorporate into About the role? Might be okay to omit as not required. But we need preserve ALL substantive information; do not invent or summarize away detail. So we should keep About Us content. Since allowed headings limited, we could use About the role
for both Who you'll work with and About Us? Might be mixing. Better to create a section with heading "About the role" for Who you'll work with, and maybe another section "About the company" but not allowed. However instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exclusive list. So we can use other headings if needed, but they gave examples. Probably safe to stick to those. Could treat About Us as "About the role" as well? Might be okay.
Compensation and Benefits: we have pay ranges and benefits. So we need Benefits and Pay sections. According to instruction: include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. So we need Benefits and Pay sections.
We have Pay: salary ranges per location. Provide that.
Benefits: list of benefits: meaningful time off, paid holidays, parental leave, 401(k) with match, health/dental/vision, adoption/fertility assistance, short/long-term disability, yearly $350 reimbursement, discounted home/auto/pet insurance.
We'll create Benefits
with - .
Pay
with maybe a describing ranges, or a
with location groups.
We also need to maybe include Schedule? Not present, so omit.
We need to preserve all substantive information: include details like "We will accept applicants until September 21, 2026, or until the position is filled." That's application instruction? It's a deadline; maybe considered application instruction. The instruction says remove application instructions. So we should remove that line. Also remove contact email for pay questions? That's also application instruction? Might be considered compensation info contact; but it's about pay range questions. Might be okay to keep? It's not boilerplate but it's a contact for compensation questions. Might be considered application instruction. Safer to remove.
Also remove EEO and Accommodations section (EEO). Remove that.
Also remove "We are committed to pay transparency..." paragraph? That's about compensation; maybe keep as part of Pay section? It's more about policy. Could keep as within Pay.
We need to not repeat job title as heading.
We need to not put Job ID/requisition numbers as headings (none present).
Now craft HTML.
Structure:
About the role
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.
But we duplicated About Us maybe separate. Could combine.
Better: About the role
with two paragraphs: first about team, second about company.
Now Responsibilities: list items from "What you'll do". Need to capture each bullet.
Let's extract bullet points 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 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 many items. We'll put them in - .
Now Skills: from "What you'll bring". Extract 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
We'll put these as
- under Skills.
Now Qualifications: from the "Qualifications:" section and also "Required Certifications:" etc. Need to capture all.
Let's extract:
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,
Skills
with list. - Qualifications: the later "Qualifications:" section with required certifications etc. UseQualifications
. - About Us: could be About the role? Already used. Could be omitted or maybe we can include as "About the role" already includes who you'll work with. The About Us is company description; could be omitted as boilerplate? It's not EEO/legal but it's about company. Might be considered relevant but not required. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About Us is not boilerplate; it's company description. Could keep as a section maybe "About the company"? Not in allowed headings. Could incorporate into About the role? Might be okay to omit as not required. But we need preserve ALL substantive information; do not invent or summarize away detail. So we should keep About Us content. Since allowed headings limited, we could useAbout the role
for both Who you'll work with and About Us? Might be mixing. Better to create a section with heading "About the role" for Who you'll work with, and maybe another section "About the company" but not allowed. However instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exclusive list. So we can use other headings if needed, but they gave examples. Probably safe to stick to those. Could treat About Us as "About the role" as well? Might be okay.
Compensation and Benefits: we have pay ranges and benefits. So we need Benefits and Pay sections. According to instruction: include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. So we need Benefits and Pay sections.
We have Pay: salary ranges per location. Provide that.
Benefits: list of benefits: meaningful time off, paid holidays, parental leave, 401(k) with match, health/dental/vision, adoption/fertility assistance, short/long-term disability, yearly $350 reimbursement, discounted home/auto/pet insurance.
We'll create Benefits
with - .
Pay
with maybe a describing ranges, or a
with location groups.
We also need to maybe include Schedule? Not present, so omit.
We need to preserve all substantive information: include details like "We will accept applicants until September 21, 2026, or until the position is filled." That's application instruction? It's a deadline; maybe considered application instruction. The instruction says remove application instructions. So we should remove that line. Also remove contact email for pay questions? That's also application instruction? Might be considered compensation info contact; but it's about pay range questions. Might be okay to keep? It's not boilerplate but it's a contact for compensation questions. Might be considered application instruction. Safer to remove.
Also remove EEO and Accommodations section (EEO). Remove that.
Also remove "We are committed to pay transparency..." paragraph? That's about compensation; maybe keep as part of Pay section? It's more about policy. Could keep as within Pay.
We need to not repeat job title as heading.
We need to not put Job ID/requisition numbers as headings (none present).
Now craft HTML.
Structure:
About the role
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.
But we duplicated About Us maybe separate. Could combine.
Better: About the role
with two paragraphs: first about team, second about company.
Now Responsibilities: list items from "What you'll do". Need to capture each bullet.
Let's extract bullet points 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 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 many items. We'll put them in - .
Now Skills: from "What you'll bring". Extract 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
We'll put these as
- under Skills.
Now Qualifications: from the "Qualifications:" section and also "Required Certifications:" etc. Need to capture all.
Let's extract:
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,
Pay
with maybe adescribing ranges, or a
- with location groups.
We also need to maybe include Schedule? Not present, so omit.
We need to preserve all substantive information: include details like "We will accept applicants until September 21, 2026, or until the position is filled." That's application instruction? It's a deadline; maybe considered application instruction. The instruction says remove application instructions. So we should remove that line. Also remove contact email for pay questions? That's also application instruction? Might be considered compensation info contact; but it's about pay range questions. Might be okay to keep? It's not boilerplate but it's a contact for compensation questions. Might be considered application instruction. Safer to remove.
Also remove EEO and Accommodations section (EEO). Remove that.
Also remove "We are committed to pay transparency..." paragraph? That's about compensation; maybe keep as part of Pay section? It's more about policy. Could keep as
- .
Now Skills: from "What you'll bring". Extract 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
We'll put these as
- under Skills. Now Qualifications: from the "Qualifications:" section and also "Required Certifications:" etc. Need to capture all. Let's extract: 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,
within Pay. We need to not repeat job title as heading. We need to not put Job ID/requisition numbers as headings (none present). Now craft HTML. Structure:
About the role
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.
But we duplicated About Us maybe separate. Could combine. Better: