How do you create a new Next.js project?
Assesses fundamental understanding of Next.js conventions, runtime behavior, and memory/performance considerations.
Hiring managers look for precision, avoidance of ambiguous jargon, and ability to explain trade-offs under real production conditions.
The officially supported and recommended way to scaffold a new Next.js application is using create-next-app:
npx create-next-app@latest
### Interactive Setup Wizard Options:
Running this command prompts an interactive configuration CLI where you can select:
- Project Name: e.g.,
my-next-app - TypeScript: Enables end-to-end static type checking (highly recommended for production).
- ESLint: Configures code quality rules out of the box.
- Tailwind CSS: Pre-configures Tailwind styling and PostCSS.
src/directory: Keeps code organized insidesrc/rather than project root.- App Router: Uses Next.js's modern routing architecture (recommended over legacy
pages). - Import Alias: Configures
@/*path mapping for clean imports.
### Non-Interactive One-Liner for Automated CI/CD:
npx create-next-app@latest my-app --typescript --tailwind --eslint --app --src-dir --import-alias "@/*"
Candidate Response Strategy & Interview Tips
- Start with a concise one-sentence summary: Deliver a direct, confident answer first before expanding into nuances.
- Demonstrate real-world trade-offs: Discuss where this approach excels and when you would avoid it in production systems.
- Discuss complexity & edge cases: Proactively explain time/space complexity or boundary conditions (null values, scale limits).
- Prepare for interviewer follow-ups: Technical hiring panels frequently probe deeper into concurrency, backward compatibility, or alternative libraries.