CF Expert but bombed my first real interview. interviewer said 'communication'. what does that even mean for a coding round?
ok so. codeforces expert (1680), ICPC regionals twice. first internship interview yesterday, dhaka product company, panel was remote from singapore. problem was a medium graph thing. had the idea in 2 min, coded it in 8, passed all their cases. feedback today: "strong problem solving, weak communication, no hire." bro WHAT. i solved it. faster than anyone they've probably seen. what do they want, a ted talk? also…
Accepted answer
Mahin, I'll be honest because I know you can take it. On Codeforces, a judge reads your code. In an interview, a human is scoring HOW you got there, because on the job your teammates have to follow your reasoning in design docs and code reviews. What "communication" means concretely on their rubric: 1. Restate the problem and ask 1-2 clarifying questions (directed? weighted? can it be disconnected?), even if you already know. 2. Say the brute force in one sentence, and why it's too slow. 3. Say the idea before coding: "multi-source BFS, because...". 4. Narrate lightly while coding. Not a TED talk, just signposts. 5. Dry run a small example before saying "done". Give the complexity without being asked. 6. Readable names, no macros. You're writing for a reader now, not a judge. Your speed is a huge asset. Slow down to 70% and spend the saved time on 1, 2, 3 and 5. You'll be a strong hire everywhere. And yes, I'm still saying LeetCode-style interviews are their own skill 😄 You can be much better than me at CF and still need this.- Very common with strong CP folks. You think in jumps, interviewers grade steps. Practise by recording yourself solving one problem a day out loud, 10 minutes. Painful to watch, very effective.