How to Hire Without an HR Team: A Practical Guide for Startup Founders

A study of 973 UK startups found that, on average, startups didn’t hire for an HR role until they had 40–50 employees. Which means that for most of your company’s early life, the period when every hire matters most and every mistake costs most, you are the recruiter, the interviewer, the offer manager, and the onboarding programme, all at once.

Most founders find this out the hard way. They post a job description, get flooded with irrelevant applications, spend three weeks interviewing people who are not quite right, make an offer to someone who declines, start again, and eventually hire someone out of exhaustion rather than conviction. Three months later, that person is gone. This guide is built to prevent that. Not with generic advice about “writing a good job description”, but with a specific, honest, step-by-step process that a technical founder can run without an HR background, without an HR team, and without losing three months of momentum every time they need to hire someone.

It is written specifically for tech startups hiring engineering and technical talent, because that is both the hardest category of role to hire without specialist support and the highest-stakes one. Get this right and you build momentum. Get it wrong and you burn runway, credibility, and your own time simultaneously.

Why Hiring Without HR Is Hard – and Why It Doesn’t Have To Be

The difficulty of hiring without HR is not that HR knowledge is inaccessible. It is that hiring is genuinely a full-time job, and you are already doing several of those.

When a company has a dedicated recruiter or HR function, that person owns the process end-to-end. They manage the job brief, write and post the description, source candidates, run the first screen, coordinate interviews, gather feedback, manage offers, and handle onboarding admin. That is easily 20-30 hours of work per open role, spread over three to six weeks.

As a founder with no HR support, you are absorbing all of that on top of everything else you are doing. The result is usually one of three failure modes.

1. Failure mode one: the reactive hire. You wait until the pain of the vacancy becomes unbearable, then hire the first person who seems good enough. “Good enough” is not a hiring standard. It is how you build a team of people who are wrong for the role but tolerable under pressure.
2. Failure mode two: the endless search. You have a vague idea of who you want but no precise brief, no structured process, and no evaluation framework. Every interview produces a different opinion. Weeks pass. The role stays open. Your existing team absorbs the workload and starts to resent it.
3. Failure mode three: the inconsistent process. You run a great process for one role and a chaotic one for the next, depending on how much time you have. You cannot reproduce your good hires because you cannot remember what made the process work.

The solution to all three is the same: a simple, repeatable process you build once and run every time. Not a complex HR system – a practical sequence of steps that produces consistent decisions even when you are operating under pressure.

Before You Post Anything: The Founder’s Pre-Hire Checklist

The most expensive hiring mistake a founder can make is starting the search before they know exactly what they need. This is also the most common one.

Run through these questions before you write a single line of a job description.

1. Do you actually need to hire, or do you need to solve a problem? Hiring is not the only answer to capacity problems. Before opening a role, ask whether the problem could be solved differently: redistributing responsibilities within the existing team, automating a process, bringing in a specialist for a defined project, or using a part-time contractor for a transitional period. Hiring a permanent employee is the most expensive, highest-commitment solution to a capacity problem. Be certain it is the right one before committing to it.
2. What specific outcome does this person need to deliver in their first 90 days? Not a job description – a concrete deliverable. “Improve backend performance” is not an outcome. “Reduce API response time from 800ms to under 200ms across three core endpoints” is an outcome. This level of specificity is what makes a brief precise enough to source against and interview against. If you cannot answer this question concretely, you are not ready to hire yet.
3. What does this role need to look like in 12 months? Startups scale fast and roles change faster. The engineer you hire today to build infrastructure may be managing a team of four in a year, or the role may be made redundant by a product pivot, or it may expand into a completely different technical domain. Understanding the 12-month trajectory of the role prevents you from optimising for today’s need at the expense of tomorrow’s reality.
4. What are your genuine must-haves versus nice-to-haves? Every founder, when asked what they are looking for, produces a list of twelve requirements. In reality, three or four of those are genuinely non-negotiable for the role to function. The rest are preferences. Knowing which is which determines whether you can fill the role in four weeks or four months. The longer your must-have list, the smaller your candidate pool. Be honest with yourself about what is truly essential.
5. What is the real budget, including total employer cost? Salary is one number. Total cost is another. For a permanent employee, add employer social security contributions, any mandatory benefits, equipment, software licences, and onboarding time cost. For a B2B contractor in Poland, the invoiced amount is your complete cost. Know the real number before you set compensation expectations, because adjusting them mid-process loses candidates.
6. What is your hiring timeline, and is it realistic? Senior engineers typically have notice periods of one to three months. A role that needs to be filled by a product deadline needs recruiting six to ten weeks before that deadline, not two. Map the timeline backwards from when you need someone in the seat, and start the process early enough to actually get there.

