The Associate Build and Release Engineer opening in Kochi is a full-time, on-site role based at Infopark, Kakkanad, with a salary up to ₹61,500 per month. It reports to the platform engineering group rather than a specific product team, which means the day-to-day work touches whichever squad has a release moving that week.
It's an associate-level seat, meaning the person hired here won't be expected to own a release process end-to-end from the first week, but will be doing real, hands-on pipeline work almost immediately rather than shadowing for months.
What the job covers
Day-to-day, the work centers on keeping the release process moving rather than on writing new product features.
- Keep CI/CD pipelines running cleanly so builds finish and releases go out on schedule
- Write and maintain the build scripts and automation tooling the wider engineering team relies on
- Coordinate with developers across different feature teams when release schedules or merge conflicts need sorting out
- Investigate build failures flagged during testing and track them back to their actual cause rather than just re-running the job
- Maintain version control workflows and help the team stick to agreed branching and merge practices
A good part of the role is genuinely reactive. A pipeline that worked fine yesterday can break today because someone else's commit introduced a dependency conflict three steps upstream, and figuring out which step actually broke is often the real task, not the fix itself. Getting comfortable with that kind of detective work matters more early on than knowing every tool in the stack cold.
Skills
The core toolkit for this role isn't unusual, but the team expects genuine day-to-day comfort with it, not passing familiarity.
- Working knowledge of build automation tools
- Practical CI/CD experience, whether that's Jenkins, GitLab CI, or a comparable platform
- Comfortable with version control systems and standard branching workflows
- Scripting ability, most commonly in Bash or Python, for automating routine build and deployment tasks
Nice to have
Some exposure to containerized build environments with Docker is a plus, and so is basic familiarity with a cloud platform like AWS or Azure, since a growing share of release work directly touches cloud-hosted infrastructure. Candidates who've maintained clear documentation of past pipeline setups tend to ramp up faster here, too, largely because much of this work involves picking up where someone else left off. None of these bonus items are dealbreakers on their own, but a candidate with two or three of them usually needs less hand-holding in the first month. Even one solid project involving a real production pipeline, rather than a personal or academic one, tends to stand out during screening.
Education and experience
A bachelor's degree is the baseline requirement, most commonly in computer science, information technology, or a closely related subject. Alongside that, candidates should have around two years of hands-on experience with build and release work, or close enough to it that the core skills above are already second nature rather than freshly learned. A background that's mostly general software development with some CI/CD exposure on the side can still work, provided the pipeline experience is real and not limited to watching a build finish from a dashboard.
Where you'd be working
The role sits at Infopark, Kakkanad, one of Kochi's main tech hubs, with a wide enough concentration of IT employers nearby that commuting options and food outlets around the campus are well established. Naukri Mitra regularly lists build and release engineer jobs in Infopark, Kakkanad, Kochi, and this campus tends to attract candidates already living in or near Kakkanad rather than those commuting from across the city.
Pay and benefits
Pay for this role goes up to ₹61,500 per month, in line with what a build and release engineer salary in Kochi typically looks like at the associate level. The package includes health insurance, paid time off, and provident fund contributions.
Because the position is on-site, the company also offers relocation assistance and accommodation support for candidates moving to Kochi specifically to take the job. Those two benefits tend to matter most for candidates from outside Kerala, since the associate salary band here leaves less room to absorb the upfront costs of a move without that kind of support.
Team and pace
Release days tend to run longer than the rest of the week, especially if a deployment window falls in the evening to limit disruption to live users. Outside those windows, the pace is steadier, with time devoted to cleaning up scripts, updating documentation, and chasing down smaller pipeline improvements that never quite make it to the top of anyone's list during a busy sprint. It's a reasonable trade-off in practice: fewer late nights than a typical on-call rotation, but the ones that do happen are planned rather than a surprise.
New hires typically pair with a more senior release engineer for the first several weeks before taking on a pipeline solo, which gives enough runway to learn the team's specific tooling without carrying full responsibility for a release from day one. That pairing period also tends to be where most of the team's specific quirks and workarounds get passed along, the kind of detail that rarely makes it into written documentation. After a year or so of solid pipeline work, most associates move up to a full release engineer title with broader ownership over which pipelines they manage independently.
Applying
Anyone applying should be ready to describe a build or deployment problem they've personally diagnosed, including what the first few troubleshooting steps looked like before the actual cause turned up. A resume that only lists tool names doesn't say much on its own without concrete examples attached. It also helps to mention which scripting language you default to and roughly how many services or repositories a past pipeline setup had to support at once. Applications are reviewed on a rolling basis, and shortlisted candidates are contacted directly for the next step.
