Software Engineer
SLB (company site, opens in a new tab)5–7 yrsMysuruOn-siteDirect career pageEst. 12–22 LPA
Posted 1d ago
Reach people at SLB
People at this company you can reach
Log in to see who works here
Create a free account or log in to see the people at SLB you could write to:
- Recruiters & HR
- People in this function
- Work addresses
Your match
Against your primary resume
Log in to see your match score
Create a free account or log in to unlock your CV match score across:
- Role fit
- Experience
- Industry relevance
Protocol Intelligence
How competitive this role is
Competition
Background fit
Strictness
Log in to see why each signal reads the way it does.
Job description
Structured overview of role & requirements
About This Role
- Build and maintain scalable C#/.NET backend services, REST APIs, and microservices, with responsibility for performance, availability, and fault tolerance.
- Implement asynchronous message-queue processing and scheduled/background jobs; integrate Azure Blob Storage, cloud services, and SQL and NoSQL/time-series data stores.
- Support production reliability through logging, monitoring, troubleshooting, testing, and containerized deployment with Docker and Kubernetes.
Minimum Requirements
- Work Experience Required: 5–7 years of hands-on .NET development experience.
- Strong C# and .NET Core/ASP.NET Core skills; experience building REST APIs and working with message queues and background workers or scheduled jobs.
- Hands-on Azure Blob Storage and Azure cloud services experience; strong SQL Server and database design skills; experience with MongoDB and InfluxDB.
- Experience with Docker and Kubernetes; knowledge of API security (JWT/OAuth), object-oriented design, and design patterns.
Ideal Candidate Profile
- A senior backend engineer who has built and operated enterprise .NET services, with an emphasis on reliability, performance, and production issue resolution.
- Best aligned with event-driven systems and scheduled processing, plus practical experience integrating Azure services and SQL, document, and time-series data stores.
- Likely to succeed in a cross-functional delivery environment involving architecture and design discussions, code reviews, testing, and coordination with DevOps and QA.