What do you do when only frontend work remains in a sprint?
This tests your commitment to team ownership over role specialization. A great answer prioritizes the Sprint Goal, offers to help the frontend devs directly (pairing, testing), and finds other ways to unblock them.
What's really being asked
This question assesses your understanding of core Scrum principles, specifically team ownership and cross-functionality. The interviewer is looking for a "we" versus "me" attitude. They want to see if you prioritize the team's shared commitment to the Sprint Goal over your individual role as a "backend specialist." It's a test for a "T-shaped" engineer who contributes beyond their core expertise.
The full answer
A strong answer demonstrates proactivity and a focus on the team's success. First, explicitly state that the entire team owns the Sprint Goal. Second, communicate with the overloaded frontend developers and ask how you can help. This could be pairing on a simple component, writing unit/integration tests for their code, or handling manual QA. Third, offer to take on non-coding tasks to free them up, like code reviews, dependency updates, or clarifying requirements with the PO. Finally, if you cannot contribute directly, use the time to improve shared infrastructure, like CI/CD pipelines or end-to-end test frameworks, which benefits the whole team's future velocity.
The mistakes people make
The most common red flag is a siloed mindset. Saying "I'd pull in a ticket from the next sprint" or "There's nothing for me to do, so I'd focus on my own refactoring" shows a fundamental misunderstanding of Scrum. According to the Scrum Guide, the entire team commits to the Sprint Goal, and "Developers" are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint. Another mistake is waiting to be assigned a task. A senior engineer is expected to proactively find ways to contribute to the team's goal.
What usually comes next
"What if you don't know the frontend framework at all? How would you help then?" (Answer: Focus on non-framework tasks: writing tests, documentation, API contract validation, manual testing, CI/CD improvements). "What if the frontend developers say they don't need help?" (Answer: Trust but verify. Ask if you can shadow or review their PRs to learn the codebase. If they're truly unblocked, pivot to high-value team improvements).
A concrete example
"In a previous sprint, our two frontend engineers were struggling to finish a new settings page with 3 days left. As a backend dev, I couldn't write React code. So, I first took over all their PR reviews to unblock their merge queue. Then, I wrote the complete Cypress end-to-end test suite for the new page based on the acceptance criteria. This freed them up to focus purely on implementation, and we delivered the feature on time."
Interview question
A backend developer finishes all tasks early in a sprint, and only frontend work remains to achieve the Sprint Goal. What is the best immediate action?
- a.Wait for the Scrum Master to assign a new task, as you lack specific frontend development skills.
- b.Use the remaining time to refactor existing backend code or explore new technologies relevant to your specialization.
- c.Start on a high-priority backend story from the upcoming sprint to get a head start on future work.
- d.Proactively engage with the frontend team to offer help with testing, reviewing, or non-coding tasks to unblock them.Correct
Why? this is the answer
The correct answer emphasizes team ownership and proactivity towards the Sprint Goal, even if it means contributing outside one's primary specialization. Options B, C, and D reflect a siloed mindset, prioritizing individual work or waiting for direction, which contradicts Scrum principles.
Just read this? Test yourself on what you have been reading.
Read the original → scrumguides.org
Put your scrolling time to good use
Learn one idea, try a quiz and save useful cards for revision. Tezvyn makes it easy to learn and stay current in your tech field, a few minutes at a time.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on agile — each one lists the topics its interview covers.
See open roles