Jobs · Information Technology

ServiceNow Technical Consultant-ITSM

Astrica · United States · 1 mo ago
RemoteRemoteInformation TechnologyContract
We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. No job title heading. No Job ID. Remove boilerplate like EEO, etc. Also remove "No 3rd party vendor submissions at this time*" line. Also remove "Astrica ServiceNow Technical Consultants bring their understanding..." maybe part of description but we need to keep substantive info. We need to parse the posting. Let's extract sections: - About the role: The paragraph after title: "ServiceNow Technical Consultant -ITSM and Learning Management Astrica ServiceNow Technical Consultants bring their understanding of system and software architecture to implement solutions on the ServiceNow platform for our customers. They lead and prescribe clients to best practice and collaborate with team members to achieve project goals. Their ServiceNow skills are kept on the bleeding-edge, they innovate IP on the platform, and serve as technical subject matter experts to clients and teammates." That's about the role. - Responsibilities: The "What you’ll do:" bullet list (though not bullet but sentences). We'll convert to
  • . List items: - Dazzle clients! Participate in all technical aspects of delivering complex customer solutions on the ServiceNow platform, advising clients on best practice to create lasting value and enhanced experiences. - Build Stuff! Contribute on multiple Agile engagements, utilizing the Astrica methodology and tools to enhance project efficiency and quality. - Influence! Define technical and design approaches, lead scrums, and advise technical consulting resources on development and configuration activities. - Drive quality! Estimate time and effort for technical resources and proactively communicate progress and forecast changes to the Engagement Manager. Own the technical quality on customer projects, participate in code reviews, and oversee Go-Live planning efforts. - Assist with discovery workshops and collaborate closely with Business Process Consultants to define customer requirements. - Participate in internal knowledge sharing, coaching, and collaboration activities and initiatives. We could split each sentence as separate li. - Requirements: The "What you bring:" list. List items: - 6+ years of ServiceNow platform experience with a comprehensive understanding of the product suite of ITSM and Knowledge Management. - 10+ years of related client-facing professional consulting experience, preferably with ServiceNow. - Demonstrated experience with the Agile methodology, leading sprint planning efforts, reviewing stories against business requirements, splitting epics, and ordering development logically in a virtual environment. - Experience assigning estimates for units of work (stories, defects, documentation, etc.) and coaching resources on the technical development and configuration against defined user stories. - Ability to lead client facing workshops and meetings and conduct calls with customers independently or in support of business process/requirements gathering efforts. - Experience with supervising and inspecting code migrations between instances, as well as providing feedback to technical resources on approaches to remediate assigned defects. - A passion for advising and guiding customers on how to get the most out of the product and for learning the latest product features. - A calm, adaptable, and driven approach to both client engagements and internal efforts/teams. - A love of working in a fast-paced, collaborative, and adaptive environment with smart and fun people. - Extra Awesome: Could be considered Skills or Additional Qualifications. Might be a separate "Skills" section. Skills: "Experience implementing the Employee Workflows of ServiceNow (HRSD, WSD, and Legal Service Delivery) Experience in one or more of the following: web technologies (HTML, CSS, AngularJS), Integrations (using REST, SOAP, Integration Hub, LDAP, SSO), and custom (scoped) application development. CSA, CAD, and ITSM (CIS) certifications, plus CIS in 3+ additional process areas outside of ITSM (ITOM, HR, CSM, UX, ITAM, or ITBM)." We can treat as Skills. - Where You’ll Work: remote-first team description. Could be "Work Location" or "Schedule"? Not exactly schedule. Could be "Work Environment". But we only have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Qualifications maybe similar to Requirements. We have Requirements already; we could put Qualifications as maybe certifications etc. But we already have Skills includes certifications. Could combine. Better: Use sections: About the role, Responsibilities, Requirements, Skills, Benefits, Work Environment (maybe not in list). But instructions say use those headings only; we can omit others. So we should only include headings that match list and have content. Thus we can have:

    About the role

    ...

    Responsibilities

      ...

    Requirements

      ...

    Skills

      ...
    (maybe include certifications etc.)

    Benefits

      ...
    (from Perks & Benefits) Pay: Not specified explicitly; just "Competitive pay that reflects your skills and certifications". That's vague but maybe we can include Pay section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Competitive pay that reflects your skills and certifications". That's somewhat specific? It's not a number but it's a statement about pay. Could include Pay section with that sentence. However they said avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "Competitive pay that reflects your skills and certifications" is somewhat vague but not exactly filler; it's a statement. Might be okay to include Pay section with that sentence. Schedule: Not specified; they mention remote-first, occasional travel up to 10%, flexible time off. That's more about work environment, not schedule. No explicit schedule like "full-time", "part-time". So we should not create Schedule section. Benefits: We have details: Unlimited vacation + flexible time off, Health, dental, vision, and 401(k) coverage, Career development support and learning incentives, Performance bonuses and annual reviews. Also "Competitive pay" maybe separate. Thus Benefits section. Work environment maybe not needed. We'll also include a short paragraph for "Where You’ll Work" maybe as part of About the role? Could be separate but not in allowed headings. Could incorporate into About the role or maybe as a separate

    after About the role but not a heading. The instruction: output only HTML fragment; we can include paragraphs not under headings. Probably okay. We must not include boilerplate like EEO etc. Remove that. Now craft HTML. Let's write:

    About the role

    ServiceNow Technical Consultant - ITSM and Learning Management. Astrica ServiceNow Technical Consultants bring their understanding of system and software architecture to implement solutions on the ServiceNow platform for customers. They lead and prescribe clients to best practice, collaborate with team members to achieve project goals, keep their ServiceNow skills on the bleeding‑edge, innovate IP on the platform, and serve as technical subject matter experts to clients and teammates.

    Responsibilities

    • Dazzle clients! Participate in all technical aspects of delivering complex customer solutions on the ServiceNow platform, advising clients on best practice to create lasting value and enhanced experiences.
    • Build Stuff! Contribute on multiple Agile engagements, utilizing the Astrica methodology and tools to enhance project efficiency and quality.
    • Influence! Define technical and design approaches, lead scrums, and advise technical consulting resources on development and configuration activities.
    • Drive quality! Estimate time and effort for technical resources and proactively communicate progress and forecast changes to the Engagement Manager. Own the technical quality on customer projects, participate in code reviews, and oversee Go‑Live planning efforts.
    • Assist with discovery workshops and collaborate closely with Business Process Consultants to define customer requirements.
    • Participate in internal knowledge sharing, coaching, and collaboration activities and initiatives.

    Requirements

    • 6+ years of ServiceNow platform experience with a comprehensive understanding of the product suite of ITSM and Knowledge Management.
    • 10+ years of related client‑facing professional consulting experience, preferably with ServiceNow.
    • Demonstrated experience with the Agile methodology, leading sprint planning efforts, reviewing stories against business requirements, splitting epics, and ordering development logically in a virtual environment.
    • Experience assigning estimates for units of work (stories, defects, documentation, etc.) and coaching resources on the technical development and configuration against defined user stories.
    • Ability to lead client‑facing workshops and meetings and conduct calls with customers independently or in support of business process/requirements gathering efforts.
    • Experience with supervising and inspecting code migrations between instances, as well as providing feedback to technical resources on approaches to remediate assigned defects.
    • A passion for advising and guiding customers on how to get the most out of the product and for learning the latest product features.
    • A calm, adaptable, and driven approach to both client engagements and internal efforts/teams.
    • A love of working in a fast‑paced, collaborative, and adaptive environment with smart and fun people.

    Skills

    • Experience implementing the Employee Workflows of ServiceNow (HRSD, WSD, and Legal Service Delivery).
    • Experience in one or more of the following: web technologies (HTML, CSS, AngularJS), integrations (using REST, SOAP, Integration Hub, LDAP, SSO), and custom (scoped) application development.
    • CSA, CAD, and ITSM (CIS) certifications, plus CIS in 3+ additional process areas outside of ITSM (ITOM, HR, CSM, UX, ITAM, or ITBM).

    Benefits

    • Competitive pay that reflects your skills and certifications.
    • Performance bonuses and annual reviews that celebrate growth.
    • Unlimited vacation + flexible time off.
    • Health, dental, vision, and 401(k) coverage.
    • Career development support and learning incentives to keep you sharp.
    We might also include Pay section separate? Already included in Benefits as first item. Could separate Pay but it's okay. We should not include Schedule. Check for any leftover boilerplate: removed EEO line, removed "No 3rd party vendor submissions at this time*". Also removed "Where You’ll Work" and "What the Work Looks Like" paragraphs. Might be okay to keep some of that as prose under About the role? Could incorporate remote-first description maybe as a paragraph after About the role but not under heading. The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we should keep the remote-first description etc. It's substantive. Where to put? Could add a

    after About the role before Responsibilities, maybe as part of About the role but we already have a paragraph. Could extend that paragraph to include remote-first details. Let's incorporate: "We’re a remote‑first team, which means you can do your best work from wherever you’re happiest and most productive. Every now and then, we may ask you to join us on‑site with a client—but those moments are the exception, not the rule. Flexibility is built in, because we know life doesn’t fit neatly into a 9–5. Most of your day will be spent collaborating online, building smart solutions, and occasionally traveling (up to 10%) if a project needs you in person. Otherwise, it’s you, your laptop, and your favorite coffee mug." Add that as a separate

    after About the role. Thus final HTML:

    About the role

Similar jobs