Candidate Evaluation Scoring Report: Full Stack Developer (.NET + Modern JavaScript + Azure)

Scoring Preview

Candidate Evaluation Scoring Report: Full Stack Developer (.NET + Modern JavaScript + Azure)

India-based full-time contract Full Stack Developer role for TMGOC/FlexGCC requiring 3-5 years of commercial experience, strong C#/.NET and ASP.NET Core Web API capability, modern JavaScript frontend work, SQL, Azure deployment exposure, testing, collaboration with a U.S. team, and willingness to work across the full stack.

Scoring Notes
Submitted evaluation responses were treated as the primary evidence of practical depth and communication; resumes were used to corroborate and identify follow-up areas.
Blank or sparse evaluation submissions were scored conservatively even where the resume claimed relevant experience.
Overall scores are weighted from 0-10 criterion scores; criteria weights add to 100.

Scoring Parameters
- .NET/API and full-stack ownership (25): ASP.NET Core/C# backend depth, REST API delivery, end-to-end feature ownership, dependency injection, async patterns, logging, validation, and release support.
- Modern JavaScript frontend (15): Production use of React, Next.js, Angular, AngularJS, Vue, or TypeScript-based frontend stacks, including component structure, forms, state, validation, and API integration.
- SQL and data access (15): Relational schema work, SQL Server, EF Core, Dapper or comparable data access, migrations, indexing, stored procedures, and performance diagnosis.
- Azure and DevOps fit (15): Hands-on Azure App Service, Azure Functions, Managed Identity, Azure SQL, Static Web Apps, CI/CD, deployment troubleshooting, monitoring, and production configuration.
- Engineering judgment, security, testing, assignment quality (20): Quality of the short assignment, authentication/authorization approach, error handling, test strategy, production debugging, AI-tool accountability, and practical tradeoff awareness.
- Collaboration, communication, and availability (10): Remote collaboration, stakeholder/QA/vendor work, ability to step into any layer, communication clarity, U.S. Pacific overlap, six-month availability, and start-date fit.

Candidate Ranking
- Naresh N: 79/100 - Strong shortlist
- Aditya Soni: 57/100 - Needs careful review
- Abhishek Kumar Tyagi: 56/100 - Possible shortlist
- Sohamkumar Modi: 36/100 - Do not shortlist
- Revati Jadhav: 35/100 - Do not shortlist

Naresh N
Best evidenced submission. Evaluation and resume match by name, email, phone, GitHub, LinkedIn, and work history. Shows practical .NET/Angular/SQL ownership, detailed Azure deployment exposure, and concrete debugging examples. Gaps remain around Azure Functions and Managed Identity, and some patterns are more junior or traditional than ideal.
.NET/API and full-stack ownership: 8/10 - Gives specific ASP.NET Core Web API example with FluentValidation, EF Core migrations, DTOs, async service layer, ILogger, JWT auth, custom exception middleware, DI, and API testing; resume supports 3 years of .NET/Angular roles.
Modern JavaScript frontend: 8/10 - Production AngularJS and Angular 12-18 experience, Reactive Forms, HttpClient, interceptors, RxJS, and Angular migration/learning repository are evidenced in the evaluation and resume.
SQL and data access: 8/10 - Strong practical SQL/EF/Dapper evidence: stored procedures, ROW_NUMBER pagination, indexes, partitioning, AsNoTracking, FindAsync, migrations, backups/restores, and query optimization.
Azure and DevOps fit: 7/10 - Hands-on Azure App Service, Azure Static Web Apps, Azure SQL, GitHub Actions, Azure VM/IIS, firewall/connectivity troubleshooting, and environment configuration; no production Azure Functions or Managed Identity.
Engineering judgment, security, testing, assignment quality: 7/10 - Assignment is complete and practical with model, endpoints, DTOs, Angular components, validation, tests, and Azure notes. Auth answer is concrete for JWT but lacks OAuth/OIDC/Entra depth; some choices such as localStorage JWT and frequent query-parameter use should be probed.
Collaboration, communication, and availability: 8/10 - Clear examples of client/lead collaboration, documentation, cross-layer blocker resolution, and currently serving notice with earliest availability stated as 01 August 2026; U.S. overlap answer is truncated in supplied context and should be confirmed.
Strong points:
- Evaluation provides specific, grounded examples across backend, frontend, database, Azure deployment, testing, and debugging.
- Resume corroborates 3 years of full-stack .NET and Angular work across UtiliPlus, Tulasi Web Solutions, and Studio Soft Solutions.
- Has hands-on Azure App Service, Azure SQL, Azure Static Web Apps, GitHub Actions, Azure VM, and deployment troubleshooting exposure.
- Shows practical SQL/data-access depth through Dapper, EF Core, stored procedures, pagination, indexing, and partitioning.
Weak points:
- No production experience claimed with Azure Functions or Managed Identity, both required in the SOW.
- Authentication experience appears mainly custom JWT username/password rather than OAuth/OIDC/Entra ID.
- Short assignment uses a limited task model and Active/Inactive status, not the richer Pending/InProgress/Completed status flow requested.
- Frontend assignment chooses template-driven forms for a simple form despite prior Reactive Forms experience; probe decision-making.
Probe further:
- Confirm the exact daily U.S. Pacific overlap window because the supplied evaluation text is truncated after question 8.1.
- Ask the candidate to walk through the Azure App Service plus Azure SQL deployment issue and show exactly what they configured themselves.
- Ask how they would replace SQL authentication with Managed Identity and what code/config changes would be required.
- Ask them to implement or sketch a small OAuth/OIDC or Entra ID protected endpoint live, including authorization policies.
- Have them explain tradeoffs between EF Core and Dapper in one report feature they personally delivered.

