Senior Engineer, Cloud Operations (Contract Position)

Location: Remote from Ukraine

Company

A product company developing an identity trust platform for real-time voice, video, and digital-interaction verification and deepfake detection.

What you will do

• Design, document, build, operate, and optimize large-scale, highly available multi-cloud infrastructure across AWS and GCP.
• Own and evolve infrastructure components supporting the SaaS platform.
• Manage and scale observability, centralized logging, monitoring, alerting, and performance-analysis systems.
• Identify bottlenecks and manual workflows, then automate them into reliable and measurable systems.
• Improve cloud scalability, cost efficiency, reliability, security, and maintainability while collaborating across teams.
• Participate in a 24/7 on-call rotation approximately once every 16 weeks.

Requirements

• Location: must work remotely from Ukraine.
• 5–7 years of experience in DevOps, SRE, or similar cloud-focused roles.
• Experience designing, building, and operating large-scale automated cloud systems across multiple regions and availability zones in AWS and GCP.
• Hands-on experience with Kubernetes, including EKS or GKE, service mesh technologies, Terraform, Packer, Ansible, Helm, Flux or ArgoCD, and Istio.
• Strong experience with observability, centralized logging pipelines, CI/CD, incident response, on-call operations, and distributed systems.
• Strong scripting skills in Python, Bash, and/or TypeScript, plus experience with relational databases such as PostgreSQL or MySQL, including high-availability design and query optimization.

Nice to have

• Experience with telephony infrastructure.

Culture & Benefits

• Remote-first work environment.
• Competitive compensation, including equity for all employees.
• Unlimited paid time off.
• Contracted through Alcor BPO.
• Collaborative engineering environment focused on reliability, scalability, automation, and continuous improvement.

Hiring process

• The first 30 days focus on onboarding, learning the products and environments, and beginning to contribute through pull requests.
• By 60 days, independent contribution and participation in design discussions are expected.
• By 90 days, ownership of meaningful platform components or initiatives begins.