Platform Engineer at crescerance, Gurgaon

Open. Posted .

Production platform engineering with CI/CD pipelines, shared services, environment ownership and a fellow engineer to mentor. The role is based in Gurgaon.

Apply on crescerance's site for Platform Engineer

Applying opens the employer's page. Want jobs like this sent to you each morning? Open Elip.

Key facts
LocationGurgaon, Haryana
Work modeOn-site
Experience3–4 years
PayNot stated by the employer
RoleDevOps Engineer
Skills asked forCI/CD, Cloud infrastructure, Code review, Access control, Monitoring, Logging, Alerting
Posted19 Nov 2026

Elip's summary

Builds platform infrastructure for an education product company. Automates CI/CD, manages production environments, and develops shared platform services using CI/CD, cloud infrastructure, and Supabase. Applies Azure DevOps and automated testing to keep deployments reliable.

The job, in the employer's words

Role at a glance

DetailInformation

Job titlePlatform Engineer

FunctionEngineering, DevOps & Infrastructure

CompanyEngagifii

LocationGurgaon, India

Reports toChief Architect

About the role

Engagifii is hiring a Platform Engineer to own the platform every product ships on, so that what we build reaches production safely, repeatably, and without depending on any one person. You will make every deployment repeatable and every environment ready before it is needed. You will report to the Engineering lead, work daily with product owners, builders, Delivery Management and QA & Automation, and guide a fellow Platform Engineer to full scope.

Why this role exists

When agents write most of the code, review, testing, deployment and running it become the bottleneck. Builders own what and why; you own how, and whether it is production-ready.

Nothing reaches production except through a pipeline and an environment you have set up or approved.

Key roles and responsibilities

  • Code review and deployments

Review code, written by people and AI agents, for correctness, security and production readiness, not style.

Release every change through the pipeline with no manual production changes; block deployments that fail it or skip review.

Fix critical bugs, and record the root cause and the safeguard against recurrence.

  • Environments and DevOps across projects

Set up and maintain dev, staging and production environments for every active project.

Keep a current inventory (what runs where, owner, deploy and rollback), write runbooks with rollback steps, and set DevOps standards.

  • Automation

Build tools that remove manual steps from deployment, environment setup, test reporting and monitoring, so any product owner can get an environment, ship a change and see its health without waiting on a person.

Live today: automated deployment portal, daily automated test reports, and a bug reporting agent for Azure DevOps. Next: a Supabase merge management tool and a health scan utility based on data and logs.

  • Shared platform services

As a peer coder, co-build services every product reuses: Webhook Manager, Test Runner (a gate inside every pipeline), Monitoring Service and an LLM Gateway for AI model access.

  • Supporting product teams

Guide product owners and builders on Supabase, Forge and similar platforms so work arrives production-ready.

Turn repeated questions into short training videos for our internal MasterClass library, reviewed by the Engineering lead.

  • Mentoring a fellow Platform Engineer

Set their standards (runbook format, pipeline templates, environment conventions) and review their infrastructure changes, moving them to full ownership in stages (about two hours a week).

Aim: nothing is blocked when you are away.

Making new products launch-ready

Every new build passes a ten-item handoff package. Four items are yours, and any gap is yours to close: automated test coverage (with QA & Automation); dev, staging and production environments; pipelines, access controls and monitoring; and performance testing where relevant.

Authority and success

Decisions: You decide pipeline and environment structure, blocking failing deployments, rolling back harmful changes, and DevOps standards. You agree architecture, deployment timing and new paid services with product owners, Delivery Management and the Engineering lead. Product scope and spend belong to others.

Escalation: Every Platform Engineer escalates straight to the Engineering lead; production incidents then go to the product owner.

Success looks like: 100% of covered projects deploy through pipelines by day 60; change failure rate tracked and falling; every project can roll back from its runbook; issues detected by monitoring before customers; reviews within one working day; your fellow Platform Engineer can deploy any project from its runbook. Baselined in month one, reviewed at 90 days.

Growth: Senior Engineer by owning production without anyone checking behind you. Compensation and terms are covered separately.

Who we are looking for

An engineer who treats production as the product: you review code critically, automate repeated work and write things down so others can follow them unaided.

Must have

Hands-on CI/CD experience, deploying through pipelines rather than by hand

Experience running dev, staging and production environments with access control and monitoring

Strong code review skills, including AI-generated code for correctness and security

Experience writing runbooks and rollback procedures, and keeping an inventory of what runs where

Working knowledge of cloud infrastructure, logging and alerting

Ability to fix critical production bugs and document root cause and prevention

Clear communication with non-DevOps teammates, including product owners

Good to have

Supabase, Azure DevOps or AI-builder platforms such as Lovable

Agentic coding tools such as Claude Code

Automated testing, test runners and performance testing

Building shared services such as webhook handling, monitoring or an LLM gateway

Mentoring a junior engineer or creating training content

About crescerance

Headquartered in Atlanta, founded in 2011.

People in Elip's index who work here
49
Typical time at crescerance
3.4 years
Typical career length so far
6.4 years

Largest teams

  • Engineering21 people

Totals from public professional profiles in Elip's index; any group under ten people is left out.

All open jobs at crescerance

Similar open jobs

More jobs in Gurgaon or all jobs on Elip

About this page

Elip lists jobs that employers publish on their own careers sites, never copies from job boards. This one comes from crescerance's listing on Keka, posted 19 Nov 2026. The summary is Elip's; the description is the employer's. When the job closes, this page says so.