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 the questions below using brief, specific examples from your own practical work. You may anonymize client, employer, product, repository, and domain names, and you should not disclose confidential information.
We are looking for evidence of full-stack ownership across backend, frontend, database, testing, Azure deployment, and stakeholder collaboration. Concise answers are preferred; links to public samples are welcome but not required.

Relevant Experience

Tell us how your recent experience maps to this full-stack role.
1. Describe your commercial software development experience over the last 3-5 years, especially where you owned features across backend, frontend, database, testing, and release.
What to include: A strong answer names the stack used, your specific responsibilities, feature complexity, team size, and what you personally delivered.
2. Which modern JavaScript frameworks have you used in production, such as React, Next.js, Angular, AngularJS, Vue, or TypeScript-based stacks? Describe one real feature you built with one of them.
What to include: A strong answer explains the framework, component structure, state/forms approach, API integration, validation, and any performance or usability considerations.

Practical Work Examples

Share examples that show how you build and deliver working software.
1. Give one example of an ASP.NET Core Web API or C#/.NET backend service you built or significantly enhanced.
What to include: A strong answer includes API design, authentication or authorization, validation, error handling, dependency injection, async programming, logging, and how the service was tested.
2. Describe a relational database task you handled, such as schema design, query optimization, indexing, migrations, EF Core, Dapper, or diagnosing a performance issue.
What to include: A strong answer explains the problem, database approach, tradeoffs, measurable improvement if available, and how you verified correctness.
3. Describe your hands-on experience with Azure App Services, Azure Functions, Managed Identity, or related Azure services.
What to include: A strong answer identifies the Azure services used, what you configured or coded yourself, deployment model, identity/security handling, and production support responsibilities.

Role-Specific Knowledge

These questions check practical engineering judgment for this stack.
1. How would you structure a new full-stack feature using ASP.NET Core Web API, a modern JavaScript frontend, and SQL? Briefly cover API endpoints, data access, validation, error handling, and tests.
What to include: A strong answer shows end-to-end thinking, clean boundaries, secure defaults, testability, and awareness of maintainability.
2. What is your practical approach to authentication and authorization in a .NET API, especially when using OAuth, OIDC, Entra ID, JWTs, roles, or policies?
What to include: A strong answer distinguishes authentication from authorization, mentions token validation and least privilege, and explains how decisions are enforced and tested.
3. Short assignment, maximum 2 hours: outline a small feature for managing task items with create, update, list, and status change flows. Include a simple data model, REST API contract, frontend component approach, validation rules, test cases, and Azure deployment notes. You may provide pseudocode, diagrams, or a short written design; do not use confidential code.
What to include: A strong answer is clear, practical, scoped, and demonstrates how you would build across API, UI, database, tests, and deployment without overengineering.

Ownership And Collaboration

This role works remotely from India with a U.S. product and engineering team.
1. Describe a time you worked with a senior technical lead, product stakeholder, QA, designer, vendor, or customer contact to deliver a feature or release.
What to include: A strong answer explains how you clarified requirements, communicated progress, handled feedback, coordinated dependencies, and supported demo or release readiness.
2. This role is not frontend-only or backend-only. Describe how comfortable you are stepping into any application layer when the team has a blocker.
What to include: A strong answer gives examples across at least two layers, such as UI, API, database, Azure, tests, CI/CD, debugging, or production support.

Problem Solving

Tell us how you diagnose issues and make technical decisions.
1. Describe a difficult production or pre-release defect you investigated across frontend, backend, database, or cloud infrastructure.
What to include: A strong answer covers symptoms, investigation steps, tools used, root cause, fix, test coverage, and what changed afterward to prevent recurrence.
2. How do you use AI-assisted coding tools, if at all, while remaining accountable for security, design, tests, and final code quality?
What to include: A strong answer shows responsible use, independent review, secure coding awareness, test verification, and refusal to submit code you do not understand.

Availability And Fit

Help us confirm operating model fit before interview.
1. Can you work remotely from India with three hours of daily overlap with U.S. Pacific/California working hours? Please describe your workable overlap window in India time.
What to include: A strong answer gives a clear recurring availability window and any constraints that should be planned around.
2. Are you available for a full-time dedicated six-month engagement if selected? Please share your earliest realistic start date and any notice period.
What to include: A strong answer gives a specific start timeline, notice period, and any planned availability constraints relevant to delivery.