Evaluation Builder

Applicant Evaluation Checklist: Full Stack Developer (.NET, Modern JavaScript, Azure)

Complete Evaluation checklist is ready.

100% Model: gpt-5.5

Checklist Preview

Please answer briefly but specifically. Use examples from real work where possible, and feel free to anonymize client, employer, product, or end-user names. Do not include confidential code, credentials, private business data, or proprietary details.
The role requires broad full-stack ownership across backend, frontend, database, testing, release, and stakeholder coordination. We are looking for evidence of hands-on delivery, not generic self-ratings.

Relevant Experience

Tell us how your experience maps to this full-stack role.
1. Describe your commercial experience with C#, .NET, and ASP.NET Core Web API. What kinds of APIs or backend services have you personally built or maintained?
What to include: A strong answer names project types, responsibilities, API complexity, authentication, validation, error handling, and production usage.
2. Which modern JavaScript frameworks have you used professionally, such as React, Next.js, Angular, AngularJS, Vue, or TypeScript? Describe one feature you built end-to-end.
What to include: A strong answer explains the UI workflow, state/data handling, API integration, responsiveness, and your personal contribution.
3. Describe your hands-on Azure experience, especially with Azure App Services, Azure Functions, Managed Identity, Azure DevOps, CI/CD, Docker, Entra ID, OAuth, or OIDC.
What to include: A strong answer distinguishes tools you configured yourself from tools you only used indirectly.

Practical Work Examples

Share concrete examples of your recent delivery work.
1. Give one example of a module or enhancement you owned from requirements through design, backend, frontend, database, testing, release, and demo.
What to include: A strong answer includes the business goal, architecture choices, technologies used, delivery steps, and outcome.
2. Describe a database-related task you handled, such as schema design, EF Core or Dapper usage, migrations, query tuning, indexing, or diagnosing performance issues.
What to include: A strong answer explains the problem, your investigation, the change made, and how improvement was verified.
3. Tell us about your testing and code quality practices. What unit, integration, UI, or API tests have you written using tools such as xUnit, NUnit, Playwright, Cypress, or similar?
What to include: A strong answer gives examples of tests written, bugs prevented, review habits, and how you balance speed with maintainability.

Role-Specific Knowledge

These questions help us understand your practical technical judgment.
1. How would you design a secure REST API endpoint in ASP.NET Core for creating and updating a business record?
What to include: A strong answer covers request validation, authorization, DTOs, async patterns, dependency injection, data access, error responses, logging, and tests.
2. Explain how you would use Managed Identity from an Azure-hosted .NET application. What problem does it solve?
What to include: A strong answer mentions avoiding stored secrets, Azure resource access, configuration, permissions, and local development considerations.
3. Short assignment, expected time under 2 hours: Design a small full-stack feature for managing customer tasks. Provide a concise API design, database table outline, frontend component/workflow description, validation rules, and 5-8 test cases. You may include pseudocode, but do not submit proprietary code.
What to include: A strong answer shows practical full-stack thinking, clear tradeoffs, secure defaults, realistic tests, and enough detail for another developer to implement.

Ownership And Collaboration

This role works in a distributed pod with a senior full-stack lead and product stakeholders.
1. Describe how you work with a senior technical lead, product stakeholders, and other developers during planning, estimation, design discussions, daily coordination, and demos.
What to include: A strong answer includes communication style, handling ambiguity, raising blockers, giving updates, and incorporating feedback.
2. Give an example where you stepped outside your preferred layer, frontend or backend, to unblock delivery.
What to include: A strong answer shows willingness to work across the stack, learn quickly, and take responsibility for the feature outcome.
3. How do you use Git, pull requests, code reviews, and collaboration tools in a remote team?
What to include: A strong answer describes branch hygiene, review quality, responding to comments, documentation, and clear async communication.

Problem Solving

Tell us how you diagnose and resolve real delivery problems.
1. Describe a production or near-production defect you investigated across frontend, API, database, or infrastructure layers. What did you do first, and how did you confirm the fix?
What to include: A strong answer shows structured debugging, logs/observability, root-cause analysis, testing, and communication.
2. If an AI-assisted coding tool produces code that appears to work but you are unsure about security, correctness, or maintainability, how would you handle it?
What to include: A strong answer makes clear that you remain accountable for design, review, testing, security, and final code quality.

Availability And Fit

Confirm practical fit for the engagement model.
1. This is a full-time remote role working from India with three hours of daily overlap with U.S. Pacific / California time. Can you support this working model? If yes, what overlap window usually works for you?
What to include: A strong answer clearly confirms availability and gives a realistic recurring overlap window.
2. When could you start, and are there any planned commitments in the next six months that would materially affect full-time availability?
What to include: A strong answer gives a clear start date or notice period and flags only practical scheduling constraints relevant to the role.