Release Engineer
Listed on 2026-09-01
-
IT/Tech
SRE/Site Reliability, AWS, IT Infrastructure
- We’re hiring a Release Engineer to join our growing Release Engineering team. You’ll be the hands-on practitioner responsible for executing production deployments across the Nymbus platform, working at the intersection of deployment tooling and product knowledge. You’ll execute releases with precision, validate behavior post-deployment, and help maintain the stability of a platform that financial institutions depend on
- This is a high-trust, high-accountability role. You’ll have direct access to production
- Environments and be expected to exercise sound judgment in every action you take. We’re not looking for someone to run a checklist. We’re looking for a technical contributor who understands what they’re deploying, why it matters, and what to watch for
- You’ll join as part of the founding team building out our Release Engineering function, with a clear path to growing into a senior/technical lead role as you take on more ownership. Our platform is hosted on AWS, so prior AWS experience is a strong plus for this role
- Execute production and non-production deployments using Helm, ArgoCD, and Rancher, following established release procedures and exercising independent judgment when conditions deviate from expected
- Manage Helm chart configurations and releases, ensuring deployments are consistent, repeatable, and aligned with the intended release state across environments
- Use ArgoCD to monitor application sync status, manage rollouts, and respond to drift or deployment failures in a timely and methodical manner
- Operate within Rancher to manage Kubernetes cluster workloads, validate pod health, and troubleshoot deployment-level issues across environments
- Build working knowledge of the Nymbus platform architecture to inform deployment decisions and speed up issue diagnosis
- Participate in off-hours release windows, including evenings and weekends as scheduled, to support deployments that require low-traffic maintenance windows
- Monitor system behavior immediately following deployments, identifying anomalies early and escalating or rolling back as appropriate
- Contribute to release documentation, deployment runbooks, and post-release summaries
- Partner with the Release Coordination team to confirm deployment readiness, flag blockers early, and maintain clear communication throughout the release cycle
- Use AI coding tools as a core part of how you work: drafting and reviewing merge requests, generating boilerplate config and chart changes, and speeding up routine deployment tasks
- Identify repetitive or manual steps in the release process and build small tools, scripts, or automations (AI-assisted or otherwise) to eliminate them and streamline the team’s workflow
- Healthcare and Dependant Care Flexible Spending Accounts
- Nymbus Awards and Recognition
- Retirement Plan Services / 401(k)
- Parental and Disability Leaves
- Time Off and Company Holidays
- Flexibility of being Fully Remote
- Collaborative Environment
- Employer Subsidized Medical and Dental Insurance
Strong process discipline and clear communication. You follow procedure rigorously, speak up early when something looks wrong, and don’t cut corners under time pressure
Familiarity with ArgoCD and Rancher, strongly preferred
Comfort using AI coding assistants (such as Git Hub Copilot, Claude Code, or similar) as a daily part of your workflow, not just for autocomplete but for drafting merge requests and building internal tooling
Comfort with off-hours work as a routine part of the role, not an exception
Off-hours availability required for scheduled production deployments
A builder’s instinct: when you spot a repetitive task, your first thought is how to script or automate it away
Experience in a regulated or high-availability environment (fintech, banking, or SaaS platforms serving enterprise clients) is a meaningful advantage
Experience deploying and troubleshooting workloads on AWS is a strong plus
At least 2 years hands-on experience with Helm and Kubernetes in a production environment
#J-18808-Ljbffr(If this job is in fact in your jurisdiction, then you may be using a Proxy or VPN to access this site, and to progress further, you should change your connectivity to another mobile device or PC).