Interview Questions: Teamwork
Workflows and good habits.
The last group of questions is about how you work with others. There's no single right answer here. Interviewers want to hear that you think about your teammates.

- How you work with others
- No single right answer
- Show you think about teammates
Describe your workflow
Question ten. Describe your Git workflow. A great answer walks through GitHub flow. Pull the latest main. Create a feature branch. Make small commits with clear messages. Push, and open a pull request. Respond to review. Merge, and delete the branch.
- Pull mainstart fresh
- Branchone per task
- Commit & pushsmall, clear
- PR & mergeafter review

What makes a good commit?
Question eleven. What makes a good commit? It does one thing. It has a short, clear message, starting with a verb, explaining what and why. It doesn't break the build. And it never contains secrets, or generated files.
Have you ever force pushed?
Question twelve. When is it okay to force push? Only to your own branch, that nobody else is using, for example after a rebase. Prefer force with lease, which refuses if someone else pushed in the meantime. And never force push a shared branch like main.
Summary
Describe GitHub flow, explain good commits, and show you'd never force push shared work. You're ready for most Git interviews. Next, a few trickier questions that catch people out.
Key takeaways- GitHub flow
- Good commits
- Force push with care