Full Stack Engineer

Project Role : Full Stack Engineer

Project Role Description : Responsible for developing and/or engineering the end-to-end features of a system, from user experience to backend code. Use development skills to deliver innovative solutions that help our clients improve the services they provide. Leverage new technologies that can be applied to solve challenging business problems with a cloud first and agile mindset.

Must have skills : .Net Full Stack Development

Good to have skills : NA

Minimum 3 Year(s) Of Experience Is Required

Educational Qualification : 15 years full time education

Job Summary

Must Have (Core Applicable Across Most .Net Full Stack Demands)

These are the explicit core expectations called out for the role (end to end full stack delivery).

Backend / API

Strong proficiency in C# and .NET Core / .NET 6+ with ASP.NET Core

Ability to build secure, high performance RESTful APIs and server side business logic

Frontend

Proficiency in HTML5, CSS3, JavaScript/TypeScript

Hands on experience with at least one modern framework: React / Angular / Blazor

Ability to create responsive, user friendly interfaces

Database / ORM

Strong knowledge of SQL Server (and/or PostgreSQL) including database design and query optimization

Experience with ORM tools such as Entity Framework Core

DevOps / Delivery Tooling

Experience with Git and repositories like GitHub / GitLab

Experience with Visual Studio / Visual Studio

Hands on exposure to CI/CD pipelines (explicitly referenced: GitHub Actions / Azure DevOps)

Docker containerization and deployment exposure (called out under Cloud & DevOps responsibilities)

Testing & Ways of Working

Ability to write unit/integration tests using xUnit / NUnit and troubleshoot issues

Comfortable working in an Agile/Scrum environment with cross functional collaboration

Good to Have (Commonly Requested, Not Universal)

The following are frequently valued add-ons, and are already implied as part of broader responsibilities like system integration and cross team collaboration you can include them when you want broader coverage across open demands.

Stronger exposure to system integration with third party services (explicit responsibility area)

Comfort working closely with UI/UX designers, product managers, and QA teams (explicit collaboration expectation)

Note: The JD excerpt doesn t explicitly list a separate Good to Have section for .NET the items above are framed as commonly valued enrichers while staying consistent with the stated responsibilities.

Depending on Client Needs (Demand Specific / Program Driven Overlays)

Use these as optional overlays depending on the client stack, delivery model, and program complexity. (These are not explicitly listed in the JD excerpt they are practical add-ons you can toggle demand by demand.)

Cloud preference: Azure heavy vs AWS heavy environments (the JD references Azure/AWS deployment add specifics based on the client)

UI framework preference: React vs Angular vs Blazor (choose based on client standards)

Database preference: SQL Server vs PostgreSQL (choose based on client)

Delivery model: modernization/build vs run/support (expand troubleshooting + reliability language if AMS/GCC run is involved)

Experience

a: Should have Good Communication Skills and leadership skills.

b: Should have Good analytical skills and presentation skills.

c: Minimum 15 yrs. of full time educational is required., 15 years full time education