Faysal Ahmed

Communication, Mentoring, and Influence Without Authority

careerseniorengineeringcommunicationmentoringleadership

Technical skill gets you to mid-level. Communication, mentoring, and influence get you to senior — and beyond. These are often called “soft skills,” but there’s nothing soft about them. They are hard, learnable skills that determine your ability to multiply your impact through others.

Technical Communication

At the senior level, your primary output is no longer code — it’s decisions. And decisions are made through communication.

Writing design docs: A good design doc is the most effective way to align a team on a technical decision. Structure yours like this:

  • Context and motivation — What problem are we solving? Why now?
  • Goals and non-goals — What’s in scope and what’s explicitly out of scope
  • Proposed solution — The architecture, key decisions, and rationale
  • Alternatives considered — What else was evaluated and why it was rejected
  • Trade-offs and risks — What are we sacrificing and what could go wrong

Running effective meetings:

  • Always have an agenda (even if it’s 3 bullet points)
  • Start with the goal: “By the end of this meeting, we need to decide X”
  • End with clear action items and owners
  • Send a brief summary within an hour

Presenting to leadership:

  • Lead with the recommendation, then the supporting data
  • Know your audience — executives care about timeline, cost, and risk
  • If something is going wrong, communicate it early. Bad news doesn’t get better with time.

Mentoring Junior Engineers

Mentoring is not an optional activity for senior engineers — it’s a core responsibility. Your team’s output is your output.

Effective mentoring patterns:

  • Pair on ambiguous tasks — Don’t just give answers. Walk through your thinking process out loud. Let them see how you approach unknowns.
  • Review code with context — Instead of “this should be a map,” say “using a map here makes the lookup O(1) instead of O(n), which matters because this function is called on every request.”
  • Assign ownership early — Give juniors ownership of a small feature end-to-end. Support them, but let them drive.
  • Teach debugging methodology — Don’t fix the bug for them. Walk them through how to isolate the root cause.

What not to do:

  • Don’t assign mentees only grunt work — they need growth opportunities
  • Don’t rewrite their code without explaining why
  • Don’t wait until they ask for help — check in proactively

Influence Without Authority

As a senior engineer, you will frequently need to drive decisions that involve people who don’t report to you: other teams, product managers, designers, leadership. You can’t tell them what to do — you have to influence them.

Building influence:

  1. Earn trust through competence — Deliver consistently. Be reliable.
  2. Understand their incentives — Why would this person want to help you? What’s in it for them?
  3. Frame decisions in terms of shared goals — Instead of “I need you to do X,” try “We both want the system to be reliable. Here’s how X helps us get there.”
  4. Build relationships before you need them — Have coffee with teammates from other teams. Comment on their design docs. Be helpful without expecting immediate returns.
  5. Be wrong publicly — Admitting mistakes builds more trust than pretending to be infallible.

Handling disagreement: When you disagree with a technical decision:

  1. Understand the other position first — ask questions until you can articulate their argument better than they can
  2. State your disagreement clearly and respectfully
  3. Propose a concrete alternative
  4. If the decision goes against you, commit to it fully (disagree and commit)

The Leverage Multiplier

Every hour you spend improving the people around you — through mentoring, documentation, better processes, or clearer communication — compounds. That hour might not produce immediate output, but it makes everyone on your team more effective going forward.

This is the defining leverage of a senior engineer: you don’t just do the work; you make everyone around you better at doing the work.

Key Takeaways

  • Senior engineers communicate to drive decisions, not just to share information
  • Mentoring juniors is a core responsibility, not an optional side activity
  • Influence is built through trust, understanding others’ incentives, and framing decisions around shared goals
  • Your force multiplier is making your team more effective