Server-Side Engineering Intern (Node.js + Redis)

Premise

Caching is easy to add and hard to add correctly. Half the slow endpoints on MailerMen would be quick with the right key and the right invalidation, and nobody has had three uninterrupted months to give the problem. You will. Over those three months you profile the twenty slowest API routes using real production timings, then work through them one at a time.

What lands on your plate

That means a Redis layer in front of the employer dashboard aggregates, stampede protection on the popular job listing pages, and a small internal library so the next engineer does not invent a fourth caching pattern. You will also write Jest tests that assert invalidation actually fires, because that is where these things quietly rot. Nothing ships without a measurement attached.

We want you comfortable with Node.js and Express, curious about what makes a request slow, and willing to measure before you change anything. Final year students and recent graduates are both fine. You spend two days a week in the Bengaluru office, sit next to the engineer who owns backend performance, and present your before and after numbers to the team in your final week.