.NET 8 and SQL Server Backend Intern

What you will have built by the end

Three months from your start date you will have shipped a working salary insights API: an endpoint that takes a job title and a city and returns a percentile band drawn from the stipend and CTC data buried in our listings table. It does not exist today.

Getting there

The data is messy. Salaries arrive as free text, as ranges, as annual figures and as monthly ones, sometimes inside the same posting. Your first fortnight goes into a normalisation pass written in C#, turning that mess into a clean table with a currency, a period and a confidence flag. Only once that holds up do you write the API on top of it in .NET 8, with response caching, because roughly twenty queries will account for most of the traffic.

Honest terms

This position carries no stipend and we would rather say that plainly than bury it. The exchange is meant to be clear: you get a genuine problem, a named mentor from the data team and a codebase that is reviewed properly, and we get a feature we have wanted for a year. You work from the Pune office two days a week and remotely the rest of the time.