AWS DevOps Architect

Job title : AWS DevOps Architect

Job Location : New Jersey, United States

Must Have Technical/Functional Skills

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.

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

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 to compare outputs of acceptance testing checkpoints.
• Produce validation evidence package (shadow run results + parity checks) to support cutover readiness and audit.

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:
• Freeze new pipeline creation in Jenkins (new work lands in Harness)
• Progressive shutdown (disable triggers → jobs → agents; keep read-only for audit retention)
• Plugin & credential cleanup (remove unused creds, rotate secrets, lock down access)
• Archive evidence (export build history/logs as required)
• Terminate Jenkins infrastructure and reclaim resources

8) Factory Delivery Model Alignment (Pods & Interfaces)

• Work within a pod-based migration factory model that includes:
• Platform Pod: templates, delegate strategy/connectors, enterprise integration, org/account governance, policy enforcement, service catalog enablement
• Migration Pod: Jenkins inventory & dependency analysis, wave planning, pipeline migration/validation, cutover support, runbooks/handover, hyper care, and decommission support