Step 1: Write a Job Description That Attracts the Right People, and Repels the Wrong Ones

Most startup job descriptions are written to attract as many applicants as possible. This is the wrong goal. The right goal is to attract specifically the people who will succeed in this role, and deter everyone else. Volume of applications is not a metric – quality of shortlist is.

A job description that actually works has five components.

1. The opening: why this role exists and what problem it solves. Not a company description. Not a list of values. The first paragraph should answer the question a strong candidate is asking when they read any job post: “Why does this role matter, and why should I care?” Write one to three sentences that explain what this person will solve and what the work will actually look like. “You will own the design and implementation of our core payment infrastructure as we scale from 10,000 to 500,000 transactions per month” is a real opening. “We are a fast-growing startup looking for a passionate engineer to join our team” is not.
2. The actual responsibilities in plain language. List what this person will genuinely do, week to week. Not aspirational responsibilities that sound good in a job ad – actual tasks. Be specific about the technical domain, the team they will work with, the decisions they will own, and the scope of their autonomy. Experienced candidates can tell the difference between a role description written by someone who understands the work and one written by someone who does not. The former builds credibility. The latter raises flags.
3. Requirements: separated into must-haves and nice-to-haves. Keep your must-have list short – three to five genuinely non-negotiable criteria. Everything else goes in a clearly labelled “nice-to-have” or “bonus” section. This matters because research consistently shows that women and underrepresented candidates are less likely to apply when they do not meet every listed requirement. Separating must-haves from preferences significantly widens your candidate pool without reducing quality.
4. What you are offering in concrete terms. Salary range, engagement model (employment vs. B2B), equity if applicable, working arrangement (remote, hybrid, office), equipment, and any relevant benefits. Founders often omit salary ranges to maintain negotiation flexibility. This is a mistake. Candidates who do not know the salary range apply speculatively and drop out at offer stage, wasting everyone’s time. A disclosed range filters for fit, not just interest.
5. The honest version of what working here is like. What is the team culture actually like? How are decisions made? What does a typical sprint look like? What does a bad week feel like? Candidates who have been in the workforce for more than two years are extremely good at detecting the gap between what a company claims its culture is and what it actually is. An honest, specific description of your working environment attracts candidates who will thrive in it – and deters those who will not.

Step 2: Where to Find Candidates When You Have No Recruiting Pipeline

Without an HR team and without a dedicated recruiting function, your sourcing options are more constrained than a specialist recruiter’s, but not as constrained as most founders assume.

• Your network – used deliberately, not casually. A LinkedIn post announcing a role is not sourcing. Direct, personal messages to specific people in your network asking whether they know someone who fits a specific profile is sourcing. The distinction is the difference between hoping the right person sees your post and actively hunting for them. Work through your first and second-degree network methodically, and ask for referrals from people whose professional judgement you trust. A referral from a strong engineer is worth more than fifty cold applications.
• Your existing team – with a referral incentive. Your current team knows people you do not. A structured employee referral programme – even a simple one offering a bonus paid after the referred hire completes 90 days – is one of the highest-quality sourcing channels available to a startup. Referrals tend to be better calibrated to your culture than open applications, because the person referring has a professional reputation at stake.
• Direct outreach on LinkedIn – done properly. Passive outreach to candidates who are not actively looking requires personalisation that mass-message templates cannot replicate. A message that demonstrates you have read the candidate’s profile, references a specific aspect of their experience that is relevant to your role, and explains concisely why this opportunity might be worth their time will get a meaningful response rate. A generic template will not. Expect to send 30–50 messages to produce three to five conversations worth having.
• Specialist job boards for technical roles. For engineering roles in Poland, JustJoinIT and No Fluff Jobs reach a significantly higher concentration of relevant candidates than generalist platforms. For international roles, levels.fyi is useful for senior engineering benchmarking. Posting on the right specialist platform produces better-quality applications than posting broadly on general job sites.
• A specialist tech recruitment agency – when the role is senior, niche, or urgent. For roles where the candidate pool is small, the requirement is technically complex, or your timeline is compressed, the DIY sourcing approach has a real ceiling. A specialist IT recruitment agency with a maintained candidate network can reach profiles that are not accessible through job boards or LinkedIn outreach alone – and can do so faster than a founder running the process alongside everything else. We address when to make this call specifically later in this guide.