Aditya Soni
Resume is highly aligned with the role, but the submitted evaluation is almost entirely blank except for status codes in the assignment. Evaluation and resume match by filename/name. Because practical evaluation evidence is missing, the score is conservative despite strong resume claims around ASP.NET Core, Angular/React/Next.js, Azure Functions, Azure DevOps, tests, and security.
.NET/API and full-stack ownership: 7/10 - Resume claims ASP.NET Core .NET 6/8, REST APIs, Clean Architecture, integrations, multi-tenant SaaS, and enterprise modules, but the evaluation does not provide practical examples.
Modern JavaScript frontend: 7/10 - Resume lists Angular 13/17, React, Next.js, TypeScript, and frontend performance improvements; evaluation gives no real frontend feature evidence.
SQL and data access: 6/10 - Resume shows SQL Server, EF Core, PostgreSQL/Supabase, query optimization, and multi-tenant data patterns, but the evaluation does not answer the database task.
Azure and DevOps fit: 6/10 - Resume includes Azure Functions, Azure DevOps CI/CD, Azure AD, Azure Storage/Blob, and Azure certifications; no submitted evaluation evidence confirms hands-on Azure work for this role.
Engineering judgment, security, testing, assignment quality: 4/10 - Resume has strong claims around OWASP, xUnit/Moq, SonarQube, auth migration, RBAC, and production-grade logging, but the assignment response is effectively missing apart from HTTP status codes.
Collaboration, communication, and availability: 4/10 - Resume suggests enterprise team experience, but the evaluation lacks stakeholder, remote overlap, notice period, and six-month availability answers.
Strong points:
- Resume is the strongest technology match on paper: ASP.NET Core, Angular, React, Next.js, TypeScript, SQL Server, Azure Functions, Azure DevOps, Azure AD, xUnit, Moq, and Clean Architecture.
- Resume includes security-heavy and enterprise examples such as OWASP assessments, RBAC, multi-tenant architecture, SSO, Stripe, Adobe Sign webhooks, and auth migration for 5000+ users.
- Resume reports measurable outcomes such as 35% frontend performance improvement, 90%+ unit test coverage, and reduced defect leakage.
Weak points:
- Submitted evaluation is sparse and does not demonstrate practical ownership, communication, database work, Azure work, auth approach, assignment design, or availability.
- Resume claims are not supported by candidate-specific evaluation examples, so practical depth remains unverified.
- Availability, notice period, and U.S. Pacific overlap are missing from the supplied evaluation.
Probe further:
- Ask why the evaluation was mostly blank and request the candidate to complete the task-item assignment live or as a timed follow-up.
- Ask the candidate to walk through one ASP.NET Core + Angular/React feature from the resume, including what they personally owned.
- Probe the 5000+ user authentication migration: migration plan, rollback strategy, token/identity mapping, tests, and release validation.
- Ask for a live explanation of Azure Functions usage and whether it was implemented, deployed, monitored, and supported personally.
- Confirm notice period, earliest start date, full-time six-month availability, and three-hour U.S. Pacific overlap.

