Find your next opportunity
Browse fresh openings from leading companies and apply with a resume tailored to the role.
Browse expert rolesBrowse expert rolesBrowse fresh openings from leading companies and apply with a resume tailored to the role.
Browse expert roles13975 openings
10009-10016 of 13975
Rocket Learning
Free to start · No card · 5 credits the moment you sign up
Reports to:Head of Infrastructure / Director of Platform Engineering
Experience:8–10+ years in DevOps, SRE, or Infrastructure Engineering
We're looking for a Senior DevOps Engineer to own our infrastructure and lead a small, growing team. We work with sensitive data belonging to vulnerable populations, so security and privacy aren't afterthoughts — they're core to how we build. You'll run multi-cloud infrastructure (AWS, GCP, MongoDB Atlas), champion open-source tooling over vendor lock-in, and help shape an engineering culture that takes both craft and mission seriously.
Design and operate secure, highly-available infrastructure across AWS and GCP. Own MongoDB Atlas end-to-end (provisioning, scaling, backups, performance tuning). Drive infrastructure-as-code (Terraform/Ansible) so environments are consistent and reproducible.
Apply security best practices by default — IAM, network segmentation, encryption, secrets management (OpenBao/Vault), vulnerability scanning. Treat data protection as a first-class requirement given the sensitivity of the populations we serve, not just a compliance checkbox.
Evaluate, self-host, and own the lifecycle (upgrades, HA, patching) of open-source tools like SigNoz, SonarQube, and OpenBao — reducing vendor dependency without compromising reliability.
Build observability stacks (metrics, logs, traces) and intelligent alerting that cuts noise, not signal. Define SLIs/SLOs. Be a senior escalation point for major incidents and drive blameless postmortems.
Maintain CI/CD pipelines (Jenkins/GitLab CI/GitHub Actions) with quality and security gates built in. Manage Kubernetes-based container orchestration and automate routine operational work.
Lead and develop a team of 3 DevOps engineers — workload, mentorship, growth. Build good processes, not just good infrastructure. Work closely with engineering, product, and security teams, and stay genuinely invested in why the work matters.
8–10+ years across DevOps/SRE/Infrastructure, including experience leading or mentoring a team
Strong hands-on experience with AWS, GCP, and hybrid/on-prem environments
Proven track record self-hosting and operating open-source infrastructure tools in production
Solid grounding in security and privacy engineering — this matters more here than in a typical infra role
Experience with Kubernetes, Terraform/Ansible, and modern CI/CD
Strong Linux administration and scripting (Bash, Python or Go)
A genuine interest in our mission — this isn't a "just infra" role; you'll be working on systems that serve vulnerable communities, and that context should matter to you
Clear communicator who can work across technical and non-technical teams
Good to have:MongoDB Atlas experience, observability/AIOps tooling (Prometheus, Grafana, SigNoz), FinOps/cost optimization, relevant certifications (AWS, GCP, CKA).
Originally posted on Himalayas
Start with a role or skill you want to use in your next job. Use the location and role filters to narrow the results, then open a listing to review the description. A title alone rarely explains the level of responsibility, working arrangement, or experience a team needs. Compare those details before deciding which opportunities deserve a tailored application.
Employers use different titles for similar work. If an exact phrase produces no results, try a shorter title, a core skill, or an alternative name for the role. Remove one filter at a time to understand which requirement is narrowing your search. A broader search can reveal suitable work without asking you to change your actual qualifications.
For each promising listing, read the responsibilities and separate essential requirements from preferences. Note the location, schedule, employment type, and compensation when provided. Missing details are questions to confirm with the employer. A remote opening may still require a particular country, work authorization, or time-zone overlap, so check the full posting before treating it as a location-independent opportunity.
Choose a few examples that demonstrate the skills this employer names. Explain your contribution and its outcome, using accurate numbers where available. Put the most relevant experience first and keep your resume easy to scan. Avoid adding technologies, qualifications, or achievements simply because they appear in a description. Your application should make your existing strengths easier to understand.
Follow the employer’s instructions for resumes, cover letters, work samples, and screening questions. Review the exported file before submitting it: confirm that contact details are correct, text can be selected, and links reach the intended pages. A resume check can help you spot unclear writing before you apply. Its feedback is advisory and does not predict a hiring decision.
Listings are collected from external sources and may change after they appear here. The employer or recruiting destination controls whether applications are open. If an original link is unavailable, check the company’s careers page for the title or move to another opening. An employer website link is a place to check current vacancies, rather than confirmation that a particular job is still accepting applications.
Keep a simple record of the company, role, job reference, application date, and documents you sent. Record any follow-up instructions and the next action you plan to take. This makes it easier to prepare for interviews, compare opportunities, and avoid applying repeatedly to the same opening through different boards. Review your shortlist as employers update their listings and prioritize opportunities with clear requirements that match the work you want to do.