NestJS Interview Questions

Interviewers ask Nest questions to verify you understand DI, the request pipeline, and modular architecture—not only decorator syntax.

How to Prepare

Be ready to explain why Nest exists over plain Express, how modules export providers, and how guards/pipes/interceptors differ. Trace a request through the pipeline out loud.

// Classic prompt: order these for an incoming request
// middleware, guards, interceptors, pipes, controller, service, filters

Answer: middleware -> guards -> interceptors (pre) -> pipes -> controller/service -> interceptors (post) -> exception filters on errors.

Question Themes

Core DI & modules
Request pipeline pieces
Auth (JWT/Passport/guards)
Persistence (TypeORM/Prisma)
TestingModule & e2e
Microservices patterns

Explain constructor injection and custom provider tokens.
Compare ValidationPipe vs custom pipes.
Describe when to use interceptors vs middleware.
Discuss modular monolith vs microservices trade-offs.

Quick-Fire Answers

Short responses to frequent Nest interview prompts.

Question	Short Answer
What is a module?	DI boundary grouping controllers/providers
What is a provider?	Injectable class/value managed by Nest DI
Guard vs middleware?	Guards have ExecutionContext + route metadata
Pipe purpose?	Transform/validate handler arguments
Interceptor purpose?	Wrap handler execution with RxJS
TestingModule?	Utility to compile DI graph for tests

Deeper Prompts

How does forwardRef help circular dependencies, and when should you avoid it?
How do you implement RBAC with Reflector and custom decorators?
How would you structure ConfigModule validation for required secrets?
How do message patterns differ from event patterns?
How do you override providers in e2e tests?

Talk in Trade-offs

Senior interviews reward trade-off language: Fastify vs Express, Prisma vs TypeORM, JWT vs sessions, monolith vs microservices—for Nest specifically.

Common Mistakes

Memorizing decorator names without pipeline understanding.
Being unable to debug a DI error explanation.
Confusing guards, pipes, and interceptors.
Ignoring testing questions.

Key Takeaways

Interviews test Nest mental models: DI, modules, pipeline.
Practice explaining request order and auth wiring.
Prepare trade-offs for ORM, transport, and architecture choices.
Be ready to describe TestingModule overrides.

Pro Tip

Rehearse drawing the Nest request pipeline on a whiteboard from memory—it unlocks half of Nest interview conversations.

Extended NestJS Interview Q&A

Longer answers for common Nest interview prompts.

1. What problem does NestJS solve compared to Express?

Express is unopinionated. Nest adds modules, DI, and decorators so large TypeScript backends share a consistent structure, improving testability and team scalability while still running on Express or Fastify.

2. How does dependency injection work in Nest?

Nest inspects constructor types/tokens, looks up providers registered in modules, constructs them (resolving nested deps), and injects instances. Tokens can be classes, strings, or symbols.

3. Difference between guard, pipe, and interceptor?

Guards decide whether a request proceeds (authz). Pipes transform/validate arguments. Interceptors wrap handler execution (logging, caching, response mapping) using RxJS.

4. How do feature modules share services?

Export the provider from the owning module and import that module where needed. Importing alone is insufficient without exports.

5. How do you validate request bodies?

Use DTO classes with class-validator and enable ValidationPipe globally with whitelist/transform options.

6. How do you unit test a Nest service?

Build a TestingModule that provides the service and useValue mocks for dependencies, then assert behavior with Jest.

7. What is a dynamic module?

A module that returns configuration at runtime via forRoot/register so consumers can supply options (API keys, URLs) when importing.

8. JWT auth flow in Nest?

Validate credentials, sign a JWT with JwtService, protect routes with a Passport JWT strategy + AuthGuard, and attach the user in validate().

9. Message pattern vs event pattern?

Message patterns are request-response (send). Event patterns are fire-and-forget (emit).

10. How do you avoid N+1 in GraphQL Nest resolvers?

Batch nested lookups with DataLoader (or equivalent), avoid per-item queries in field resolvers, and paginate list fields.