Cloud Engineer
Job Description
W2 Only
\n
\n
Job Title: Cloud Engineer
\n
Location: Indianapolis, IN 46225
\n
Contract Duration: 6 Months
\n
\n
KEY RESPONSIBILITIES:
\n
\n
Cloud Architecture & Infrastructure
\n
– Design and deploy cloud architectures across AWS and/or Azure that meet performance, security, availability, and cost-efficiency requirements for a diverse portfolio of enterprise and research applications.
\n
– Architect and implement cloud networking, compute, storage, and identity constructs with security built in from the outset — applying least-privilege principles, network segmentation, encryption, and defense-in-depth across every layer.
\n
– Evaluate and recommend cloud services, architectural patterns, and infrastructure approaches; build evidence-based adoption cases that account for engineering capability, operational cost, and long-term platform sustainability.
\n
Automation & Deployment
\n
– Implement and maintain infrastructure-as-code (IaC) frameworks using Terraform, CloudFormation, Ansible, or equivalent — making infrastructure provisioning repeatable, auditable, and developer-friendly.
\n
– Build and maintain CI/CD pipelines for cloud infrastructure and application deployments; ensure changes are tested, validated, and deployed safely with automated rollback capability.
\n
– Drive automation of operational tasks — patching, scaling, monitoring, alerting, and cost optimization — reducing manual intervention and improving platform reliability and response time.
\n
Security & Compliance
\n
– Ensure cloud environments comply with Client's security standards, regulatory requirements, and data governance policies; implement and maintain controls for identity management, Products management, audit logging, and encryption at rest and in transit.
\n
– Monitor cloud security posture continuously; identify and remediate misconfigurations, drift, and policy violations — integrating CSPM tooling into operational workflows for proactive compliance management.
\n
– Partner with Cybersecurity teams to align cloud platform security with enterprise threat models and applicable regulatory frameworks including GxP, 21 CFR Part 11, HIPAA, and SOX where relevant.
\n
Optimisation & Operational Excellence
\n
– Monitor cloud environments for performance, availability, and cost efficiency; proactively identify waste, right-size resources, and drive FinOps practices that deliver cloud value without unnecessary spend.
\n
– Contribute to platform engineering standards, reference architectures, and guardrails that simplify how development teams consume cloud infrastructure correctly and consistently.
\n
– Troubleshoot and resolve cloud infrastructure issues with urgency and precision; contribute to post-incident analysis and implement preventive improvements that reduce recurrence.
\n
\n
Quals--
\n
The Cloud Engineer is responsible for designing, implementing, and maintaining secure, scalable, and reliable cloud-based solutions. This role supports business objectives by optimizing cloud infrastructure, automating deployments, and ensuring compliance with security and performance standards.
\n
\n
BASIC QUALIFICATIONS:
\n
\n
– Bachelor's degree in Computer Science, Information Technology, or a related field — or equivalent professional experience.
\n
– 3+ years of hands-on cloud engineering experience in a production enterprise environment (AWS and/or Azure required).
\n
– Demonstrated proficiency with infrastructure-as-code tools (Terraform, CloudFormation, Ansible, or equivalent) and version control (Git).
\n
– Proficiency in scripting languages (Python, Bash, or equivalent) for automation and tooling development.
\n
– Strong understanding of cloud networking, virtualization, containerization (Docker, Kubernetes), and cloud security principles.
\n
– Experience with CI/CD pipelines and DevOps practices in a cloud-native context.
\n
\n
PREFERRED QUALIFICATIONS:
\n
\n
– AWS Certified Solutions Architect (Associate or Professional), AWS DevOps Engineer, or Azure Administrator/Architect certification strongly preferred.
\n
– Experience with FinOps practices and cloud cost optimization at enterprise scale.
\n
– Familiarity with monitoring and observability platforms (Prometheus, Grafana, Splunk, CloudWatch, Azure Monitor, or equivalent).
\n
– Experience in pharmaceutical, healthcare, life sciences, or other regulated industries — particularly with GxP, 21 CFR Part 11, or HIPAA cloud compliance requirements.
\n
– Experience with Kubernetes in production (EKS, AKS, or self-managed) including cluster operations and workload management.
\n
– Experience with Site Reliability Engineering or Agent Reliability Engineering
\n
– Background in working in a fast paced Agile environment
\n
– Background in cloud security architecture: IAM design, Products management, network security groups, and cloud-native security tooling[MB1.1].
\n
\n
WHAT YOU SHOULD BRING
\n
\n
– Deep, hands-on cloud expertise — you build and operate production cloud infrastructure, and you hold yourself accountable for its reliability, security, and cost.
\n
– Infrastructure-as-code as a default practice: you write Terraform or equivalent as naturally as you use the cloud console, and you understand why that matters for consistency, auditability, and scale.
\n
– A security-conscious engineering mindset — you design with least privilege, defense in depth, and compliance requirements built in from the start, not retrofitted under pressure.
\n
– A cost-conscious approach: you care about what cloud resources cost, you design systems that deliver value without unnecessary spend, and you proactively surface optimization opportunities.
\n
– The communication skills to work effectively with developers who need platform guidance and business stakeholders who need to understand cloud investment decisions — and to adjust your language for each.