Asking for Help without Sounding Incompetent

In tech, everyone gets stuck. The difference between a junior and a senior is how they ask for help.

The "Proactive Help" Framework

When you ask for help, follow this structure:

1. The Goal: What are you trying to do?
2. The Problem: What is happening instead?
3. The Effort: What have you already tried?

Example: "I'm trying to deploy the staging branch (Goal), but the build is failing with a timeout error (Problem). I've already checked the logs and increased the memory limit (Effort), but it didn't solve it. Any ideas?"

Useful Vocabulary

• "I'm stuck on...": Use this instead of "I can't do..."
• "I've tried...": Signals you've put in effort.
• "I'm seeing a [error name]...": Be specific.
• "Does anyone have context on...?": A polite way to ask for information.
• "Could you point me in the right direction?": Asks for a hint rather than a full solution.

When to Ask?

The "15-Minute Rule":

1. Try to solve it yourself for 15 minutes.
2. Document what you tried.
3. If you are still stuck, ask for help immediately. Don't waste hours being stuck!

• depend on
• focus on
• listen to
• talk to / talk about
• ask for
• wait for
• belong to

Examples:

• We depend on your input for the next sprint.
• Let us focus on the most critical bug first.
• I will talk to the product manager about the timeline.

Common mistakes

Here are the errors I hear most often from non-native speakers:

• Incorrect: I am responsible of the backend.
  • Correct: I am responsible for the backend.
• Incorrect: We depend of your decision.
  • Correct: We depend on your decision.
• Incorrect: I am interested on this role.
  • Correct: I am interested in this role.
• Incorrect: She is good on presentations.
  • Correct: She is good at presentations.

Quick test

Fill in the blanks:

1. I work _ a fintech startup _ San Francisco.
2. Who is responsible _ the QA checklist?
3. We need to focus _ improving page load time.

Answers:

1. for, in
2. for
3. on