How would you run a mentoring-focused code review?

Scenario

You are handed a poorly written frontend code change—for example, a React/TypeScript component along with its related state and API calls—produced by a junior engineer. The code works, but it is hard to maintain.

Task

Conduct a code review and explain:

1. What issues you would point out, ordered by impact: correctness, security, performance, accessibility, maintainability.
2. How you would communicate feedback so the junior engineer learns, including tone, framing, and asking questions versus prescribing fixes.
3. What concrete refactors you would suggest, such as component structure, state management, separation of concerns, naming, typing, and error handling.
4. What tests you would add or request—unit, integration, UI/e2e—and the behaviors they should cover.
5. How you would follow up after the review, including pairing, documentation, conventions, and future prevention.

Assume you can ask clarifying questions about requirements and constraints.

Overview

This question evaluates mentoring-focused code review competencies, including code quality and maintainability analysis, frontend architecture in React/TypeScript, testing strategy, accessibility and security awareness, and written and interpersonal feedback skills.