Every engagement ends in a written call.

A memo for the people deciding, with my name on it: the call, the evidence behind it and what would change my mind.

  1. 01

    Frame

    One call on the decision in front of you and what good looks like. If we fit, I send a short written scope with a clear deliverable and a fixed fee, and we agree the bar before I meet anyone.

  2. 02

    Test

    For a finalist: a leadership interview, references with consent, and a technical session with your reviewer, designed together and weighed alongside what I learn about the person. For a team or your key people: conversations in confidence with the people who carry the work.

  3. 03

    Call

    A clear answer, such as Hire, Do Not Hire or Wait for a finalist, or Keep, Fix or Replace for a team, with my reasons and what would change my mind. Then a live walkthrough.

The scope sets the timeline, and a finalist moves at the pace of your search. I take on a small number of engagements at a time, so each has my full attention. Remote by default, in US hours until 6pm Eastern, and in person when it matters.

See a sample for

From Leadership Diligence

Sample memo

Confidential

To
CEO and board
Re
Head of Engineering finalist
Stage
Series A, 5 engineers
Basis
Leadership interview, technical session with your reviewer, 4 references
HireDo Not HireWait

Do not extend the offer this week.

A strong manager of a team of 20, and the wrong first seat. This role is the build, not the run.

What I found

Against the bar

  • Builds from zero

    Gap

    Every team they led was inherited. No reference describes a first hire.

  • Fit for the next 12 months

    Gap

    The seat is the next 6 hires and the platform, hands on.

  • Technical read

    Adequate

    Sound on trade-offs. Your reviewer found the data-platform answers thin.

  • Hiring bar

    Strong

    Closed 9 of 11 senior offers last year. 2 references name the bar they held.

1 Strong1 Adequate2 Gap

What would change the call

A founding engineer first, with this seat opened at 12 to 15 engineers. Or a reference who watched them build a team from nothing.

Next step

Keep the finalist warm without a date. I walk you and the board chair through it live.

Uroš Majstorović

44 Parallel Partners

Read my story
Invented examples. A real memo covers every area in depth, with the evidence behind each rating, and stays with the client.

What I judge, and what I don’t.

My work sits on the people side of engineering. Technical depth is judged by an engineer you trust.

I judge

  • Leadership and judgment
  • Track record and references
  • How someone works with others
  • Fit with your stage
  • Retention risk
  • The cost of getting it wrong

Your technical reviewer judges

  • Code and architecture
  • Systems design
  • Depth in your stack

Usually that reviewer is you, or an engineer on your team. We design the session together, and I weigh what they find. If you do not have a reviewer, we settle it in the scope, before the first conversation. If depth cannot be covered, I will say so rather than guess.

What you can count on.

Everyone is held to the same bar, and everything I write stays with your team after I leave.

  • No placement or referral fees

    A fixed fee for judgment. Never a percentage of salary, and never paid by the firms I recommend.

  • Your people stay off-limits

    I never recruit your employees for other roles or other clients.

  • I work for the company

    The company is my only client in the room. A candidate or a vendor may be the subject of my work, never the party I answer to.

  • Confidence kept

    What your team tells me in confidence is never attributed by name. Leadership hears my judgment and the patterns.