DevOps Engineer
vtech solutionSan Jose (CA)
About the role
Job Summary:
The DevOps / Cloud Engineer is responsible for owning and managing cloud accounts, primarily Azure, and ensuring robust infrastructure through Infrastructure as Code (IaC) and deployment automation. This role focuses on maintaining uptime, monitoring, backup, disaster recovery, and continuous integration and delivery (CI/CD) in a steady-state operational environment, especially during seasonal peak loads.
Responsibilities:
- Own and manage existing or new Azure cloud accounts.
- Develop and maintain Infrastructure as Code using Terraform or Bicep.
- Automate deployment processes and CI/CD pipelines.
- Ensure system uptime and reliability, particularly during peak seasonal demands.
- Implement monitoring, backup, and disaster recovery strategies.
- Execute restore and failover procedures as needed.
- Collaborate with other teams during patching and operational tasks.
- Manage container orchestration in production environments.
- Required Skills & Certifications:
- Bachelor's degree or equivalent experience.8+ years of experience in cloud infrastructure and operations.
- Proficient in Infrastructure as Code delivery using Terraform or Bicep.
- Experience with container orchestration in production.
- Strong knowledge of CI/CD pipelines and deployment automation.
- Proven ability to execute restore or failover operations.
- Preferred Skills & Certifications:
- Azure Administrator Associate certification.
- DevOps Engineer Expert certification.
- Certified Kubernetes Administrator (CKA).HashiCorp Terraform Associate certification.
- Special Considerations:
- Role involves steady-state operational responsibilities rather than project-based work.
- Must handle peak-load operations during seasonal periods, such as rainy winter seasons.
- May require coordination with external teams for direct patching activities.
Scheduling:
Work schedule aligned with operational demands, including seasonal peak periods.
May require availability for on-call or emergency restore/failover operations.
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.