Step 3: Build a Screening Process That Respects Your Time and the Candidate’s

Without an HR team to run initial screens, you need a filtering mechanism that removes poor-fit candidates before they reach your calendar. Here is a simple three-stage screening process that works for most technical roles.

Stage zero: the application filter.

 Before you schedule any conversation, review applications against your must-have list only. This is a binary filter – does the candidate meet the non-negotiable criteria or not? At this stage you are not making quality judgements; you are removing obvious misfits. A well-scoped must-have list should allow you to filter a pool of 50 applications down to 8–12 worth looking at in under two hours.

Stage one: the async screen. 

For the candidates who pass the application filter, send three to five specific written questions before scheduling any call. This serves three purposes: it tests written communication skills (critical for remote engineering roles), it gives you a richer picture of the candidate’s thinking than a CV provides, and it filters out candidates who are not genuinely interested enough to engage with the role seriously.

Good async screening questions for engineering roles are specific rather than generic. “Describe a system design decision you made that you would approach differently today, and what you would change” is a good question. “Why are you interested in this role?” is not. Aim for questions that reveal how the candidate thinks, not just what they have done.

Stage two: the 30-minute technical conversation. 

Not a coding interview at this stage – a structured conversation with a defined set of questions that you ask every candidate in the same order. This is the most important process discipline a founder without HR can adopt. Asking different questions to different candidates makes meaningful comparison impossible and introduces evaluation bias. Define five to seven questions before you start interviewing and use them consistently.

Cover: the specific technical experience most relevant to your role, a recent complex problem the candidate solved, how they handle ambiguity and competing priorities, what their preferred working environment looks like, and what they are optimising for in their next role. Take notes during the conversation using a simple scorecard – rate each area on a 1–3, 1-5 or 1-10 scale – so that you are comparing structured data after the call, not impressions.

Stage three: the technical assessment. 

For engineering roles, a practical assessment is the most reliable predictor of on-the-job performance. Keep it focused and time-bound – a well-designed take-home task of three to four hours, or a live technical session of 60–90 minutes, is enough to assess the skills you actually need to evaluate. Do not design assessments to test everything – design them to test the one or two capabilities most critical to success in the specific role.

Pay candidates for take-home assessments if the task is longer than two hours. It signals respect for their time and improves completion rates among the strongest candidates – who have the most options and the least incentive to invest time in a speculative exercise.

Step 4: Run Interviews That Actually Predict Success

Most startup interviews are conversations that assess how likeable the candidate is, not how well they will perform in the role. Likeable and high-performing are correlated but not identical, and optimising for the former at the expense of the latter is how startups end up with teams that feel good and ship slowly.

Structured interviews outperform unstructured ones. Research is unambiguous on this: structured interviews – where every candidate is asked the same questions in the same order and evaluated against the same criteria – predict job performance significantly better than free-form conversations. For a founder without HR support, structured interviews also save time and make decision-making faster, because you are comparing consistent data rather than subjective impressions.

Use the STAR format to evaluate past behaviour. Asking candidates to describe specific past situations – what the Situation was, what Task they owned, what Actions they took, and what the Result was – produces far more evaluative data than hypothetical questions. “Tell me about a time you had to make a critical architectural decision under time pressure” tells you more than “What would you do if you had to make a critical architectural decision under time pressure?”

Involve a technical evaluator in at least one round. If you are a non-technical founder hiring engineers, you must have someone with genuine technical depth involved in the assessment – whether that is a technical co-founder, an advisor, a fractional CTO, or a senior engineer already on your team. Evaluating engineering candidates without technical expertise is not an interview; it is a personality assessment. You will consistently undervalue strong but reserved candidates and overvalue confident but shallow ones.

Assess culture fit – but define it before the interview, not after. Culture fit is a legitimate criterion and an important one. It is also the criterion most frequently used to justify decisions that were made for other reasons. Before interviews begin, write down three to five specific, observable working style characteristics that predict success in your environment – not values statements like “we value transparency,” but specific behaviours like “communicates blockers proactively before they become delays” or “makes architectural decisions independently without requiring explicit direction.” Evaluate candidates against those specifics, not against a vague feeling of fit.

Step 5: Make Offers That Get Accepted

An offer that gets declined after a three-week interview process is one of the most demoralising experiences in startup hiring. It is also largely avoidable.

Do not make a formal offer blind. Before you send an offer letter, have a direct conversation with the candidate to confirm that the compensation, engagement model, start date, and role scope you are planning to offer are within their acceptable range. This is not negotiation – it is calibration. A candidate who tells you their minimum B2B rate is 20,000 PLN/month should not receive an offer for 17,000 PLN/month. You already know it will be declined.

