Senior DevOps Engineer / Release Engineer

You will own how Traackr engineers build, test, and ship: the CI/CD pipelines, delivery infrastructure, standardized developer environments, and test automation that every product and data team depends on. You will embed with those teams for stretches at a time to fix friction where it actually happens, and you will lead the design of the systems that replace it, from proposal through rollout. Your customers are Traackr engineers, so success is measured in adoption and team velocity: faster builds, fewer flaky runs, less setup, fewer manual steps between a commit and production.

• Take high-complexity delivery and tooling work from concept to production, often as the only engineer on it.
• Lead design discussions for the build, test, and deployment systems, balancing speed, reliability, and cost, and author the architecture documents or RFCs behind the decisions.
• Own CI/CD pipelines end to end, including the move from Jenkins to GitHub Actions, cut build and test time, automate, add caching, and make releases repeatable with a clear rollback path.
• Own developer environments and internal tooling (local setup, standardized environments, CLIs, and scripts) so engineers spend less time on tooling and more time shipping.
• Embed with an engineering team for a stretch at a time, work the way they work, and fix the friction you find rather than filing it as a ticket for them.
• Eat your own dogfood. Work on or with the teams you enable and actually use the tools you've built, and continually evaluate if there's room for improvement.
• Build AI into everyday development workflows, including tooling for code review, tests, refactoring, and internal search, with sensible defaults around security and data handling.
• Drive incident response for the delivery toolchain and own post-mortems with follow-ups that get completed.
• Set a baseline before a change and measure after it (build times, deployment frequency, and how long a new engineer takes to get from requirements to a merged change), and say so plainly when something did not help.
• Plan rollouts across teams: surface dependencies early, negotiate scope, migrate rather than cut over in one step, and write the documentation and runbooks that let teams use what you build without you in the room.
• Act as the go-to technical mentor on tooling, testing, and delivery practice through code review, pairing, and design feedback.

• 7+ years of related experience and a bachelor's degree, including hands-on work in developer experience, CI/CD, build or release engineering, platform automation, or developer tooling.
• Experience building and shipping application software, not only platform work, with a track record of helping product teams move faster without giving up quality.
• Range matters more to us than an exact stack match. If you have worked across the development lifecycle and pick up new tools quickly, we want to talk even if our stack is not the one you know best.
• Strong command of at least one production language (Node, Python, Kotlin, or comparable), and the ability to write and review automation and test code held to product standards.
• Depth with CI platforms (e.g., Jenkins, GitHub Actions), Git platforms (e.g., GitHub, Bitbucket), and infrastructure-as-code tools (e.g., Terraform, Ansible, Helm).
• Working knowledge of containers and Kubernetes-based deployments (EKS), enough to debug why a build or deploy is failing, not necessarily to run the cluster.
• A track record of making pipelines or test suites faster and more reliable, with numbers to show for it across build and test time, caching, and flake reduction.
• Experience with modern testing tooling and with API and contract testing, including reviving a suite a team had stopped trusting.
• Experience leading a technical design that crossed team boundaries: writing the proposal, getting agreement, and seeing the migration or deprecation through to the end.
• Comfortable using AI tools such as Claude in day-to-day engineering work, and interested in building them into how other teams work, with good judgment about security, data handling, and where output needs verifying.
• Able to work inside another team's codebase and process for a stretch at a time, earn their trust, and leave things better without taking over.
• Strong written communication and a service mindset. Documentation and a clear proposal are a real part of the job, and you measure success by whether other engineers actually adopt what you build.