Describe the Git and code review workflow you follow when building a feature on a team.
What the interviewer wants to hear
- Create a short-lived feature branch from main
- Make small, focused commits with clear messages
- Open a pull request with context, screenshots and test notes
- CI runs lint, type checks and tests before merging
- Respond to review feedback and keep the branch up to date
Model answer
I start by pulling the latest main and creating a short-lived branch named after the ticket. I work in small commits with clear messages, so each one is easy to understand and to revert. I try to keep the pull request small, ideally one feature or fix, because big PRs get shallow reviews. When I open it I explain what changed and why, link the ticket, add screenshots for UI changes and describe how I tested it. CI runs linting, type checks, unit tests and a preview deployment, and I fix anything red before asking for review. I treat review comments as a conversation: I either make the change or explain my reasoning politely. Before merging I rebase or merge main to resolve conflicts, then squash-merge and delete the branch so main stays clean and deployable.
Can you answer it under time pressure?
Take a timed easy round and get scored on every answer.
More easy Full Stack Developer questions
- What happens, step by step, when a user types your app URL into the browser and presses Enter?
- Design the REST API endpoints for a simple blog with posts and comments. What URLs, methods and status codes would you use?
- What is the difference between authentication and authorization? Give an example from a web app.
- You are starting a new e-commerce app. Would you choose a SQL or a NoSQL database, and why?
- Explain client-side rendering, server-side rendering and static site generation. When would you use each?
- In a web app with a React frontend and an API, where should input validation happen, and why?
- A page loads data from your API. How do you handle loading, empty and error states so users are never left confused?
- How do you manage configuration and secrets across development, staging and production for a full-stack app?
- How would you explain a database index to a junior developer, and how do you decide which columns to index?