Senior Harness Architect
Occupations:
Computer Systems Engineers/ArchitectsSoftware DevelopersDatabase ArchitectsComputer Systems AnalystsData Warehousing SpecialistsIndustries:
Continuing Care Retirement Communities and Assisted Living Facilities for the ElderlyComputing Infrastructure Providers, Data Processing, Web Hosting, and Related ServicesManagement, Scientific, and Technical Consulting ServicesComputer Systems Design and Related ServicesSoftware PublishersResponsibilitiesFinalize the Harness target-state architecture including multi-org topology, delegate strategy, identity federation, and integration with existing Elevance enterprise systemsLead architectural decision-making for golden pipeline patterns, OPA Policy-as-Code framework, and trusted supply chain controls (signing, SBOM, attestation)Guide the delivery pod on Harness best practices and ensure implementation reflects production-grade standardsAct as the senior technical authority for Harness-specific questions from the broader engagement teamRemove technical blockers in real time across both the onshore and offshore podsPartner with the Elevance Platform Engineering Lead and Enterprise Architect on architecture sign-offHand off a documented, defensible architecture and a hardened initial platform by end of Month 2Required experience5+ years of Harness platform experience including production deployments at enterprise scaleDeep familiarity with Harness CI, CD, STO, Policy-as-Code, and delegate architectureHands-on experience with golden pipeline patterns, template-by-reference inheritance, and OPA / RegoBackground in regulated enterprises (financial services or healthcare preferred)Demonstrated ability to operate as the senior architectural voice in client-facing settingsStrong written communication for architecture documentation and decision recordsPreferredPrior experience migrating from Bamboo, DAIR, or Jenkins to HarnessExperience with JFrog Artifactory, HashiCorp Vault, ArgoCD integrationsFamiliarity with HIPAA or HITRUST control frameworks in a CI/CD context