Move fast between final interview and offer. The window between a candidate completing their final interview and receiving an offer is the window in which they are most actively entertaining competitive offers. For senior engineering candidates in a competitive market, this window can be days. A week of internal deliberation after a final interview is a week in which your preferred candidate may accept an offer elsewhere. Make the decision, discuss it internally, and issue the offer as quickly as possible once it is made.

Be specific in your offer letter. The offer letter for a B2B engagement should specify the monthly rate, expected hours, engagement start date, notice period terms, IP assignment, and any equity arrangement. Vague offer letters create renegotiation risk and slow the acceptance process. A clear, specific offer letter signals organisational competence, which matters to senior candidates who are evaluating whether they want to trust their career to your company.

Have a response to “can you go higher?” Almost every offer generates a counter. Know in advance what your walk-away point is and what your flex is, so that you are not making budget decisions under the emotional pressure of a negotiation. A candidate who asks for 10% more than your initial offer is not being unreasonable – they are doing exactly what experienced professionals do. Have a clear answer ready.

Step 6: Onboard Properly or Waste the Hire

The hire is not complete when the offer is signed. It is complete when the person is performing in the role. The period between those two points, typically the first 30 to 90 days, is where more placements fail than most founders realise, and where the absence of HR infrastructure is most keenly felt.

A minimal, effective onboarding process for a startup without HR covers five things.

Before day one: The person has their equipment, all system access credentials, their contract signed, and knows who they are reporting to, where to find documentation, and what their first week will look like. This is basic and frequently skipped. Showing up on day one without a laptop or without Slack access is a trust-destroying first impression that no subsequent good management recovers in full.

Week one: A structured introduction to the product, the codebase, the team, and the current priorities. Not a passive documentation read, rather an active conversations with the relevant people. A good week one ends with the new hire having a clear understanding of where the company is, where it is going, and what their role is in getting it there.

First 30 days: A defined first project – something meaningful enough to require real engagement with the codebase or product, scoped tightly enough to be completable within the month. Completing a real deliverable in the first 30 days builds confidence, surfaces onboarding gaps early, and gives you a genuine data point on the hire’s performance before the probation window becomes a difficult conversation.

First 60 days: A structured check-in – not a performance review, a two-way conversation about how the role is going, what is working, what is not, and what support the person needs to perform at their best. This conversation, held at 60 days rather than never, is the intervention that turns most early-stage misalignments into resolvable situations rather than resignations.

First 90 days: A more formal performance conversation that establishes the goals and evaluation criteria for the next quarter. This is the point at which you are either confident the hire is working or aware that it is not, and awareness at 90 days is recoverable. Awareness at 6 months is not.

When DIY Hiring Breaks Down: Recognising the Ceiling

Hiring without HR is entirely viable for a startup in its early stages, for roles where the candidate pool is broad, the requirement is straightforward, and the timeline is flexible. It becomes significantly harder, and significantly more expensive in terms of your time, as any of those conditions change.

Here are the specific situations where the DIY approach hits a ceiling.

1. When the role is senior or niche. Senior engineering candidates are not browsing job boards in the way that junior candidates are. They are reachable through networks, community relationships, and direct outreach by people they trust. A founder who does not have an established engineering network in the relevant market will spend weeks on outreach that an experienced recruiter with an existing relationship network could compress into days.
2. When you have already been searching for more than four weeks. A search that has not produced a viable candidate after four weeks has a problem – either the brief is miscalibrated, the sourcing approach is too narrow, the compensation is below market, or some combination of all three. Continuing the same approach expecting different results is the definition of a sunk cost. At this point, bringing in external expertise is faster and cheaper than continuing to absorb the time cost yourself.
3. When the role is business-critical and the timeline is compressed. A vacancy that is delaying a product delivery, creating team overload, or blocking a fundraise has a real daily cost. The recruiter fee for a specialist agency – typically 18–20% of first-year salary, paid once on success – is almost always cheaper than the cost of a three-month vacancy on a business-critical role. Itentio’s average time to fill of 3–4 weeks, with documented cases under one week for urgent requirements, exists precisely for these situations.
4. When you are hiring for a role you cannot technically evaluate yourself. A non-technical founder hiring a senior backend engineer without technical support in the process is flying blind on the most important dimension of the hire. In this situation, a specialist IT recruiter who can run a technical pre-screening before candidates reach you is not a luxury, it is the mechanism through which you avoid hiring someone impressive-sounding who cannot actually do the job.
5. When you are hiring more than two or three roles simultaneously. Three concurrent open roles, each requiring 20–30 hours of process management, is a 60–90 hour workload on top of running your company. This is the point at which the operational efficiency argument for a recruitment partner becomes overwhelming regardless of cost.

