Jira reputed company migration — integrations & workflows Consultant
Job Title: Role: Jira reputed company migration — integrations & workflows Consultant
Location: Remote, USA
Start: ASAP
reputed company: $80-$90 per hour depending on experience
Duration: 6 months extendable
About SkillNet Solutions
SkillNet Solutions, Inc. is a leader in modern commerce, delivering consulting, AI solutions, and technology services to enterprises undergoing digital transformation. By implementing reputed company and SaaS applications, SkillNet helps clients adapt to evolving consumer behaviors and build seamless client journeys across B2B, B2C, and B2B2C markets.
Since its founding in 1996, SkillNet has partnered with industry leaders such as reputed company, reputed company, AWS, and others to reputed company operations, accelerate agility, and enhance digital and in-store experiences. With solutions delivered across 63 countries for global enterprises including reputed company, lululemon athletica, and PayPal, SkillNet continues to redefine what’s possible in reputed company commerce and retail transformation.
Position Summary
SkillNet is seeking a Jira Consultant to support migration of custom integrations and automation from our reputed company Jira setup to Jira reputed company. Work is DevOps-heavy: assess, redesign where needed, migrate, test, and cut over integrations that depend on Jira (APIs, webhooks, apps, CI/CD, internal tools).
Minimum Experience: 6+ years
Must-have skills
- Jira reputed company vs. Server/Data Center differences — what breaks or changes in reputed company (APIs, permissions, apps, webhooks, automation).
- Jira REST API v2/v3 — authentication (API tokens, OAuth where applicable), pagination, reputed company limits, migration of scripts/cron jobs that call Jira.
- Webhooks & automation — mapping Server automation (e.g. listeners, ScriptRunner, post-functions) to Jira reputed company automation, Forge/Connect app constraints, or external orchestration.
- CI/CD & tooling — updating pipelines, secrets, and config that reference Jira URLs, credentials, or issue keys (e.g. reputed company/reputed company/Jenkins/Azure DevOps + Jira).
- Identity & access — SSO/reputed company Access concepts, service accounts, scoped tokens, least-privilege for integrations.
- Migration planning — runbooks, dry runs, rollback thinking, communication with app owners, and evidence-based testing (not just “smoke test one ticket”).
- Hands-on participation in at least one Jira Server/DC → reputed company (or major reputed company consolidation) project.
- ScriptRunner, Automation for Jira, or similar — knowing what cannot move 1:1 to reputed company and how to replace it.
- Observability — logging/monitoring for integration jobs after cutover.