Candidate Scoring
Candidate Evaluation Scoring Report: TMGOC Full Stack Developer (.NET + Modern JavaScript + Azure)
Complete
Candidate scoring report is ready.
Scoring Preview
Candidate Evaluation Scoring Report: TMGOC Full Stack Developer (.NET + Modern JavaScript + Azure) India-based full-time contract Full Stack Developer for TMGOC pod work, requiring 3-5 years commercial experience, strong C#/.NET and ASP.NET Core Web API, modern JavaScript frontend capability, relational database work, Azure services, testing, debugging, and remote collaboration with U.S. Pacific overlap. Scoring Notes Submitted evaluation responses were treated as primary practical evidence; resumes were used to corroborate and identify follow-up areas. Blank or sparse evaluation submissions were scored conservatively even where resumes list relevant technologies. Criteria weights total 100; each criterion score is 0-10 and contributes proportionally to the overall score. No candidate except Krunal provided meaningful completed evaluation evidence in the supplied material; availability and start-date answers are missing for all candidates. Scoring Parameters - Full-stack ownership and role fit (20): Evidence of owning features across backend, frontend, database, testing, release, and willingness to work across layers in the required 3-5 year pod model. - .NET/C# API depth (20): Hands-on ASP.NET Core Web API, C#, REST, dependency injection, secure backend design, service/API implementation, and backend troubleshooting. - Modern JavaScript frontend (15): Production use of React, Angular, Next.js, TypeScript, or similar component-based frontend stack with real feature examples. - SQL, data access, and performance (15): Relational schema design, EF Core/Dapper/LINQ, migrations, indexing, query optimization, transactional design, and diagnosing database performance issues. - Azure, DevOps, and deployment readiness (15): Practical Azure App Services, Functions, Managed Identity or related Azure services, CI/CD, cloud deployment, configuration, and release support. - Practical evidence, testing, debugging, collaboration, and availability (15): Specific evaluation examples, test approach, production defect diagnosis, stakeholder collaboration, communication clarity, AI-tool accountability, Pacific overlap, and six-month availability. Candidate Ranking - Krunal Pagdar: 75/100 - Strong shortlist - Rohit Warge: 50/100 - Possible shortlist - Aboli Mane: 48/100 - Possible shortlist - Sanju Singh Tomar: 42/100 - Needs careful review - Nidhin C: 40/100 - Needs careful review Krunal Pagdar Best evidenced fit in the supplied material. Evaluation gives concrete examples across ASP.NET Core, React/TypeScript, PostgreSQL, load testing, performance diagnosis, tenant isolation, JWT-based auth, and cloud deployment. Resume corroborates 4+ years full-stack .NET experience, React, SQL Server/PostgreSQL, Azure DevOps, and client/stakeholder work. Main gap is that hands-on Azure evidence is weaker than Oracle Cloud/Vercel evidence, and availability responses are missing. Full-stack ownership and role fit: 8/10 - Evaluation describes SalesFlow and LeadPilot across backend, frontend, database, testing, deployment, and documentation; resume shows 4+ years, close to the target range. .NET/C# API depth: 8/10 - Strong ASP.NET Core, MVC, WCF, REST API, authentication, multitenancy, Unit of Work, and security claims, with practical examples in the evaluation and resume. Modern JavaScript frontend: 8/10 - Evaluation and resume cite React 19, TypeScript, Tailwind, Angular, responsive grids, API integration, and shipped UI work. SQL, data access, and performance: 8/10 - Specific PostgreSQL tenant isolation, row-level locking, EF Core filters, query optimization, SQL Server/PostgreSQL experience, and k6 performance diagnosis. Azure, DevOps, and deployment readiness: 6/10 - Resume lists Azure and Azure DevOps CI/CD, but evaluation says SalesFlow was deployed on Oracle Cloud and Vercel and that Azure mapping is part of AZ-900/AZ-104 preparation. Practical evidence, testing, debugging, collaboration, and availability: 7/10 - Good debugging and load-test evidence, case-study links, decision logs, and stakeholder-oriented documentation; missing direct answers on Pacific overlap, six-month availability, and senior-team collaboration. Strong points: - Most complete practical submission among the candidates, with concrete architecture, performance, security, and deployment examples. - Resume supports full-stack .NET plus React/TypeScript and SQL/PostgreSQL experience. - Shows engineering judgment through multitenancy, transaction optimization, load testing, authentication hardening, and documented tradeoffs. Weak points: - Azure App Services, Azure Functions, and Managed Identity are not strongly evidenced in the evaluation; cloud experience is mainly Oracle Cloud and Vercel. - Some strongest examples appear to be independent projects, so commercial scale and team delivery need validation. - Availability, notice period, and Pacific overlap answers are absent. Probe further: - Ask Krunal to walk through the SalesFlow tenant-isolation implementation and explain exactly what he personally built. - Ask for a live explanation of how he would deploy the same app to Azure App Service with Azure Database, Key Vault or Managed Identity, logging, and CI/CD. - Ask him to reproduce a small task-item API plus React component design live, including validation, tests, and error handling. - Confirm full-time six-month availability and three hours of daily U.S. Pacific overlap. Rohit Warge Resume is a reasonable backend-heavy match for the role, showing 3 years 9 months experience, ASP.NET Core, Web API, EF Core, Dapper, SQL/PostgreSQL, Kafka, Redis, Docker, Azure, and BFSI integrations. However, the submitted evaluation is blank in the supplied material, so practical full-stack depth, frontend ownership, Azure specifics, testing, communication, and availability are not evidenced. Full-stack ownership and role fit: 5/10 - Resume shows relevant 3.9 years and backend feature ownership in BFSI platforms, but evaluation provides no completed examples and frontend ownership is not clear. .NET/C# API depth: 7/10 - Resume strongly lists ASP.NET Core, Web API, EF Core, Dapper, microservices, integration architecture, and resilient API layers. Modern JavaScript frontend: 2/10 - Resume lists JavaScript and Ajax but does not evidence React, Angular, Next.js, Vue, or TypeScript production feature ownership; evaluation is blank. SQL, data access, and performance: 7/10 - Resume provides SQL, PostgreSQL, EF Core, Dapper, Redis caching, SQL optimization, and high-volume processing examples. Azure, DevOps, and deployment readiness: 4/10 - Resume lists Microsoft Azure and production deployment pipelines, but no specific Azure App Service, Functions, Managed Identity, or CI/CD details are evidenced in the evaluation. Practical evidence, testing, debugging, collaboration, and availability: 3/10 - Resume mentions production deployments and reliability work, but the evaluation has no examples, test approach, defect walk-through, stakeholder collaboration, AI-tool accountability, or availability information. Strong points: - Resume aligns well with the target 3-5 year experience band. - Strong backend and BFSI integration signals: ASP.NET Core, Web API, EF Core, Dapper, Kafka, Redis, SQL/PostgreSQL, third-party financial APIs. - Claims production reliability and performance optimization experience. Weak points: - Completed evaluation content is missing, so practical communication and ownership cannot be assessed from the assignment. - Modern frontend framework evidence is weak for a role that explicitly rejects backend-only fit. - Azure experience is listed but not substantiated with role-specific services or deployment examples. Probe further: - Ask Rohit to explain one banking platform feature end to end, including API, database, frontend touchpoints, testing, and release. - Probe whether he has production React, Angular, Next.js, Vue, or TypeScript experience beyond JavaScript/Ajax. - Ask for a concrete Azure deployment example involving App Service, Functions, Managed Identity, or equivalent services. - Confirm availability, notice period, and three hours of daily U.S. Pacific overlap. Aboli Mane Resume shows 4+ years full-stack .NET experience with React.js, Angular, SQL Server, REST APIs, EF Core, Dapper, Azure DevOps, JWT, CI/CD, production support, and Agile work. The submitted evaluation is blank in the supplied material, so specific practical examples, Azure service depth, testing, debugging, ownership, and availability are not evidenced. Full-stack ownership and role fit: 5/10 - Resume describes end-to-end transportation/tracking systems and current enterprise enhancements, but evaluation provides no role-mapping example. .NET/C# API depth: 6/10 - Resume lists .NET Core, MVC, ASP.NET Core, C#, Web API, REST APIs, dependency injection, JWT, and third-party integrations. Modern JavaScript frontend: 5/10 - Resume lists React.js and Angular with transportation/tracking systems, but no submitted feature example is provided. SQL, data access, and performance: 5/10 - Resume lists SQL Server, LINQ, Dapper, EF Core, database structures, and optimization, but evaluation does not provide a concrete database task. Azure, DevOps, and deployment readiness: 4/10 - Resume lists Azure DevOps, Git, CI/CD, and pipelines, but not hands-on Azure App Service, Functions, Managed Identity, or cloud deployment detail. Practical evidence, testing, debugging, collaboration, and availability: 3/10 - Resume mentions production support, Agile, Jira, global teams, and deployments, but evaluation lacks specific examples, test cases, defect diagnosis, AI-tool approach, and availability. Strong points: - Resume presents a broad full-stack .NET profile with React.js, Angular, SQL Server, REST APIs, EF Core, and Dapper. - Relevant production support and application enhancement experience. - Some collaboration signals through Agile, Jira, global teams, and change management. Weak points: - Completed evaluation content is missing, so practical depth is not demonstrated. - Azure evidence is mostly Azure DevOps rather than Azure application hosting, Functions, or Managed Identity. - Testing depth and security/auth implementation are listed only at a keyword level. Probe further: - Ask Aboli to walk through one React plus .NET Core feature from the transportation/tracking system, including her exact ownership. - Ask for a concrete database optimization or schema-design example with before/after impact. - Ask her to design the task-item assignment live, including API contracts, frontend state, validation, and test cases. - Confirm availability, notice period, and three hours of daily U.S. Pacific overlap. Sanju Singh Tomar Resume shows substantial .NET experience and recent React, .NET Core, SQL Server, Azure SQL, Blob Storage, Functions, API Management, and xUnit exposure. However, the submitted evaluation is blank, the resume indicates approximately 14 years total IT experience and 8 years Dot Net experience, which is much more senior than the 3-5 year pod-member target, and the current role date appears inconsistent because it says 12/2025 to present while the prior role ended 02/2025. Full-stack ownership and role fit: 4/10 - Resume shows full-stack and leadership signals, but seniority appears above the target band and evaluation provides no ownership examples. .NET/C# API depth: 6/10 - Resume lists ASP.NET, C#, MVC, .NET Core, Entity Framework, Web API, WCF, and long Microsoft-stack experience. Modern JavaScript frontend: 4/10 - Resume lists React.js and Angular in recent projects, but no feature-level evidence is provided in the evaluation. SQL, data access, and performance: 5/10 - Resume shows long SQL Server experience and database-heavy CRUD/reporting work, but little evidence of indexing, migrations, performance diagnosis, EF Core depth, or Dapper. Azure, DevOps, and deployment readiness: 5/10 - Resume lists Azure SQL Database, Blob Storage, App Service, Functions, API Management, Managed Instance, and Databricks, but evaluation has no practical deployment example. Practical evidence, testing, debugging, collaboration, and availability: 2/10 - Evaluation is blank; resume mentions client interaction, xUnit, and team cooperation, but no test cases, defect diagnosis, AI-tool approach, availability, or Pacific overlap. Strong points: - Resume indicates broad Microsoft-stack experience across ASP.NET, C#, MVC, .NET Core, SQL Server, React, and Azure services. - Has recent resume claims for Azure Functions, API Management, Blob Storage, Azure SQL, React, and xUnit. - Long experience with enterprise, government, hostel booking, membership, and management systems. Weak points: - No completed evaluation evidence was supplied. - Seniority appears significantly above the requested 3-5 year profile, creating fit and cost/role-expectation risk. - Resume contains a date inconsistency: current role listed as 12/2025 to present while prior role ended 02/2025. Probe further: - Clarify the employment timeline, especially the 12/2025 to present entry. - Ask Sanju to explain a recent .NET Core plus React feature and identify exactly what he personally owned. - Probe practical Azure depth with App Service, Functions, API Management, Managed Identity, CI/CD, and monitoring. - Confirm he is comfortable with a hands-on pod-member role under a senior technical lead, not only a lead/senior role. Nidhin C Resume shows long .NET, SQL, MVC, Angular/React, Azure, DevOps, support, and development experience across ERP, healthcare, manufacturing, energy, and ITSM domains. However, the submitted evaluation is blank, the resume indicates 11+ years experience which is far above the 3-5 year role target, and several project descriptions are generic support/development statements rather than concrete full-stack feature ownership. Full-stack ownership and role fit: 3/10 - Resume indicates broad support/development experience but not enough recent end-to-end ownership evidence, and seniority is outside the target range. .NET/C# API depth: 5/10 - Resume lists C#.NET, .NET Core API, MVC, ASP.NET, WCF, Blazor, Entity Framework, and many .NET roles, but lacks specific API design examples in the evaluation. Modern JavaScript frontend: 4/10 - Resume lists Angular, React, jQuery, JavaScript, and Blazor, but no production frontend feature example is supplied. SQL, data access, and performance: 5/10 - Resume lists SQL Server, MySQL, database fixing, database design, LINQ, and EF, but no concrete optimization, indexing, migration, or performance diagnosis evidence. Azure, DevOps, and deployment readiness: 5/10 - Resume lists MS Azure, AWS, DevOps, CI/CD, Git, and server configuration, but no evaluation evidence for Azure App Services, Functions, or Managed Identity. Practical evidence, testing, debugging, collaboration, and availability: 2/10 - Evaluation is blank; resume is mostly generic role descriptions and does not provide test approach, defect walkthrough, AI-tool approach, availability, or overlap information. Strong points: - Resume shows extensive .NET ecosystem exposure, including MVC, .NET Core API, Entity Framework, SQL Server, Angular, React, Blazor, Azure, DevOps, and CI/CD. - Has support and development exposure in large-team enterprise settings. - Some relevant domain breadth: healthcare, manufacturing, energy, ERP, ITSM, banking, and education. Weak points: - No completed evaluation evidence was supplied. - Experience level is far above the requested 3-5 years, raising role-fit concerns. - Resume examples are often generic and support-oriented, with limited evidence of modern full-stack product ownership. Probe further: - Ask Nidhin to walk through one recent feature from Timesense or Moonpreneur, covering API, UI, database, tests, and deployment. - Clarify whether he is seeking a hands-on full-stack developer role under a senior lead despite 11+ years experience. - Probe actual React or Angular ownership versus support/maintenance exposure. - Confirm availability, notice period, and three hours of daily U.S. Pacific overlap.