Senior Full Stack Developer
Summary
Senior full-stack developer building web apps with Angular/React front ends and .NET/ASP.NET Core back ends on cloud (Azure/AWS/GCP). Day to day: designing REST APIs and event-driven distributed systems, applying caching strategies (Redis), and debugging production issues to drive root cause analysis.
Role : Senior Full Stack Developer (.NET / Angular or React)
Experience: 10+ years
Timings : 3 - 12pm
Type: Full-time
Location : Bangalore , Coimbatore
About the Role
We're hiring a Senior Full Stack Developer with strong React and .NET skills and real experience with cloudbased, distributed systems. The key thing for us: you understand how the moving parts queues, message buses, caches — actually work, not just how to publish and subscribe. When something breaks in production, we need someone who knows enough about what's happening under the hood to start digging and drive a root cause analysis.
What You'll Do
- Build and maintain modern web applications with React and .NET / ASP.NET Core • Design scalable backend services, REST APIs, and cloud-native solutions • Work with messaging and event-driven architectures
- Apply sensible caching strategies to keep applications fast
- Investigate production issues and lead root cause analysis
Required Skills
- Frontend: Angular or React, JavaScript/TypeScript, component-based architecture, state management • Backend: .NET / ASP.NET Core, REST APIs, async programming, design patterns • Cloud: Azure, AWS, or GCP — designing and supporting distributed applications
Messaging — you should understand, not just use: Hands-on with at least one of Azure Service Bus, RabbitMQ, Kafka, or AWS SQS/SNS, and able to reason about how they work — pub/sub, fan-in/fan-out, retries, dead-letter queues, message ordering, at-least-once vs exactly-once delivery, and idempotency. You know why duplicate messages happen and how to prevent them.
Caching — strategy, not just usage: Redis or similar, with a grasp of the trade-offs — cache-aside, invalidation, expiration policies — and when each applies. Production troubleshooting: Comfortable diagnosing messaging failures and performance bottlenecks through logs and monitoring, and running RCA on distributed systems.
The Bar We're Setting
We're not expecting deep, nitty-gritty distributed-systems expertise. We are looking for someone who knows enough about how these systems behave underneath to investigate confidently, ask the right questions, and get to the root cause — rather than someone who only knows the publish/subscribe surface.