Next Gen IT IncRemote
ServiceNow Business Analyst with APM & Data mapping
Remote
Contract
2 hours ago
$55 - $60 USD
Key skills
ETLServiceNowCommunication
About this role
ServiceNow Business Analyst
Remote
Exp: 10+yrs
Work Environment: REMOTE anywhere in US as long as they can work from 8-5 EST.
Interview Information: 1 round technical interview for 45 min over MS Teams w/ ServiceNow Team members
The most important need is someone who is strong with Data mapping, APM (Application Portfolio Management) and has experience with Enterprise Applications.
MUST HAVES:
Application Portfolio Management
Enterprise Applications
ServiceNow
Data Mapping enterprise Apps data into ServiceNow
Strong understanding of ServiceNow data model, tables, and workflows
Hands-on experience with ServiceNow data mapping, integrations, and data transformation
POSITION OVERVIEW:
ServiceNow Technical Business Analyst (Planview Integration Project)
We are seeking a skilled ServiceNow Technical Business Analyst to support the integration of Planview Enterprise applications into the ServiceNow platform. This role will focus heavily on data mapping, system integration, and requirements translation, ensuring seamless alignment between Planview and ServiceNow data models and workflows.
KEY RESPONSIBILITIES:
Lead data mapping activities between Planview Enterprise and ServiceNow, ensuring data accuracy, consistency, and integrity
Gather, analyze, and document business and technical requirements for integration efforts
Collaborate with stakeholders (IT, PMO, business teams) to define data structures, business rules, and workflows
Translate business needs into technical specifications and integration designs
Partner with developers to support API integrations, ETL processes, and data transformations
Validate and test data mappings, integrations, and system functionality
Troubleshoot and resolve data discrepancies across systems
Ensure alignment with ServiceNow best practices and governance standards
Support documentation, including mapping documents, process flows, and technical requirements
Application Portfolio Management
Enterprise Applications
ServiceNow
Data Mapping enterprise Apps data into ServiceNow
Strong understanding of ServiceNow data model, tables, and workflows
Hands-on experience with ServiceNow data mapping, integrations, and data transformation
POSITION OVERVIEW:
ServiceNow Technical Business Analyst (Planview Integration Project)
We are seeking a skilled ServiceNow Technical Business Analyst to support the integration of Planview Enterprise applications into the ServiceNow platform. This role will focus heavily on data mapping, system integration, and requirements translation, ensuring seamless alignment between Planview and ServiceNow data models and workflows.
KEY RESPONSIBILITIES:
Lead data mapping activities between Planview Enterprise and ServiceNow, ensuring data accuracy, consistency, and integrity
Gather, analyze, and document business and technical requirements for integration efforts
Collaborate with stakeholders (IT, PMO, business teams) to define data structures, business rules, and workflows
Translate business needs into technical specifications and integration designs
Partner with developers to support API integrations, ETL processes, and data transformations
Validate and test data mappings, integrations, and system functionality
Troubleshoot and resolve data discrepancies across systems
Ensure alignment with ServiceNow best practices and governance standards
Support documentation, including mapping documents, process flows, and technical requirements
Experience working for major Enterprise-Wide Org.
Experience working in a large ServiceNow environment
Strong understanding of ServiceNow data model, tables, and workflows
Hands-on experience with data mapping, integration, and data transformation
Familiarity with Planview Enterprise (or similar PPM tools)
Knowledge of REST/SOAP APIs, integration tools, and data exchange formats (JSON, XML)
Strong analytical, problem-solving, and communication skills
Ability to work cross-functionally with technical and non-technical stakeholders