Find programmers by defining the work first, choosing a suitable engagement model, and evaluating candidates against a small sample of that work. A long list of programming languages or a high marketplace rating does not establish fit for your project.
A website change, a mobile integration, and a long-lived business system need different skills and ownership. You do not need to finish the product or hire a designer before speaking to engineers. You do need enough context for a useful conversation.
Write a role brief before searching
Include these fields:
- Outcome: the user task or operating problem to solve.
- Existing system: stack, repository condition, hosting, integrations, and known constraints.
- Scope: the first deliverable, acceptance criteria, and exclusions.
- Ownership: who supplies product decisions, design, code review, QA, deployment, and support.
- Working arrangement: location or time-zone overlap, expected availability, duration, and decision cadence.
- Budget: a current range, engagement model, and whether ongoing maintenance is included.
If you cannot choose the stack responsibly, hire a bounded technical discovery engagement first. Do not pick a language solely to make the job advertisement look precise.
Choose the hiring model
| Model | Where to look | Useful fit | Tradeoff |
|---|---|---|---|
| Employee | Relevant job boards, professional communities, referrals, specialist recruiters | Continuing roadmap and retained domain knowledge | Hiring, onboarding, management, and ongoing employment cost |
| Freelancer | Referrals, professional portfolios, freelance marketplaces | Defined work with an internal owner | Availability, continuity, and skills outside the contracted remit |
| Agency | Relevant case studies, referrals, targeted vendor search | Several coordinated skills or a bounded delivery team | Allocation, handover, subcontracting, and commercial overhead |
| Internal move | Existing employees with demonstrated relevant skills | Domain knowledge and a credible development path | Backfill, training, and role transition still need planning |
An in-house hire is an employee working within your organization; it is not synonymous with internal promotion. New hires still need onboarding. Freelancers and agencies may work with other clients, so confirm capacity rather than assuming exclusivity.
Search channels with a specific purpose
Start with colleagues who have delivered comparable software. Ask what the person actually owned, how they communicated, and whether they supported the result after launch. A recommendation for a marketing website does not automatically transfer to a payment system.
Use job boards and professional networks for a clearly defined role. Look for public portfolios or contributions relevant to the work, while remembering that capable developers may have no public code because their work is proprietary. Do not make public contribution volume a hiring requirement.
Freelance marketplaces can help find candidates for a bounded brief. Review examples and references, then check current fees, payment terms, and engagement rules directly with the platform. A rating is a starting signal, not proof of technical competence.
For an agency, meet the proposed lead and confirm the team allocation. Use the outsourcing guide to compare delivery ownership, reporting, and exit terms.
A sample outreach message
This is a template to adapt, not a message to send indiscriminately:
We are building [product] for [users]. We need help with [specific workflow] in [existing stack, if fixed]. The first deliverable is [observable result], with [budget range], [duration], and [working overlap]. Your work on [relevant public example] appears related. If you are available, could you share a comparable project, your role in it, and any questions you would need answered before estimating?
Use the candidate’s stated contact route and respect community rules. Be clear about paid work, decision timing, and who will assess it.
Evaluate through a bounded work sample
A short paid exercise can test the real job better than unrelated trivia. Agree the time cap, compensation, permitted tools, evaluation criteria, and use of the output. Avoid asking candidates to build an unpaid production feature or disclose confidential former-employer work.
Illustrative exercise: in a small synthetic project, fix a duplicate form submission and explain how to verify the behavior. For a design-heavy role, substitute an accessible interface task; for a data role, use a small transformation with invalid input cases.
| Criterion | Evidence to inspect |
|---|---|
| Understanding | Clarifies requirements and identifies missing information |
| Correctness | Handles the intended task and important failure cases |
| Maintainability | Uses understandable structure and explains tradeoffs |
| Verification | Demonstrates the behavior and chooses proportionate tests |
| Communication | Reports uncertainty, decisions, and remaining work clearly |
Use missing, partial, demonstrated, and corroborated as suggested evidence anchors. Apply the same exercise and criteria to comparable candidates, with appropriate accommodations. The OPM structured-interview guidance provides a general basis for consistent job-related assessment; this rubric is not a validated predictor of programmer performance.
Interview and check references
Ask about a comparable project, a difficult defect, a missed estimate, and a disagreement over scope. Follow up on what the person decided, what others owned, and what changed after feedback. For agency candidates, establish that the proposed team—not just the company—has the relevant experience.
With permission, ask references about communication, review habits, estimate assumptions, production ownership, and handover. Separate a candidate’s coding skills from the product, design, leadership, or security expertise that must come from elsewhere.
Compare cost without false shortcuts
There is no universal rate for a “good programmer.” Compare dated quotes for the same geography, seniority, scope, and engagement model. An employee salary is not equivalent to a contractor’s billable rate. Include recruiting, onboarding, equipment, management, review, benefits where applicable, agency or platform fees, and maintenance.
More headcount does not produce proportional speed. New people need context, shared code review, and coordination; one person’s changes can affect everyone using the same system. Add capacity where work can be divided responsibly, not because ten developers are assumed to finish ten times faster.
Make ownership and the first milestone clear
Before work begins, agree repository and account access, decision authority, deliverables, acceptance, payment, third-party licenses, confidentiality, IP terms, support, and handoff. Have the relevant legal or commercial reviewer adapt the agreement to the jurisdiction and relationship. A checklist does not itself transfer ownership.
Start with a small deliverable that produces useful evidence and can be reviewed in your environment. Confirm that another engineer can run it, understand it, and continue the work. Expand the engagement when the working relationship and delivery evidence support it.
If the missing role is senior technical judgment rather than coding capacity, define that separately. Hapy can help scope the next technical step through a defined engagement before you hire.
Further questions
Where should I start looking for programmers?
Start with a role brief and referrals for comparable work, then use relevant job boards, professional communities, freelance marketplaces, or agencies according to the engagement you need.
How Many Developers Are Required for a Startup?
Team size depends on scope, platform, risk, deadline, and existing skills. Include product decisions, design, review, QA, deployment, and support; adding programmers does not automatically shorten the critical path.
