
Lead Administrator - L1
- Pune, Maharashtra
- Permanent
- Full-time
- [Mandatory] Minimum 5 plus years of ServiceNow platform development experience
- [Mandatory] Create, maintain, and enhance Incident Management, Problem Management, Service Request Management, Service Catalog, Knowledge Management, Self-Service Portals
- [Mandatory] Create and configure Business Rules, UI Policies, UI Actions, Client Scripts, and ACLs including advanced scripting of each.
- [Mandatory] Perform advanced customizations including Business rules, Script Includes, Client Scripts
- [Mandatory] Experience designing, building and maintaining integration using REST, SOAP web services.
- [Mandatory] Knowledge on Event Management and monitoring tools
- [Mandatory] Experience work on ServiceNow CMDB, Mid server onboarding and troubleshooting, CSDM, Data loads, transform maps.
- [Mandatory] Experience in working with LDAP, AD, SSO, Email notifications.
- [Mandatory] Activate a plug-in, build reports, gauges, and homepages.
- [Mandatory] Set up Service Level Agreements (SLAs) and monitor SLA workflows.
- SME in ServiceNow system applications and custom applications.
- Knowledge on Server infrastructure, Network infrastructure
- Knowledge on ServiceNow platform modules likes HRSD, APM, PPM, GRC, ITAM
- Experience on troubleshooting production issues and lead team providing solutions.
- Perform platform upgrades, patching adhering to release management and software development best practices.
- Proven experience in up to 2 additional product lines outside of ITSM
- Responsible for standard configuration, user administration, security, workflow, data management and integrations.
- Aiding in translating business requirements into technical requirements
- Experience working in Agile/Scrum methodologies.
- ServiceNow Certified Application Developer (preferred)
SAP as service providerWe use the following session cookies, which are all required to enable the website to function:
- "route" is used for session stickiness
- "careerSiteCompanyId" is used to send the request to the correct data center
- "JSESSIONID" is placed on the visitor's device during the session so the server can identify the visitor
- "Load balancer cookie" (actual cookie name may vary) prevents a visitor from bouncing from one instance to another