97How would you evaluate a coding agent, and why is a single SWE-bench score not enough to trust it?▼hardNewOpenAIAnthropicCognition◆ premiumCandidates who cite one leaderboard number fail the follow-up. The interviewer wants you to name what SWE-bench measures, what it cannot (long-horizon multi-file refactors, real tool use, business logic), and which complementary benchmarks close those gaps.Open full answer →
103Your team merges 50 agent-written PRs a week and review is the bottleneck. Design the review workflow.▼expertNewGoogleGitHub◆ premiumAgent PR volume scales with compute; human review capacity does not. Most candidates answer 'add an AI reviewer' and miss the real design problem: deciding which changes deserve human judgment at all. Interviewers want a risk-tiered pipeline you would trust in production.Open full answer →
104Claude Code ships with no codebase index while Cursor trains custom embeddings. Which repo-context strategy do you pick, and when?▼hardNewAnthropicCursor◆ premiumTwo frontier coding agents made opposite bets on the same problem, and both published evidence. Candidates who pick a side on vibes miss what the interviewer wants: the axes that actually decide it, and what each choice costs in staleness, latency, tokens, and infrastructure.Open full answer →