Abhishek Kumar Tyagi
Evaluation and resume match by name, email, phone, LinkedIn, and work history. Strong commercial .NET/MVC/Web API, SQL Server, CRM, payments, workflow, vendor integration, and stakeholder delivery evidence. Main fit risk is that the evaluation states production frontend work is mainly JavaScript/jQuery/Razor rather than modern frameworks, and Azure experience is limited.
.NET/API and full-stack ownership: 7/10 - Evaluation describes CRM lead-allocation API with role authorization, validation, async database operations, DI, logging, Postman testing, UAT, production release, and support; resume supports nearly 5 years in .NET/MVC/Web API.
Modern JavaScript frontend: 3/10 - Evaluation explicitly says production frontend work is mainly JavaScript, jQuery, AJAX, and Razor rather than React or Angular, despite resume listing React.
SQL and data access: 7/10 - Evaluation gives SQL Server stored procedure, join, index, and performance optimization examples; resume corroborates SQL Server, stored procedures, RDLC, reporting, and CRM data workflows.
Azure and DevOps fit: 3/10 - Evaluation says Azure hands-on experience is limited and applications are mainly hosted on IIS; Azure App Services, Functions, slots, monitoring, and Managed Identity are described as concepts.
Engineering judgment, security, testing, assignment quality: 7/10 - Task assignment is well structured with model, REST contract, React/TypeScript component plan, validation, test cases, Azure deployment notes, OAuth/OIDC/Entra/JWT answer, and production defect example with idempotency.
Collaboration, communication, and availability: 8/10 - Good stakeholder, QA, product, and payment-vendor example; clear full-stack blocker answer; confirms India remote overlap and full-time six-month availability with 30-day notice.
Strong points:
- Strong evidence of end-to-end ownership in CRM and loan-settlement work, including API, UI, SQL, testing, UAT, release, and support.
- Resume corroborates domain breadth across loan settlement, BPO operations, HRMS, healthcare, recruitment CRM, payment gateways, e-signature, dialer integration, reporting, and workflows.
- Good SQL Server and stored procedure optimization evidence.
- Clear availability: 8:30 PM-11:30 PM IST during Pacific Daylight Time and 9:30 PM-12:30 AM IST during Pacific Standard Time; 30-day notice.
Weak points:
- Modern JavaScript production experience is weak for this JD; evaluation says mainly jQuery/AJAX/Razor, while resume lists React without evaluation evidence.
- Azure hands-on experience is limited; no production Azure App Service, Azure Functions, or Managed Identity evidence.
- Some assignment content is stronger than the candidate's stated hands-on Azure and React experience, so ownership should be verified.
- Resume title and leadership claims exceed what the role needs but practical modern-stack evidence is uneven.
Probe further:
- Ask the candidate to build or explain a small React or Angular component live, including state, validation, API integration, and error handling.
- Probe the resume's React claim since the evaluation says production work was mainly jQuery/AJAX/Razor.
- Ask what Azure services they have personally configured versus only studied conceptually.
- Have them walk through the payment status duplicate-callback defect and explain the idempotency design.
- Ask how they would deploy their current IIS-hosted application to Azure App Service with Managed Identity and Application Insights.

