Senior DevOps Engineer

What you'll do

Required skills & experience

Preferred qualifications

• Experience turning a manual, human-run release process into a fully automated one as a scoped project — not just incremental pipeline improvements.
• Experience operating infrastructure for a self-serve, marketplace-distributed SaaS product.
• Familiarity with cloud data platform deployment models — warehouse-adjacent compute or native application distribution.
• When you join Solvd, you'll...
• Shape real-world AI-driven projects across key industries, working with clients from startup innovation to enterprise transformation.
• Be part of a global team with equal opportunities for collaboration across continents and cultures.
• Thrive in an inclusive environment that prioritizes continuous learning, innovation, and ethical AI standards.
• Ready to make an impact?
• If you're excited to build things that matter, champion responsible AI, and grow with some of the industry’s sharpest minds. Apply today and let’s innovate together.
• Solvd is an equal opportunity employer.

Qualifications

• 5+ years in a DevOps, platform engineering, or SRE role with real ownership of a CI/CD pipeline for a production system — not just consuming someone else's pipeline.
• Hands-on experience with secrets management — designing rotation schedules and per-tenant/per-environment scoping, not just storing static values.
• Infrastructure-as-code experience with Terraform or equivalent for standing up and managing multiple environments consistently.
• Experience building observability — metrics, logging, alerting — for distributed systems with many independent, loosely-connected clients.
• Comfortable working with multi-platform build pipelines across at least two operating systems, including packaging and signing requirements.
• Security-conscious by default — this role directly replaces a process that bakes shared secrets into distributed software; access control needs to be a standing question, not an afterthought.

Responsibilities

• Redesign the current manual, per-customer release pipeline into an automated, parameterized CI/CD pipeline that a provisioning event can trigger directly — no manual pipeline run or spreadsheet edit required.
• Build and operate secrets-management infrastructure — vaulting, per-tenant scoping, rotation schedules — that the backend credential-issuance service runs on top of.
• Own infrastructure-as-code for all services being built as part of this migration — provisioning APIs, configuration services, admin console — across dev, staging, and production environments, with consistent and reproducible builds.
• Build monitoring and alerting for a distributed, endpoint-heavy system with known failure modes — stale proxy detection, retry storms, unbounded local queue growth — turning silent failures into pages before customers report them.
• Maintain build and release tooling for multi-platform client software, making platform-specific configuration differences visible and manageable rather than a source of drift.
• Tighten access controls, logging, and distribution for production configuration tooling as part of the broader security posture of the release process.
• Required skills & experience
• 5+ years in a DevOps, platform engineering, or SRE role with real ownership of a CI/CD pipeline for a production system — not just consuming someone else's pipeline.
• Hands-on experience with secrets management — designing rotation schedules and per-tenant/per-environment scoping, not just storing static values.
• Infrastructure-as-code experience with Terraform or equivalent for standing up and managing multiple environments consistently.
• Experience building observability — metrics, logging, alerting — for distributed systems with many independent, loosely-connected clients.
• Comfortable working with multi-platform build pipelines across at least two operating systems, including packaging and signing requirements.
• Security-conscious by default — this role directly replaces a process that bakes shared secrets into distributed software; access control needs to be a standing question, not an afterthought.