Git Branching Strategy
Also written as Gitflow, Feature Branching
A team's agreed convention for how code branches, merges, and releases — e.g. Gitflow's long-lived develop/release branches, versus trunk-based development's short-lived branches merged into main frequently.
Think of it like
Like a shared kitchen's rule for how many dishes can be 'in prep' on separate stations before they all have to come together on the pass — some kitchens run many stations at once, others push everything through one line fast.
Junior or senior?
Junior sounds like
Name-drops 'Gitflow' without explaining why.
Senior sounds like
Can explain why their team's specific branching strategy fit their release cadence and team size.
Ask them
“What branching strategy did your team use, and what made it the right fit for how often you released?”