What's your responsibility when only frontend work remains?

WHAT THIS TESTS: This question probes your understanding of team accountability in an Agile/Scrum context. It's not about your frontend skills. The interviewer is testing whether you see success as a team outcome (achieving the Sprint Goal) or an individual one (completing your assigned tasks). It reveals your attitude towards cross-functional collaboration and the Scrum value of commitment.

A GOOD ANSWER COVERS: A strong answer has a clear order of priorities. First, state that the entire team owns the Sprint Goal, so it's everyone's responsibility. Second, offer direct, practical help to the frontend developers, even as a backend specialist. This could be pairing on a simple task, manual testing, writing end-to-end tests (e.g., with Cypress or Playwright), reviewing PRs for logic, or improving their build tooling. Third, if direct help isn't feasible, offer to take on other work that frees them up, like handling customer support tickets or writing documentation. Fourth, as a last resort, propose productive work that benefits the team, like paying down tech debt or prototyping a future story, while making it clear this is only after exhausting all options to help the current sprint.

COMMON WRONG ANSWERS: The biggest red flag is saying, "I'd start working on tickets for the next sprint." This signals a "not my job" attitude and a fundamental misunderstanding of Scrum. Another poor answer is waiting passively for the Scrum Master to assign you work; Scrum teams are self-managing. Also, avoid blaming the situation on poor planning. While it might be true, a senior engineer focuses on solving the immediate problem first and brings up process improvements during the retrospective.

LIKELY FOLLOW-UPS: "What if the frontend developers say they don't have anything you can help with?" (A: I'd still try to find ways to contribute, like writing test plans, doing exploratory QA, or improving documentation. I'd also raise this as a team-wide impediment in the Daily Scrum). "How would you prevent this situation in the future?" (A: Suggest better task breakdown in Sprint Planning, encourage more cross-skilling, advocate for T-shaped engineers).

ONE CONCRETE EXAMPLE: "In a previous role, our sprint was blocked on a complex UI component. As a backend engineer, I couldn't write the React code, but I paired with the frontend dev and wrote all the Cypress end-to-end tests for the feature as they were building it. This let them focus purely on the component logic and we caught bugs in real-time. We still hit the Sprint Goal because we collaborated."