MetLife Is Hiring Jr. Software Dev Engineer in Pune

Overview

Quick heads up before you skim past this thinking it’s another generic “software developer” listing: it isn’t. MetLife’s opening here is specifically for someone to work on GitHub Enterprise administration and CI/CD automation — a niche that sits between DevOps and platform engineering, not general app development. If that distinction doesn’t mean much to you yet, keep reading, because it changes whether this role is a good fit.

The Basics

Company: MetLife
Role: Jr. Software Dev Engineer
Job ID: 19668
Location: Pune, Maharashtra
Work Setup: Hybrid, full-time
Relocation Support: Not offered — factor that into your decision if you’re outside Pune
Posted: 5 August 2026
Experience Band: 0–2 years

✅What This Role Is Not, and What It Actually Is

A lot of freshers see “Software Dev Engineer” and assume it means writing application code day to day. This one doesn’t. Read the responsibilities closely and it’s clear MetLife wants someone to help run and secure the internal developer tooling that other engineering teams rely on — think GitHub Actions pipelines, repository access controls, branch protection policies, and security scanning built into the CI/CD process.

In plain terms: you’d be less “building the product” and more “building and guarding the assembly line the product gets built on.” That’s a genuinely valuable and increasingly in-demand skill set — platform and DevSecOps engineers are hard to find at the junior level precisely because most fresh grads gravitate toward pure development roles instead.

✅Why That Distinction Matters for Your Career

If you go down this path early, you’re setting yourself up for platform engineering, DevSecOps, or Site Reliability Engineering roles down the line — all of which currently pay well above average and face a real talent shortage compared to generalist dev roles. The trade-off is that it’s a narrower specialization; if you later decide you want to go back to pure backend or full-stack development, you may need to actively rebuild that muscle.

For someone who genuinely enjoys automation, infrastructure, and the “how does this actually get deployed safely” side of engineering more than writing business logic, this is a strong entry point most freshers overlook simply because they don’t know the field exists yet.

✅The Actual Work, Broken Down

Set the corporate wording aside — day to day, this role covers three real chunks of work:

Pipeline modernization. Taking CI/CD setups and rebuilding them properly using GitHub Actions — reusable workflows, standard templates, the kind of thing that stops every team from reinventing automation from scratch.

Platform governance. This is the less glamorous but genuinely important part — deciding who gets access to what repository, enforcing branch protection so people can’t push straight to production branches, managing the runners that execute pipelines, and generally keeping GitHub Enterprise from turning into an ungoverned mess as the org scales.

Security built into the pipeline, not bolted on after. Getting security scanning and compliance checks directly into the CI/CD flow so vulnerabilities get caught before code ships, not after — this is the “DevSecOps” part of the title, and it’s a mindset shift from traditional QA that a lot of interviewers will probe for.

There’s also a lighter fourth piece — helping other developers adopt tools like GitHub Copilot and generally making the engineering org more productive, which suggests this role has a bit of an internal-consulting flavor too, not just heads-down pipeline work.

L&T GenAI Freshers Hiring: Check Here

Cornerstone Hiring Freshers : Check Here

Latest Off-Campus Jobs: Check Here

✅How to Actually Stand Out for This One

The listing asks for GitHub Actions, GitHub Enterprise governance, and — notably — migration experience from Azure DevOps, which tells us MetLife is likely mid-transition off Azure DevOps onto GitHub internally. If you’ve touched both platforms even briefly, that’s worth calling out explicitly in your application, since it maps directly to something they’re clearly dealing with right now.

Beyond that, here’s what’s realistically worth brushing up on if you have a few days before applying:

Write at least one real GitHub Actions workflow — even a simple one that runs tests on push. Being able to talk through a YAML workflow file in an interview will set you apart from candidates who’ve only read about CI/CD conceptually.
Understand branch protection rules and repo permissions models — this is core to the “governance” part of the role and rarely covered in college coursework, so most candidates will be weak here.
Know roughly what a security scanning step in a pipeline looks like — tools like CodeQL or Dependabot are common in GitHub Enterprise setups; you don’t need deep expertise, but you should be able to explain the concept.
Basic scripting comfort — the JD mentions scripting/APIs explicitly, so being able to write a simple script that hits the GitHub API (say, to list repos or check permissions) is a good thing to have ready to discuss.

✅A Note on MetLife Itself

MetLife is a large, established insurance and financial services company — not a tech-first employer, but one that’s visibly investing in internal engineering capability as part of what they’re calling their “New Frontier” push toward AI-enabled operations. For a role like this specifically, that context is actually relevant: companies going through internal platform modernization (like the Azure DevOps → GitHub migration hinted at here) tend to give early hires meaningful ownership, simply because the team building the new standard is still small. That’s often a better learning environment than joining a platform team at a company where the tooling has already been standardized for years.

If you’re a fresher who’s more excited by automation, infrastructure, and “how do we make 200 engineers ship code safely” than by writing yet another CRUD application, this role is a genuinely good, slightly under-the-radar opportunity. If you have zero interest in DevOps/platform work and just want a straightforward dev role, this probably isn’t the right fit — the title is a bit misleading in that sense.

📍How to Apply

Apply through MetLife’s official careers portal using Job ID 19668. Given the hybrid work arrangement and no relocation assistance, make sure Pune is workable for you before applying.

About LatestOffCampusJobs:

LatestOffCampusJobs is an initiative by Online Learning, one of India’s fastest-growing career guidance communities. Founded by Lokesh Bagora, we help freshers and recent graduates navigate the competitive job market by providing timely, accurate, and verified job updates.

What started as a YouTube channel sharing placement tips has grown into a full-fledged platform trusted by over 300,000 subscribers and a Telegram community of 27,000+ active job seekers.