How to Hire Without an HR Team: The Tools You Actually Need (No Expensive HR Software Required)

You do not need an ATS, an HRIS, a recruitment CRM, or any dedicated HR software to run an effective hiring process at early startup stage. Here is the minimum viable toolkit.

• A shared document for each role – containing the role brief, the must-have criteria, the interview scorecard, the candidate shortlist, and the evaluation notes from each stage. Google Docs or Notion work fine. The goal is a single source of truth that every person involved in the hiring process can access and contribute to.
• A simple candidate tracker – a spreadsheet or Notion table with columns for candidate name, source, current stage, last contact date, evaluation score, and next action. Nothing more complex than this is needed until you are running ten or more concurrent searches.
• A structured interview scorecard – a one-page document with the five to seven questions you ask every candidate, a 1–3 rating scale for each, and space for notes. Completing this immediately after each interview and sharing it with other evaluators before they form their own opinion prevents groupthink and keeps decisions grounded in evidence.
• A calendar booking link – Calendly, Cal.com or or equivalent, with interview slots pre-loaded. Eliminating the back-and-forth of manual scheduling saves hours per role over the course of a search and is one of the easiest process improvements a time-constrained founder can make.
• A template offer letter – reviewed once by a lawyer for your jurisdiction. Drafting an offer letter from scratch for every hire is unnecessary, error-prone, and slow. A well-drafted template that you customise for each role takes fifteen minutes to prepare and eliminates legal risk.

Hiring Without HR in the Tech Market: The Specific Realities

Generic hiring advice applies differently in the tech market. Here are the dynamics that matter specifically for founders hiring engineers.

The best engineers are not actively looking. The strongest senior engineers are typically employed, doing interesting work, and not browsing job boards. Reaching them requires direct outreach or a recruitment partner with existing relationships. If your sourcing strategy is entirely inbound, like posting jobs and waiting, you are accessing only the fraction of the talent pool that is actively searching, which skews toward candidates who are between roles for a reason.

Speed is a competitive differentiator. Strong engineering candidates in an active search typically have two to four processes running simultaneously. The company that moves fastest through the interview process, without cutting corners on evaluation, wins the most candidates. A one-week gap between each interview round is standard practice at large companies and a candidate attrition engine for startups. Two to three days between rounds is achievable and meaningfully better.

Compensation benchmarks move faster than most founders realise. The Polish IT market in particular has seen significant salary evolution over the past three years. An engineer who was billing 18,000 PLN/month in 2022 is likely billing 22,000–25,000 PLN/month in 2026. Founders who are working from outdated salary data consistently lose candidates at offer stage. Before setting a compensation range, get current market benchmarks from a recruitment partner or from publicly available sources like the salary surveys.

Technical assessments must be relevant and time-respectful. The engineering community has become significantly less tolerant of assessment processes that are long, generic, or appear designed to extract free work. A take-home task that requires more than three to four hours, or a live coding exercise that tests algorithms unrelated to the actual role, signals that the company either does not understand the current market or does not respect candidates’ time. Both are reputation risks in a small market where word travels.

How to Hire Without an HR Team: Frequently Asked Questions

When You Are Ready for External Help

Hiring without HR is entirely achievable with the process in this guide. For most early-stage roles in non-technical functions, it is the right approach – lower cost, faster when it works, and keeps you close to the people joining your team.

For senior technical roles – particularly in a market like Poland where the candidate pool for the best profiles is limited and competition from international companies is real – a specialist recruitment partner is often the faster and more cost-efficient path than running the process yourself.

Itentio has been placing senior IT professionals for startups, scaleups, and international technology companies since 2018. Our candidate database of over 30,000+ IT professionals is built on eight years of active sourcing across the full technical role spectrum – not just engineers, but QA, DevOps, Data, AI, Design, Product, and technical leadership. Our average time to fill is 3-4 weeks. Our candidate retention rate is 99%.

If you have a role that is stalling, a brief that is proving hard to fill, or a search that needs to be run faster than your current capacity allows – we will give you an honest assessment of the candidate market for your specific requirement, with no obligation.

Explore our IT recruitment services →

See documented case studies from startup clients →

Contact us to discuss your hiring brief →