ServiceNow Business Analyst

TechDigital Group; Charlotte (NC); On-site; USD 80,000 - 120,000; Full time

Job summary

A leading IT solutions firm is seeking an experienced ServiceNow Business Analyst who will act as a bridge between business stakeholders and technical teams. This role involves gathering and documenting business requirements, translating them into user stories, and managing stakeholder expectations. Candidates should have significant experience in ServiceNow, Agile methodologies, and strong communication skills. This position offers a chance to contribute to ServiceNow initiatives and collaborate with cross-functional teams.

Qualifications

• 6–10+ years of experience as a Business Analyst, with ServiceNow focus.
• Strong experience in Agile/Scrum delivery models.
• Excellent stakeholder communication and documentation skills.

Responsibilities

• Gather and document business requirements for ServiceNow initiatives.
• Translate requirements into user stories and functional specifications.
• Work with stakeholders to prioritize backlog items.

Skills

ServiceNow experience

Agile methodology

Stakeholder communication

Documentation skills

ITIL knowledge

Job description

The ServiceNow Business Analyst acts as a bridge between business stakeholders and technical teams.

Key Responsibilities

• Gather, analyze, and document business requirements for ServiceNow initiatives (BAU and enhancements)
• Translate requirements into clear user stories, acceptance criteria, and functional specifications
• Work with stakeholders to prioritize backlog items and manage scope expectations
• Participate in sprint planning, backlog grooming, demos, and retrospectives
• Support UAT planning, execution, defect triage, and sign‑off
• Maintain documentation: BRDs, user stories, process flows, SOPs, training materials

ServiceNow Technical & Platform Responsibilities

• Possess hands on understanding of ServiceNow platform architecture
• Understand how requirements map to:
  • Tables, fields, relationships
  • Forms, views, UI policies
  • Workflows vs Flow Designer
  • Business Rules, Client Scripts, Script Includes (conceptual level)
• Convert Business requirements to Functional Requirement documentation and collaborate with Dev/Lead Dev's for Technical Design documentation
• Design requirements that align with out of the box capabilities before customization
• Understand RITM → SCTASK lifecycle, fulfillment models, approvals, and SLAs
• Review and validate technical solution approaches proposed by developers
• Identify technical impacts, dependencies, and risks early in the lifecycle
• Ensure requirements are upgrade safe, scalable, and maintainable
• Support data related discussions (imports, CMDB impacts, integrations – conceptual)

Collaboration & Governance

• Act as a single point of contact between business and technical teams
• Work closely with:
  • ServiceNow Developers
  • Lead Developer / Architect
  • Product Owners / Scrum Master
• Help enforce BAU vs Project scope boundaries
• Participate in release planning and post release validation
• Support leadership with status updates, risks, and dependency tracking

Required Skills & Experience

• 6–10+ years of experience as a Business Analyst, with ServiceNow focus
• Strong experience in Agile / Scrum delivery models
• Excellent stakeholder communication and documentation skills
• Experience working with US based customers / stakeholders preferred
• 8–10+ years of ServiceNow Business Analyst experience
• Strong ITIL and ServiceNow platform knowledge
• Agile/Scrum delivery experience
• Strong stakeholder communication skills

ServiceNow Technical Knowledge (Must Have)

• Strong understanding of ServiceNow core platform concepts
• Functional knowledge of:
  • ITSM (Incident, Problem, Change)
  • Asset (HAM and SAM)
  • CMDB
  • Service Catalog & Request Fulfillment
  • Application Portfolio Management
  • Business Continuity Management
  • SecOps (SIR and VR)
  • Knowledge Management
  • CMDB (conceptual understanding)
• Ability to read and understand:
  • User stories vs technical tasks
  • Configuration vs customization
• Awareness of integrations (REST, MID Server – conceptual)
• Comfortable working with developers on technical feasibility discussions