.NET Worker Services and Background Jobs Internship

A small service with a big job

At 2am every night, a .NET worker service emails eleven thousand candidates the roles that matched their profile that day. When it fails, nobody notices until the support queue fills up at breakfast. Making that job observable, retryable and quick is what you will spend these two months on.

What you actually do

Rebuild the scheduling on top of Hangfire, add idempotency so a retry can never double send, and put a simple read-only dashboard in front of it so support can check the last run without messaging an engineer. You will also help split one monolithic batch into smaller queues, because today a single slow SMTP response holds up the entire send.

Terms, and what comes with them

The internship is remote from anywhere in India and it is unpaid, which we state plainly rather than in fine print. Your mentor is the engineer who wrote the original job, so you inherit the archaeology along with the code. Two months is enough time to finish this properly, and finishing it means your name sits on a system that runs every single night.