Architecture scenarioMedium~7 min

Interview question

How would you use route groups without changing public URLs?

Uses route groups for organization and layout boundaries while accounting for URL collisions and full reloads across roots.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

A folder such as (marketing) or (app) groups routes without adding that folder name to the URL. I use groups to organize teams or features, opt selected routes into a shared layout, or create separate root layouts for distinct application shells. Because the group is omitted from the URL, two groups cannot both resolve to the same final route.

Full answer below

Practice focus

App Router folder conventions, root layouts, URL stability, organization, and navigation behavior.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Overview
Parentheses organize routes and layout ownership, but they do not become URL segments.
A folder such as (marketing) or (app) groups routes without adding that folder name to the URL. I use groups to organize teams or features, opt selected routes into a shared layout, or create separate root layouts for distinct application shells. Because the group is omitted from the URL, two groups cannot both resolve to the same final route.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
A useful structure might put /pricing under a marketing layout and /account under an authenticated product layout while preserving those clean URLs. If the top-level app/layout is omitted, each group can define its own root layout with its own html and body. Navigation between different root layouts performs a full page load, so I do not split roots only for folder tidiness. I keep private implementation folders and colocated files distinct from route groups because they solve different organizational problems.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
Before introducing groups, I map final URL ownership, layout state lifetime, error boundaries, metadata inheritance, and deployment analytics. Moving a route into a group should not alter its canonical URL, but it can change which layout and loading boundary wraps it. I add route-level tests for representative URLs and a navigation test across roots so the full-document transition is deliberate. If two product areas need shared client state or seamless transitions, one root with nested layouts is usually a better boundary than multiple roots.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Assuming the group name appears in the browser URL.
Creating colliding routes in different groups.
Splitting root layouts without considering full page loads.

Red flagsCandidateRed flagsSignals that an interviewer may treat as risky.Open details

Details

A refactor silently changes layout or metadata inheritance.
Two folders compile to the same public path.
Shared state is expected to survive navigation across roots.

Follow-up prompts

Quick interviewer prompts inside this drill.

Follow-up questionsCandidateFollow-up questionsLikely next questions after the main answer.Open details

Details

Treat these as the next interviewer turn. Answer one out loud, then save the gap in your practice notes.

Do route groups affect canonical URLs?
When does navigation cause a full reload?
How are private folders different?

Continue practice

Move to the linked follow-up, next path step, prerequisite, or deeper variant.

1 linked

Next interviewer turn

Continue the conversation with a linked follow-up drill.

Layout vs templateExtends layout ownership across larger route groups.

Practice route

Read core answer Review checklist Follow-up prompts Track progress

Finished this drill?

Practice freely. Sign in only when you want to save completion, confidence, notes, or bookmarks.

New to Aporeon? Create account

Drill details

Human editorial direction

Aporeon is shaped by Aleksandar Tomovski, a software developer with experience on both sides of technical interviews. Content is reviewed for accuracy, natural spoken delivery, useful depth, and honest trade-offs.

About the creator Editorial standards

Was this drill useful?

Help improve the interview library.

Found this answer useful?

Say thanks with a standalone, one-time $5 contribution. No account required.

No subscription or perks.Choose another amount

Opening drill

Architecture scenarioMedium~7 min

Interview question

How would you use route groups without changing public URLs?

Uses route groups for organization and layout boundaries while accounting for URL collisions and full reloads across roots.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

Full answer below

Practice focus

App Router folder conventions, root layouts, URL stability, organization, and navigation behavior.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Overview
Parentheses organize routes and layout ownership, but they do not become URL segments.
A folder such as (marketing) or (app) groups routes without adding that folder name to the URL. I use groups to organize teams or features, opt selected routes into a shared layout, or create separate root layouts for distinct application shells. Because the group is omitted from the URL, two groups cannot both resolve to the same final route.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
A useful structure might put /pricing under a marketing layout and /account under an authenticated product layout while preserving those clean URLs. If the top-level app/layout is omitted, each group can define its own root layout with its own html and body. Navigation between different root layouts performs a full page load, so I do not split roots only for folder tidiness. I keep private implementation folders and colocated files distinct from route groups because they solve different organizational problems.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
Before introducing groups, I map final URL ownership, layout state lifetime, error boundaries, metadata inheritance, and deployment analytics. Moving a route into a group should not alter its canonical URL, but it can change which layout and loading boundary wraps it. I add route-level tests for representative URLs and a navigation test across roots so the full-document transition is deliberate. If two product areas need shared client state or seamless transitions, one root with nested layouts is usually a better boundary than multiple roots.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Assuming the group name appears in the browser URL.
Creating colliding routes in different groups.
Splitting root layouts without considering full page loads.

Red flagsCandidateRed flagsSignals that an interviewer may treat as risky.Open details

Details

A refactor silently changes layout or metadata inheritance.
Two folders compile to the same public path.
Shared state is expected to survive navigation across roots.

Follow-up prompts

Quick interviewer prompts inside this drill.

Follow-up questionsCandidateFollow-up questionsLikely next questions after the main answer.Open details

Details

Treat these as the next interviewer turn. Answer one out loud, then save the gap in your practice notes.

Do route groups affect canonical URLs?
When does navigation cause a full reload?
How are private folders different?

Continue practice

Move to the linked follow-up, next path step, prerequisite, or deeper variant.

1 linked

Next interviewer turn

Continue the conversation with a linked follow-up drill.

Layout vs templateExtends layout ownership across larger route groups.

How would you use route groups without changing public URLs?

Practice focus

Answer path

Overview

Review signals

Follow-up prompts

Continue practice

Next interviewer turn

How would you use route groups without changing public URLs?

Practice focus

Answer path

Overview

Review signals

Follow-up prompts

Continue practice

Next interviewer turn