Highlights
Implement hands-on readiness required for factory execution: validate network allowlists/proxy/firewall, and ensure delegates/runners are deployed and healthy in target environments. § Expertise on Enterprise Integrations & Secrets - integrations with SCM, artifact repositories/registries, secrets management, and environment targets (e.g., Kubernetes/cloud) using connectors and least-privilege principles.
Numbers & Facts
| Location | Lebanon, NJ |
| Industry | Computer/IT Services |
| Company Size | 500 to 999 employees |
| Year Founded | 1990 |
| Website | http://q1tech.com/ |
Description
Job Title: AWS DevOps Architect
Duration- Fulltime Permanent
Location: Lebanon NJ (Onsite from Day 1)
Job Description:
DevOps Architect
Mandate
Harness, AWS DevOps, CI/CD, Jenkins, AWS EKS, Terraform
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:
o Freeze new pipeline creation in Jenkins (new work lands in Harness)
o Progressive shutdown (disable tri ggers → 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
8) 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, hyper care, 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.
§ 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.
§ Experience with parallel/shadow runs, artifact/output comparison, readiness checkpoints, and cutover + stabilization practices.
§ Expertise on Enterprise Integrations & Secrets - integrations with SCM, artifact repositories/registries, secrets management, and environment targets (e.g., Kubernetes/cloud) using connectors and least-privilege principles.
§ End-to-end design of CI pipelines (build/test) and CD pipelines (deploy/approve/release)
§ Ability to define enterprise pipeline standards with strong expertise in Harness CI + CD modules, Pipeline templates, RBAC, delegates and Policy as Code & approvals
§ Integration experience of 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)
§ Ability to enable infra provisioning as part of pipeline
§ Ability to Build: Reusable pipeline templates, Automation playbooks, Self-service CI/CD frameworks
§ Ability to Optimize: Build times, Failure rates, Pipeline efficiency
§ Expertise in: "Build once, deploy everywhere” and Artifact promotion across environments
§ Ability to Debug: Pipeline failures, Deployment issues and Integration gaps.
Duration- Fulltime Permanent
Location: Lebanon NJ (Onsite from Day 1)
Job Description:
DevOps Architect
Mandate
Harness, AWS DevOps, CI/CD, Jenkins, AWS EKS, Terraform
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:
o Freeze new pipeline creation in Jenkins (new work lands in Harness)
o Progressive shutdown (disable tri ggers → 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
8) 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, hyper care, 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.
§ 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.
§ Experience with parallel/shadow runs, artifact/output comparison, readiness checkpoints, and cutover + stabilization practices.
§ Expertise on Enterprise Integrations & Secrets - integrations with SCM, artifact repositories/registries, secrets management, and environment targets (e.g., Kubernetes/cloud) using connectors and least-privilege principles.
§ End-to-end design of CI pipelines (build/test) and CD pipelines (deploy/approve/release)
§ Ability to define enterprise pipeline standards with strong expertise in Harness CI + CD modules, Pipeline templates, RBAC, delegates and Policy as Code & approvals
§ Integration experience of 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)
§ Ability to enable infra provisioning as part of pipeline
§ Ability to Build: Reusable pipeline templates, Automation playbooks, Self-service CI/CD frameworks
§ Ability to Optimize: Build times, Failure rates, Pipeline efficiency
§ Expertise in: "Build once, deploy everywhere” and Artifact promotion across environments
§ Ability to Debug: Pipeline failures, Deployment issues and Integration gaps.
About Company
Q1 consists of experienced and recognized experts providing the capability to respond to market demand in order to provide professional services for our clients including Enterprise software implementations, application integration and technical / functional support.
Q1 has steadily grown into a Quality IT services and solutions organization with the average experience of our team being over 10 years. We have continuously met or exceeded client expectations by delivering professional services and project implementations on time and under budget to help clients truly recognize return on investment.
