Where the wrong call can cost a year.

For technology companies and the people who lead their engineering. Each engagement starts with one decision and ends in a written call.

2practices

4engagements

Open any engagement to see what it covers.

Practice

Technical leadership and key talent

For founders, CEOs and engineering leaders

A written call on the people your roadmap depends on: the senior leader you are about to hire, and the engineers you cannot afford to lose.

Engagements
  • First we agree what the seat has to deliver. Then I run a leadership interview and take references, with the candidate’s consent, and read both against that bar. Your technical reviewer tests depth in a session we design together, and I set what they find beside what I learn about the person. The decision stays yours.

  • Where your roadmap rests on too few people, what is driving retention risk, and what to change to keep them. People tell an outsider what they will not tell their manager, so I have those conversations. Participation is voluntary, I report themes to leadership and never what any one person said, and leadership commits in writing that nothing from them is used against anyone. Most useful after a funding round, a reorg, an acquisition or a key departure.

Practice

An engineering team in Belgrade

For companies with a team in Belgrade, or weighing one

Your point of contact on the ground: whether to build, who to work with, and an independent look at the team once it is running.

Engagements
  • Whether the talent for your stack is in Belgrade, who you would compete with for it, and what it would take to hire and keep a team there. If the call is Build, I connect you with the right firms and people, with no referral fees, and stay your first point of contact as you set up.

  • I speak with the people who carry the work, and measure ownership, depth and retention risk against your own bar. You learn who you really depend on, what the vendor or team is delivering, and whether to keep the setup, fix it or replace it.

When the decisions keep coming.

Offered after a first engagement.

  • Hiring loops and offers reviewed as they come, and a quarterly read on the senior team, in themes and never names. For leadership teams who want the same judgment on every people decision, not only the first.

What I do not do

High-volume recruiting, code audits and architecture reviews, or company registration, legal and payroll in Serbia. For those, I introduce firms I trust.

What Belgrade offers a US team.

Serbia is easy to misjudge from abroad. These are the facts that change the decision.

  • 6 h

    The same working day

    Belgrade runs 6 hours ahead of New York, so the team works with you in real time.

  • Math

    A technical tradition

    Strong university training and a long record in mathematics and engineering, a strength few people outside the region know about.

  • English

    English at work

    The norm in technical teams, from daily work to reviews and references.

  • Nonstop

    Easy to reach

    Direct flights to New York, and short hops from every major European hub. Time in person with the team is easy to plan, and visitors are glad to come back.