Sohamkumar Modi
Evaluation file appears blank, so there is no submitted practical evidence. Resume match is assumed from filename Sohamkumar and resume name Sohamkumar Modi. Resume shows relevant 3+ years with Angular, .NET Core Web API/MVC, SQL Server, PostgreSQL, Azure DevOps, and CI/CD, but these claims are not supported by evaluation answers.
.NET/API and full-stack ownership: 5/10 - Resume claims .NET Core Web API/MVC and full-stack project work, but the evaluation provides no backend/API example.
Modern JavaScript frontend: 5/10 - Resume lists Angular, TypeScript, JavaScript, and an Angular migration leadership claim, but the evaluation provides no production feature example.
SQL and data access: 4/10 - Resume lists SQL Server, PostgreSQL, MySQL, database tuning, and project database use; no evaluation evidence for schema design, indexing, migrations, or performance diagnosis.
Azure and DevOps fit: 2/10 - Resume lists basic Azure DevOps and CI/CD; no evidence of Azure App Services, Azure Functions, Managed Identity, or hands-on cloud deployment in the evaluation.
Engineering judgment, security, testing, assignment quality: 2/10 - No assignment, auth/security answer, defect example, test strategy, or AI-tool accountability was provided.
Collaboration, communication, and availability: 3/10 - Resume mentions QA, UI/UX, DevOps collaboration and Agile sprints, but the evaluation lacks availability, overlap, notice period, and stakeholder examples.
Strong points:
- Resume shows 3+ years of experience aligned to the target seniority range.
- Resume includes Angular, .NET Core Web API/MVC, SQL Server, PostgreSQL, Azure DevOps, CI/CD, Agile, and Git.
- Resume claims end-to-end lifecycle work and beginning to lead a 5-person MVC-to-Angular migration.
Weak points:
- Submitted evaluation is blank, so practical depth, communication, assignment quality, availability, and ownership are missing.
- No evaluation evidence for Azure App Service, Azure Functions, Managed Identity, authentication, testing approach, or production debugging.
- Resume cloud exposure appears basic and not Azure service-specific.
Probe further:
- Confirm the blank evaluation was the candidate's actual submission and whether a completed response exists elsewhere.
- Ask the candidate to complete the task-item assignment live or in a controlled timed setting.
- Probe the MVC-to-Angular migration: what he personally led, architecture changes, release plan, and testing.
- Ask for one concrete .NET Core Web API feature walkthrough including database design, validation, auth, tests, and deployment.
- Confirm full-time six-month availability, notice period, and three-hour U.S. Pacific overlap.

Revati Jadhav
Evaluation file appears blank, so there is no submitted practical evidence. Resume match is assumed from filename Revati and resume name Revati Jadhav. Resume contains relevant .NET, Angular, SQL Server, MongoDB, Azure, Docker, CI/CD, microservices, Redis, Kafka, and JWT claims, but the role asks for 3-5 years and the resume states 2+ years.
.NET/API and full-stack ownership: 5/10 - Resume claims ASP.NET Core Web API, microservices, CQRS, FastEndpoints, and 20+ REST APIs, but the evaluation provides no practical example.
Modern JavaScript frontend: 4/10 - Resume lists Angular, HTML, CSS, Bootstrap, and ERP frontend work; evaluation gives no production frontend answer.
SQL and data access: 4/10 - Resume includes SQL Server, stored procedures, MongoDB, DynamoDB, Cosmos DB, and query optimization; no evaluation evidence confirms practical depth.
Azure and DevOps fit: 4/10 - Resume mentions Azure, Docker, Azure DevOps CI/CD, Azure Blob, and Cosmos DB, but no evaluation evidence for App Service, Functions, Managed Identity, or deployment ownership.
Engineering judgment, security, testing, assignment quality: 2/10 - No submitted assignment, auth approach, test strategy, defect example, or AI-tool accountability; resume claims xUnit, RBAC, Redis, Kafka, and microservices remain unverified.
Collaboration, communication, and availability: 3/10 - Resume mentions mentoring, PR reviews, Agile collaboration, and interviews, but evaluation lacks availability, overlap, start date, and concrete stakeholder delivery evidence.
Strong points:
- Resume shows broad modern backend exposure: ASP.NET Core, EF Core, microservices, CQRS, JWT, Redis, Kafka, Docker, Azure, and CI/CD.
- Resume includes Angular and enterprise application modules across business platform, ERP, monitoring, event, and subscription/payment workflows.
- Resume claims mentoring, PR reviews, and cross-functional Agile delivery.
Weak points:
- Submitted evaluation is blank, so practical role-specific evidence is missing.
- Resume states 2+ years, below the SOW's required 3-5 years of commercial experience.
- No evaluation evidence for Azure App Services, Azure Functions, Managed Identity, SQL task, auth approach, tests, production defect handling, or availability.
Probe further:
- Confirm whether a completed evaluation response exists elsewhere; if not, request a timed completion before interview.
- Probe actual commercial tenure against the 3-5 year requirement.
- Ask the candidate to walk through one claimed microservices assignment, including what she personally owned versus team-owned.
- Ask for a live design of the task-item feature covering API, Angular UI, SQL, validation, tests, and Azure deployment.
- Confirm full-time six-month availability, notice period, and U.S. Pacific overlap.