Hiring - AWS DevOps w/ Harness - Lebanon NJ

0 views
Skip to first unread message

Bishwa Mahato

unread,
Jun 8, 2026, 2:44:39 PM (yesterday) Jun 8
to Bishwa Mahato

Title : AWS DevOps w/ Harness

Location : Lebanon NJ

 

Candidate should be willing to move to client location day 1

LinkedIn URL is mandatory

We are open for other locations candidates who are willing to relocate to NJ but local NJ based candidates will be given priority based on our past experience

 

Job Title - AWS DevOps w/ Harness

- 8 to 14+ years of overall experience in Infrastructure and Cloud services

- 8+ years of DevOps and CI/CD experience

- 1+ years of Harness tool experience

 

Harness CI/CD DevOps Engineer (Migration Factory) executes wave-based, repeatable Jenkins → Harness migrations using a factory operating model: Intake → Convert → Remediate → Validate → Cutover → Stabilize, while driving standardization through golden templates, enterprise integrations (SCM/artifacts/secrets), and controlled legacy CI/CD decommissioning.

Core Mission

• Industrialize CI/CD migration using waves, playbooks, reusable templates, and validation gates to reduce delivery risk and improve consistency.

• Leverage Harness Jenkins Migrator to scan/analyze pipelines, convert Jenkins pipelines to Harness format, and consolidate into reusable templates (where applicable), reducing manual effort and operational risk.

• Deliver controlled cutovers and stabilization while enabling governance elements (approvals, evidence capture) and controlled Jenkins decommission actions.

Key Responsibilities (Migration Factory Scope)

1) Migration Intake, Inventory & Segmentation

• Perform Jenkins estate discovery: inventory pipelines/jobs, Jenkins files, shared libraries, credentials usage, build agents, plugins; map dependencies and owners.

• Classify pipelines into complexity buckets (e.g., Quick Win/Simple, Standard/Medium, Complex) and build wave backlogs for migration execution.

• Run migrator assessment to produce a conversion readiness report and list of unsupported patterns (to drive remediation plan).

2) Platform Foundation for Migration

• Implement hands-on readiness required for factory execution: validate network allowlists/proxy/firewall, and ensure delegates/runners are deployed and healthy in target environments.

• Configure and validate connectors for SCM, artifact repositories/registries, cloud/K8s targets, and secret stores (Vault / secrets integration where applicable).

• Establish/maintain operational runbooks for delegate installation, access troubleshooting, and credential rotation.

3) Convert + Standardize via Golden Templates

• Use Harness Jenkins Migrator for bulk conversion and initial YAML generation where applicable.

• Refactor conversions to adopt golden templates (build/test/package/scan/deploy/notify patterns) and replace ad hoc logic with reusable templates/modules.

• Translate Jenkins constructs into Harness equivalents:

o shared libraries → templates/steps/stage templates

o Jenkins agents → delegates + build infrastructure model

o credentials → connectors + secrets manager

4) Remediate Gaps

• Replace unsupported Jenkins plugins / Groovy patterns with Harness-native steps or agreed scripts, and convert shared-library logic into reusable templates/modules.

• Integrate required enterprise toolchain hooks (e.g., artifact management, code quality gates, smoke tests), aligned to app team inputs.

5) Validate Shadow Mode & Parity Checks

• Execute parallel runs (Jenkins + Harness) for validation; compare outputs (artifacts, test reports, scan outputs) and complete acceptance testing checkpoints.

• Produce a validation evidence package (shadow run results + parity checks) to support cutover readiness and audit needs.

6) Cutover & Stabilize (Hypercare within the factory cycle)

• Execute cutover by switching triggers/webhooks/notifications to Harness and keeping Jenkins as rollback for a defined period when required by the plan.

• Stabilize builds by monitoring failures, tuning caching, adjusting runner sizing, and addressing recurring pipeline issues; capture improvements back into templates/playbooks.

• Run wave retrospectives to update templates, playbooks, and known-issues guidance for the next wave.

7) Controlled Jenkins Decommission (Factory Exit)

• Support controlled Jenkins reduction activities as defined by the migration plan:

o Freeze new pipeline creation in Jenkins (new work lands in Harness)

o Progressive shutdown (disable triggers → jobs → agents; keep read-only for audit retention)

o Plugin & credential cleanup (remove unused creds, rotate secrets, lock down access)

o Archive evidence (export build history/logs as required)

o Terminate Jenkins infrastructure and reclaim resources

Factory Delivery Model Alignment (Pods & Interfaces)

• Work within a pod-based migration factory model that includes:

o Platform Pod: templates, delegate strategy/connectors, enterprise integration, org/account governance, policy enforcement, service catalog enablement

o Migration Pod: Jenkins inventory & dependency analysis, wave planning, pipeline migration/validation, cutover support, runbooks/handover, hypercare, and decommission support

Required Skills

Harness CI/CD Execution

• Hands-on ability to build and migrate CI/CD pipelines and enforce reuse through templates and versioning.

• Experience deploying and operating delegates/runners, and troubleshooting connectivity/toolchain access.

Migration Engineering (Jenkins → Harness)

• Strong experience analyzing Jenkins pipelines (Jenkins-files, shared libraries, agents, plugins, credentials) and translating them to Harness equivalents.

• Familiarity with AI-assisted conversion using Harness Jenkins Migrator and handling unsupported patterns through remediation/refactoring.

Validation & Cutover Discipline

• Experience with parallel/shadow runs, artifact/output comparison, readiness checkpoints, and cutover + stabilization practices.

Enterprise Integrations & Secrets

• Integrations with SCM, artifact repositories/registries, secrets management, and environment targets (e.g., Kubernetes/cloud) using connectors and least-privilege principles.

Deliverables (Expected Outputs)

• Jenkins inventory + complexity segmentation + “unsupported patterns” list and wave plan inputs.

• Migrated Harness pipelines (YAML) with golden template adoption and versioned reusable components.

• Validation evidence package (parallel run results + parity checks) and cutover readiness artifacts.

• Runbooks/SOPs/troubleshooting guides and handover materials for operations teams.

• Jenkins decommission checklist execution support (freeze, cleanup, archive evidence, teardown).

 

End-to-end design of:

• CI pipelines (build/test)

• CD pipelines (deploy/approve/release)

• Ability to define enterprise pipeline standards

 

Strong expertise in:

• Harness CI + CD modules

• Pipeline templates, RBAC, delegates

• Policy as Code & approvals

Define:

• “Golden” pipeline templates

• Naming, branching, approvals, security gates

• Enforce consistency across apps

Strong integration experience with:

• GitHub / GitLab (SCM)

• Artifact repo (JFrog/Nexus)

• Container registry

• ITSM (ServiceNow)

Hands-on with:

• EKS/Kubernetes

• Helm / deployment strategies (blue-green, canary)

• Harness

Experience with:

• Secrets management (Vault / AWS Secrets / CyberArk)

• SAST / DAST / vulnerability scanning

• Handle plugins, shared libraries, dependencies

Strong in:

• Terraform (mandatory)

• Enable infra provisioning as part of pipeline

Build:

• Reusable pipeline templates

• Automation playbooks

• Self-service CI/CD frameworks

Optimize:

• Build times

• Failure rates

• Pipeline efficiency

Expertise in:

• “Build once, deploy everywhere”

• Artifact promotion across environments

Debug:

• Pipeline failures

• Deployment issues

• Integration gaps

 

Skills: AWS DevOps and Automation

Experience Required: 8-10

 

Reply all
Reply to author
Forward
0 new messages