OUR HIRING PROCESS:
- We will review your application against our job requirements. We do not employ machine learning technologies during this phase as we believe every human deserves attention from another human. We do not think machines can evaluate your application quite like our seasoned recruiting professionals—every person is unique. We promise to give your candidacy a fair and detailed assessment.
- We may then invite you to submit a video interview for the review of the hiring manager. This video interview is often followed by a test or short project that allows us to determine whether you will be a good fit for the team.
- At this point, we will invite you to interview with our hiring manager and/or the interview team. Please note: We do not conduct interviews via text message, Telegram, etc. and we never hire anyone into our organization without having met you face-to-face (or via Zoom). You will be invited to come to a live meeting or Zoom, where you will meet our INFUSE team.
- From there on, it’s decision time! If you are still excited to join INFUSE and we like you as much, we will have a conversation about your offer. We do not make offers without giving you the opportunity to speak with us live.
INFUSE is committed to complying with applicable data privacy and security laws and regulations. For more information, please see our Privacy Policy
INFUSE is looking for a Senior DevOps Engineer to own and evolve our AWS infrastructure, CI/CD pipelines, and observability stack. You will bridge cloud engineering and software development across our entire product suite, including production LLM products and legacy systems requiring modernization.
We need a proactive technical partner to lead our transition to EKS and GitHub Actions, enforce zero-trust security baselines, and mentor engineering teams along the way.
As part of our dynamic team, your responsibilities in this role will include:
- Design, build and run secure AWS infrastructure (EC2 with Docker Compose, EKS) with Terraform and Ansible; move suitable workloads from EC2 to EKS
- Build and maintain CI/CD in GitHub Actions; move remaining Jenkins jobs to GitHub Actions
- Keep new and existing services at our security baseline: Cloudflare proxy with WAF and rate limiting, origins open only to Cloudflare, SSM access, no public SSH, least-privilege IAM, secrets rotation, regular patching and rebuilds, no containers running as root
?token=pk_coDvT7FgQPeeYufxR7q_Wg&size=36&format=webp&retina=true&fallback=404){kind=logo}
