Free · takes a minute · your resume fills your profile
CoreHRx never asks candidates for money. If anyone does, .
Role at a glance
You will
Develop a good understanding of business use cases and user needs for features assigned
Contribute to story writing and grooming by asking appropriate questions and demonstrating strong grasp of feature functionality
Communicate technical issues in a way that can be understood by non-technical people
Experience
5+ years
Must-have skills
AgileC#CSSDesign PatternsHTMLJavaScript
Work mode
Hybrid
How well do your skills match this job?
Sign in to see your fit: the skills, experience and location this job asks for, checked against your profile.
Job description
Location: Jaipur, IN Department: Engineering
The Software Engineer II is a trusted and collaborative member of their POD or development team, capable of implementing medium-complexity features with moderate guidance from senior engineers.
Responsibilities:
Develop a good understanding of business use cases and user needs for features assigned
Contribute to story writing and grooming by asking appropriate questions and demonstrating strong grasp of feature functionality
Communicate technical issues in a way that can be understood by non-technical people
Work on multiple clients/projects independently
Participate in technical conversations
Proficient in communicating technical principles
Have Insurance, Life and Annuities domain knowledge, or actively learning and developing in this area
Develop a strong understanding of business use cases, user needs, and feature functionality for assigned projects and features
Establish, document, and maintain high-quality software modules
Contribute to story writing and grooming
Independently manage work across multiple clients or projects
Design, write, comment, and unit test code
Maintain accountability for all assigned work
Communicate technical issues and project status effectively
Actively participate in team meetings, technical discussions, and process improvement activities
Plan ahead and identify potential challenges early
Continuously seek opportunities to learn and develop new skills
Develop and maintain domain expertise in Insurance, Life, and Annuities
Understand Agile and Waterfall development lifecycles
Participate in client/product grooming calls
Understand and utilize debugging tools and techniques
Update and maintain defect/change tracking systems
Qualifications:
Minimum of 5+ years of experience in software development
Proficiency in C#
In-depth knowledge of the .NET framework
Proficiency in HTML, CSS, and JavaScript
Experience with database technologies
Understanding of the software development lifecycle (SDLC) and agile methodologies
Object-Oriented Programming (OOP) and Design Patterns
Experience working in an Agile scrum team environment
Knowledge of unit testing frameworks
Awareness of common security vulnerabilities and best practices
Proficiency in optimizing application performance
We believe the best ideas and innovation happen when we are together. Employees in this role will work in the office four days, with the flexibility to work remotely one day (Friday).
This guide is for C# and .NET developers in India preparing for interviews, from freshers applying for a first role at a Pune IT services firm or a Bengaluru product company to engineers with several years of experience moving into senior positions. It has 60 questions in three levels: language basics such as types, OOP and collections; then everyday topics like LINQ, async and await, ASP.NET Core middleware, dependency injection and Entity Framework Core; and finally senior topics such as the thread pool, garbage collection, performance and design. Each answer is written the way a strong candidate would say it, with C# code where it helps. The answers are based on C# 12 and .NET 8, and most of them apply to later versions too. Try answering each question aloud before you read the answer, then take the mock test.
Questions you may be asked
What is the difference between C#, .NET and the CLR?
What is the difference between value types and reference types in C#?
What are boxing and unboxing, and why should you avoid them in hot code?
Why are strings immutable in C#, and when should you use StringBuilder?