🧩 How do you usually **distribute work among** developers on your team?, 👀 What’s the strangest excuse you’ve **come across** for missing a deadline?, 🤝 Would you rather work with a brilliant developer who is difficult to **get along with**, or an average developer who is a great teammate?, 📦 When is it reasonable to **pass on the workload to** another developer, and when does it become unfair?, 🔍 When a project goes wrong, is it more useful to **pinpoint** who made the mistake or why it happened?, 📋 How often do you have to **submit a report** on your team’s progress or performance?, 🙄 How can you tell whether someone is explaining a genuine problem or **making excuses**?, 🚨 What behaviour do technically strong developers sometimes **get away with** that other employees wouldn’t?, 💥 Should admitting a mistake immediately reduce the **consequences** someone faces? Why or why not?, 🔔 What can **disrupt the workflow** more: unexpected meetings, changing requirements, or slow code reviews?, 🤐 Why do colleagues sometimes **talk behind someone’s back** instead of addressing a problem directly?, 🚪 Would you **quit** a well-paid job if you were constantly expected to fix other people’s mistakes?, 🦸 Can always **picking up the slack** make you a worse teammate in the long run?, 🎯 If you lost motivation at work, what would help you **get back on track**: a new challenge, a break, or an honest conversation?, 💬 Does the saying “If you want something done properly, do it yourself” **resonate with you**?, 🧯 If a junior developer **messes up** in production, what should their senior colleague say to them first?, 🤝 How can a junior developer **contribute to** a team in ways that a senior developer might not?, 👀 How would you react if you **found out** that a colleague had been taking credit for your work?, 🎯 How do you **set goals** for yourself when urgent requests keep changing your priorities?, 🗣️ How **upfront** should you be with your manager if you think a deadline is unrealistic?, 🌳 How do you react when someone **beats around the bush** instead of getting straight to the point?, 🙋 How should a tech lead **acknowledge a mistake** without losing the team’s trust?, ⚖️ Do you think everyone on your team does their **fair share of the work**?, ⏳ Is “I didn’t have time to write tests” ever **an acceptable excuse**?, ❓ What would you want to **clarify** before agreeing to take ownership of an unfamiliar service?, 🙋‍♂️ How easy is it to **voice your thoughts** in a meeting when everyone else seems to agree on a solution you think is wrong?, 📉 Before describing a developer as **underperforming**, what should a manager investigate?, 🧠 What might a senior developer still **struggle with**, even after ten years of experience?, 📊 If you could remove one metric from developer **performance** reviews, what would it be — and what would you replace it with?

qqq

by
Print
Embed

Leaderboard

Visual style

Options

Switch template

Continue editing: ?