Every business starts with one idea. Clear, bright, and yours…

↓

…and at first it is simple. A point of light. You know what it should do, who it is for, and why it matters.

Then the research begins. Agencies, freelancers, platforms, quotations, and a random, unmaintained chat thread for every conversation. Every answer raises three new questions, and the clear point becomes a cloud of half-decisions that nobody has written down.

Somewhere inside that cloud is one decision the rest depends on. Not the framework, not the budget, not the deadline. Who you hire first.

Get the first few people right and almost everything else is recoverable. Get them wrong and you lose two years finding out, usually while paying for it.

And this is the hard part when you are not technical yourself. You cannot judge what you cannot do. From the outside, a convincing answer and a correct one sound exactly the same.

So we wrote down everything we know about hiring technical people. Role briefs, interview kits, scorecards a non-technical interviewer can actually score, the first ninety days. All of it is free. Take it and use it.

And when it is time to interview, we join the call with you. We ask the technical questions you cannot, we score alongside you, and afterwards we tell you plainly what we heard.

Then the team is yours — and so is the judgement. The next one is a hire you can make without us, which was the point all along.

ITCHEEZ.Services & charges ↓
Free resources · and one paid thing

Everything we know about hiring, given away.

Founders without a technical background lose years to their first few hires, and almost nothing written about it is any use when you are actually in the interview. So we wrote what is. Take all of it, use it, change it, put your own name on it. Nothing to sign up for.

  1. Free

    The role brief

    A role you cannot describe is a role you cannot interview for.

    • Levels in plain words, and what each actually delivers unaided
    • How much of your week each level will need
    • Must-haves, nice-to-haves, and what is explicitly not required
    • How you will know at 30, 90 and 180 days that it worked
    Download the role brief ↓
  2. Free

    The interview kit

    Questions you can ask, and judge the answers to, without being technical.

    • A sixty-minute shape, with what to look for in each part
    • Questions with what a good and a weak answer sound like
    • An exercise built from your own Tuesday, not a puzzle
    • The four things not to do, and the one that costs a year
    Download the interview kit ↓
  3. Free

    The scorecard

    Filled in during the conversation, because memory rearranges itself afterwards.

    • Four-point scoring with no middle, so nobody can sit on the fence
    • Evidence in their words, not your impression
    • Red flags worth a conversation, and the three that are a no
    • Why there is no “maybe” — a maybe is a no with extra steps
    Download the scorecard ↓
  4. Free

    The first ninety days

    The hire is not finished at the offer. This is where most of them are lost.

    • What to have ready before day one
    • What to check at thirty, sixty and ninety days, against the brief
    • How to hold the honest conversation early instead of at day 85
    • What to learn from it, whichever way it goes
    Download the ninety-day plan ↓
Download all four ↓ Four PDFs, about a megabyte. No email, no sign-up, no follow-up sequence — take them and go.

And if you would rather not judge the answers alone

BeforeWe write the role brief with you and build the interview kit and scorecard around itA role you could hire for without us next time
On the callWe join every interview, ask the technical questions you cannot, and score alongside youA written score per candidate, with the evidence
AfterWe tell you plainly what we heard, including when the honest answer is that none of them are rightA decision you can defend in a year
ThenA ninety-day plan for whoever you hire, and a review at the end of itSomebody the business can rely on

We are two people and we take a small number of these a year, because sitting in interviews properly is not something that scales. Candidate sourcing is yours or your recruiter’s — we are there for the judgement, not the pipeline. We do not take development contracts, so there is nothing we are quietly hoping to sell you afterwards.

What it costs

The resources are free and always will be. The only thing with a price is us being on the call. Everything happens over video, wherever you are.

Everything aboveRole brief, interview kit, scorecard, ninety-day plan. No sign-up, no email, no drip sequence. FreeFree
A conversation about the roleHalf an hour. What you are actually hiring for, and whether you need us at all. Often you do not. FreeFree
On the call, per role the only paid thingThe brief written with you, the kit and scorecard built for it, up to six interviews we join and score, and the ninety-day plan for whoever you hire. ₹45,000$599
A second role, same searchHiring two people at once is mostly the same work twice, so it should not cost twice. ₹25,000$349
The ninety-day reviewOptional, at the end. Against the brief, not against a feeling — and honest when it is not working. ₹12,000$159

Indian clients add 18% GST. Half on booking, half after the last interview. We work remotely only — every session and every interview is a video call, which is why we can do this for a company anywhere and why it costs what it does. If we join the interviews and you hire nobody, that is a normal outcome and the fee stands — you paid for the judgement, not for a hire. Every brief, kit and scorecard is yours to keep and reuse for every role after this one. We do not take a percentage of anybody’s salary, and we are not a recruiter.

Why us on the call

Nine years building and running production systems, and still building them. We ask the questions we would want asked of ourselves, and we can tell the difference between an answer that is correct and one that is merely confident:

  • React
  • Node.js
  • Python
  • PostgreSQL
  • Redis
  • job queues
  • WebSockets
  • Claude Agent SDK
  • MCP
  • embedding models
  • vector search
  • speech to text
  • GPU workers
  • Docker
  • nginx
  • object storage
If you are hiring

Take the kit. Write if you want us on the call.

The resources are free and always will be. If you have a technical role open and would rather not judge the answers alone, tell us about the role and we will say honestly whether we can help. We work entirely remotely, so where you are does not matter.

Write to ushello@itcheez.com →

We reply within one business day, and we take a small number of these a year. ITCHEEZ on LinkedIn →