Node.js Easy technical 0 views 1 min read

Explain middleware in Express.

Peer-reviewed by HireXTech Technical Panel • Updated for 2025/2026 hiring • Editorial standards
Practise this track
Interviewer Expectations for this Question
01
Core Competency

Assesses fundamental understanding of Node.js conventions, runtime behavior, and memory/performance considerations.

02
Evaluation Criteria

Hiring managers look for precision, avoidance of ambiguous jargon, and ability to explain trade-offs under real production conditions.

Comprehensive Model Answer Verified Solution

Middleware are functions with the signature (req, res, next) that run in order and can inspect or modify the request/response, end the cycle, or pass control with next().

  • Application-level: app.use(logger).
  • Router-level: router.use(auth).
  • Error-handling: four arguments (err, req, res, next), registered last.
  • Built-in: express.json, express.static.
  • Third-party: cors, helmet, morgan.
app.use((req, res, next) => {
  req.startedAt = Date.now();
  next();
});

app.use((err, req, res, next) => {
  console.error(err);
  res.status(500).json({ error: 'Internal error' });
});

Order matters: authentication and parsing must precede routes that depend on them.

Candidate Response Strategy & Interview Tips

  1. Start with a concise one-sentence summary: Deliver a direct, confident answer first before expanding into nuances.
  2. Demonstrate real-world trade-offs: Discuss where this approach excels and when you would avoid it in production systems.
  3. Discuss complexity & edge cases: Proactively explain time/space complexity or boundary conditions (null values, scale limits).
  4. Prepare for interviewer follow-ups: Technical hiring panels frequently probe deeper into concurrency, backward compatibility, or alternative libraries.
Related Topics & Skills
Spotted an error or have an alternative solution?