Senior Cloud Platform Engineer (AIOps)
Credence
·Yesterday
- Salary
- $150k – $190k/yr
- Location
- McLean, Virginia
- Workplace
- Hybrid
- Type
- Full-time
- Department
- DOW AI/Tech
- Seniority
- Senior
- Experience
- 7+ years
- Education
- Bachelor
- Source
- Workable
Description
Join a team where innovation meets mission. Our AI, cloud, cyber, and modernization solutions save agencies thousands of hours, safeguard national security, and strengthen health and humanitarian missions worldwide. With more than 1,700+ team members, 1,500+ AI & data experts, and 100+ prime contracts, we deliver at scale and with purpose.
We've been recognized as a Top Workplace by The Washington Post for six consecutive years and named to the Inc. 5000 list of Fastest-Growing Private Companies in 13 of the past 14 years. Credence is a welcoming environment for those looking to grow and make a meaningful impact. We encourage employees to push boundaries and help solve critical, world-changing federal challenges.
Credence is seeking a Senior Cloud Platform Engineer (AIOps) to support secure AWS hosting environments for Department of War customers and to lead engineering of our AIOps / Operations Platform.
This is a senior, hands-on role that combines three things: solutioning customer requirements into working AWS designs, strong DevOps execution across IaC, CI/CD, and containers in a large multi-account GovCloud environment, and building the observability and AI-assisted triage capabilities that shorten time to detect and resolve. The ideal candidate leads technical conversations with customers and security teams, sets the patterns other engineers follow, and is a technical escalation point for the hosting team.
Responsibilities
Responsibilities include, but are not limited to:
- Technical solutioning
- Lead solutioning discussions with customer stakeholders, application teams, and cybersecurity; turn ambiguous requirements into a clear architecture, implementation plan, and level of effort.
- Produce technical designs and reference patterns that other engineers build from; present recommendations, tradeoffs, and risks to technical and nontechnical audiences and drive decisions to closure.
- Review designs and merge requests from other engineers; mentor mid-level and junior staff.
- DevOps and platform engineering
- Design, deploy, and operate secure AWS hosting solutions for dev, test, and production environments across a multi-account GovCloud landing zone.
- Build and maintain reusable Terraform and CloudFormation modules with remote state, versioning, and policy guardrails.
- Build and maintain GitLab CI/CD pipelines covering build, test, security scanning, deployment, and release, including pipeline templates teams reuse.
- Deploy, operate, and troubleshoot containerized workloads on Docker, Amazon ECS/Fargate, and Amazon EKS/Kubernetes.
- Write Python, Shell, and PowerShell automation; turn recurring operational issues into automation, platform capabilities, or standard deployment patterns.
- Troubleshoot complex issues across infrastructure, OS, networking, IAM, databases, pipelines, and containers; act as a senior technical escalation point.
- Work with cybersecurity and compliance to keep infrastructure and automation aligned with customer, federal, and organizational requirements.
- AIOps / Operations Platform
- Build and operate the observability data pipeline: CloudWatch, OS-, and infrastructure-level telemetry and logs collected into a centralized analytics store.
- Build the event correlation and AI-assisted triage layer on top of it, including anomaly detection, alert deduplication and enrichment, and root cause analysis workflows, integrating generative AI services such as Amazon Bedrock with appropriate guardrails.
- Own alarm and monitoring automation so new resources are covered automatically; define and report MTTD, MTTR, alert volume, and coverage.
- Contribute to FinOps capabilities built on platform data: tagging standards, cost allocation, and chargeback reporting.
- Operations
- Create and maintain runbooks, deployment procedures, and operational documentation.
- Participate in a rotating on-call schedule, typically approximately one week every four months.