Employer-paid medical, dental, vision, and life insurance; medical insurance for employees, Gym bonus support Education reimbursement (Up to MXN 54,000 per year) 30% vacation bonus 10 days paternity leave Work at Home Bonus for office equipment 1-time MXN 5,000 What you'll do: Track every committed story from dev-ready through release, and make stalled or aging work visible early. Actively drive work in progress down: help the team finish before starting, and keep work-in-progress limits honest. Diagnose why work is stuck at any stage, such as an unclear requirement, a pending review, an unmerged dependency, a failing pipeline, a pending infrastructure change, or missing test evidence. Know where to go and who to bring in to remove each barrier; you'll clear the path rather than do the engineering yourself. Have direct, constructive conversations with engineers when work stalls, going beyond status updates and Jira hygiene to real, meaningful unblocking support Run releases end to end. Run a weekly release train, including schedules, cutoffs, and go/no-go decisions Prepare releases: confirm scope, verify environment readiness, and assemble release notes. Run and monitor test suites, interpret the results, and confirm test evidence is in place before promotion. Ship releases to staging and production through our Git Ops workflow, with rollback plans ready. Map dependencies across infrastructure, software, and safety, and flag risks before they cause delays. Capture the sequencing that comes out of initiative kickoffs with the architects, and hold the team to it. Own release documentation and communication:



Manage change control records and release evidence. Keep Jira and Git Lab accurate, so the status of every commitment is clear without anyone having to ask. Tell our customer teams what's shipping and when. Make delivery faster over time: Measure and improve cycle time from dev-ready to production, work in progress, throughput, release frequency, and change failure rate. Treat repeated manual work as a signal to automate; work with engineers to move release steps into the pipeline or to coding agents, such as test evidence, release notes, and change records. Adapt the delivery process as the team grows, keeping it as light as the environment allows. Qualifications: 5+ years in technical delivery, technical program management, release management, Dev Ops, or software engineering, including time on a platform, infrastructure, or developer-tools team. Hands-on experience with CI/CD and Git-based workflows (Git Lab preferred), including running test suites and reading pipeline and test output. Working knowledge of Kubernetes and Git Ops deployment, enough to understand why a deployment is stuck and who can fix it. Experience running releases and change control in a regulated or high-governance environment. A track record of improving flow on a fast-moving engineering team, with examples you can quantify, such as shorter cycle times or higher release frequency. Clear, direct communication, and comfort holding senior engineers accountable while staying collaborative. A bias for action: you notice stalled work before anyone asks and follow through until it ships. #J-18808-Ljbffr

📌 Release engineer (Tijuana)
🏢 ITJ
📍 Tijuana