ServiceNow - ServiceNow IT Operations Management (ITOM) - Senior - Tech Cons - Open Location
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate like EEO, legal, navigation, cookie, application instructions, etc. Must preserve all substantive info. We need to parse the posting. Let's extract sections: - Location: Anywhere in Country (maybe not needed? It's location info; could be part of a short paragraph. Not a heading. Could be included in a
maybe. - Intro paragraph: "At EY, we’re all in to shape your future with confidence..." etc. That's about the role/company. Could be "About the role" or "About EY". We'll decide. - "The opportunity" paragraph: describes role. Could be part of About the role. - "Your Key Responsibilities As a Senior Application Designer and Developer, you will play a pivotal role..." then bullet list (though not bullet but colon separated). We'll need to convert to
- .
- "Skills And Attributes For Success" paragraph then bullet list of abilities.
- "To qualify for the role, you must have" list of qualifications.
- "Ideally, you’ll also have" additional preferred qualifications.
- "What We Look For" paragraph.
- "What We Offer You At EY..." includes salary range and benefits.
- Then "Are you ready..." etc is call to action (application instruction) - should be removed.
- Then legal EEO etc - remove.
Thus sections:
About the role (intro + opportunity). Could be combined.
Responsibilities (Your Key Responsibilities).
Skills (Skills And Attributes For Success) maybe combine with Qualifications? But we have separate sections: Requirements (maybe qualifications), Skills, Benefits, Pay.
We have qualifications: "To qualify for the role, you must have ..." plus "Ideally, you’ll also have ..." Could be Requirements (mandatory) and Preferred Qualifications.
But guidelines: Use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They gave a list but we can choose which to include. They said: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those exact headings if appropriate. We need to avoid filler like "commensurate with experience". Not present. We need to include Pay section only if posting states salary range. It does: salary ranges for different locations. So we include Pay. Benefits: posting mentions "Total Rewards package includes medical and dental coverage, pension and 401(k) plans, and a wide range of paid time off options." That's benefits. Schedule: Not mentioned explicitly (no mention of work schedule). So we should not include Schedule. We may also include "Location" as a paragraph but not a heading. We need to preserve all substantive info: location, intro, opportunity, responsibilities, skills/attributes, qualifications (mandatory and ideal), what we look for, what we offer (benefits + pay). Also maybe "What We Look For" could be part of Skills or separate? Could be a short paragraph about desired traits; we could include under Skills or as its own section like "What We Look For". But headings list does not include that; we could incorporate into Skills or maybe a separate "Attributes". But better to follow guidance: use headings from list; we can have Skills covering both skills and attributes. The "What We Look For" paragraph is about curiosity, learning, etc. Could be placed under Skills. Thus final HTML:
Location: Anywhere in Country
About the role
At EY, we’re all in to shape your future with confidence. We’ll help you succeed in a globally connected powerhouse of diverse teams and take your career wherever you want it to go. Join EY and help to build a better working world. In the digital economy, it takes more than good ideas and strong leadership to thrive. Upgrading outdated processes, systems and information is vital – but can be a risky investment in such a rapidly changing environment. That’s why some of the most prestigious businesses worldwide look to us for authoritative, agile, and efficient solutions for business decision-making. As a ServiceNow Senior Consultant you’ll play a leading role in that mission, providing the competitive edge our clients need to overcome some of the biggest creative and technical challenges around. The opportunity You’ll lead ServiceNow Transformation teams in a rapidly growing area of the business. It’s a client visible role, in which you’ll have opportunities to showcase your ability to not only motivate and develop your team but also establish and maintain new client relationships. You will have an opportunity to grow your consulting and team leadership skills, as well build relationships and obtain experiences that will define your career. In this role, you will identify and define user/customer requirements, focusing on developing user interfaces (UI) across various platforms such as mobile, web, and tablets. You will be responsible for creating software components and services that interact seamlessly with upstream and downstream components, ensuring that business requirements are met through effective coding and programming.
Responsibilities
- Collaborating with clients to gather and analyze requirements, ensuring that the final product meets their needs.
- Designing and developing user interfaces that are not only functional but also enhance user experience.
- Writing clean, maintainable code and creating specifications that support business objectives.
- Regular travel may be required to meet with clients, providing you with the opportunity to engage directly with stakeholders.
Skills
- Act as a workstream lead across all aspects of a ServiceNow ITOM/CMDB project and solution delivery including but not limited to design, configuration/development, testing and deployment phases
- Ability to manage and mentor a multi-disciplinary team of 3-5 resources including offshore resources (e.g., consultants, developers, and testers)
- Provide guidance and industry leading practice expertise for ServiceNow ITOM/CMDB process implementations, including how specific business objectives can be met through process and technology transformation
- Ability to analyze a company’s people, process, and technology capabilities, provide leading practice recommendations and contribute insights to strategic roadmaps
- Ability to advise on the connectivity of the CMDB and IT Operations Management (ITOM) to ITSM processes
- Ability to lead client process and design sessions and facilitate requirements workshops with functional and/or business process area subject matter resources
- Experience in waterfall and agile delivery models – including supporting management activities such as planning, status reporting, budgets and risk and issue logs
- Ability to create high quality deliverables and project artifacts
- Excellent soft skills – communication (written/verbal), adaptability, problem solving, teamwork, relationship building, dependability, and organization
- Experience leading teams and supervising others
Requirements
- A bachelor's degree, preferably in Computer Science, Information Systems Management, Engineering or similar discipline
- Typically, no less than 2 - 4 years relevant ServiceNow ITOM/CMDB project experience.
- ServiceNow Certified Systems Administrator (CSA) or Certified Application Developer (CAD)
- Minimum of 2 of the following ServiceNow certifications:
- ServiceNow Certified Implementation Specialist – Data Foundations
- ServiceNow Certified Implementation Specialist – Discovery
- ServiceNow Certified Implementation Specialist – Event Management
- ServiceNow Certified Implementation Specialist – Service Mapping
- 3+ years of Big 4 or equivalent consulting experience
- A driver’s license valid in the U.S.
- Ability to travel to meet client needs
Preferred Qualifications
- ServiceNow Certified Implementation Specialist – ITSM or HAM or SAM
- Performance analytics and reporting experience – certifications are a plus
- Experience in ServiceNow’s AI solutions (Now Assist, Agentic, AI Control Tower)
What We Look For
We seek individuals who are not only technically proficient but also possess a strong sense of curiosity and a desire to learn. Top performers are those who can navigate complex challenges with ease, communicate effectively, and build meaningful relationships with clients and colleagues alike.
Benefits
In addition, our Total Rewards package includes medical and dental coverage, pension and 401(k) plans, and a wide range of paid time off options.
Pay
The salary range for this job is: New York City, Boston, and Washington DC Metro Areas, Washington State, and Southern California offices – $122,900 to $204,900; Bay Area California offices – $128,100 to $213,400; All other offices locations in the US, including Sacramento – $102,500 to $187,900. Individual salaries within these ranges are determined through a wide variety of factors including but not limited to education, experience, knowledge, skills and geography.
We must ensure no boilerplate like "Are you ready..." etc removed. Also removed EEO etc. Check that we didn't repeat job title. Good. We usedfor each section. We used
for prose. We used
- for lists.
We included location as a
before sections. We included "What We Look For" as a section though not in the list but it's substantive; guidelines said use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't forbid other headings but said use those for section headings. Might be safer to incorporate that paragraph into Skills or About the role. But it's okay to have extra heading? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say you cannot use other headings, but implies you should use those for sections. Safer to merge "What We Look For" into Skills or About the role. Let's merge into Skills section as a paragraph before the list. Thus adjust: after Skills heading, we can have a paragraph describing what we look for, then the list. Let's restructure:
Skills
We seek individuals who are not only technically proficient but also possess a strong sense of curiosity and a desire to learn. Top performers are those who can navigate complex challenges with ease, communicate effectively, and build meaningful relationships with clients and colleagues alike.
- ...