What we do
Tools
Industries
Department
How we workLet's talk →
Home/Hiring Computer Programmers Without a Tech Lead
Hiring Programmers

Hiring Computer Programmers When You Don't Know Which Kind You Need

"Programmer" covers people who build websites, phone apps, databases, integrations between business systems and a dozen other things, and most are good at two or three of them. If nobody in the business is technical, the risk is hiring the first one you speak to and getting their favorite tool as the answer. Start from the problem instead. (Looking for programming work yourself? This page is for businesses hiring, so it isn't a job listing.)

Find your problem, then the kind of programmer it needs

Plain-English problems on the left. Each links to a page about that kind of work in more depth.

What is going on Who usually does it What to watch for
Our website is slow, was hacked, or needs to take bookings or orders A WordPress developer or PHP developer for most business sites. A Shopify developer if it's a Shopify store. If the job is only a new look, a web designer is the better and cheaper hire.
Our tools don't talk to each other, so someone retypes data every day Integration work: an automation engineer, or an API developer when one of the systems needs its own connection built. What happens when a sync fails, and who finds out. That's most of the real work.
We want an app customers install on their phones A mobile app developer. A Flutter developer when one app has to cover iPhone and Android. The cost of keeping it in both app stores after launch, not just building it.
A spreadsheet or Access file runs part of the business and keeps breaking A database developer to give the data a proper home, often with a Python developer for the scripts and reports around it. Who has the latest copy today. Moving it starts with agreeing which one is right.
Nothing off the shelf fits how we work Custom software development: a small team with front-end, back-end and database skills. Check a subscription tool can't do it first. Custom only pays off when workarounds keep piling up.
We already have developers and need more capacity That's a different model, covered on staff augmentation and dedicated development team. Who manages the new people day to day. Added capacity still needs someone directing it.

Write a one-page brief any programmer can quote from

Ten minutes of writing saves weeks of back-and-forth, and it makes quotes comparable.

  1. 1

    Say what happens today, step by step

    Who does what, in which tool, how often. "Every morning Sam copies yesterday's web orders into the stock spreadsheet" is more useful than "we need automation".

  2. 2

    Say what should happen instead

    Describe the result, not the technology: orders appear in stock on their own, customers can book without calling, managers see the week's jobs on one screen.

  3. 3

    List every system and account involved

    The website, the accounting package, the CRM, the spreadsheets, and who holds the login to each. This alone tells a programmer most of what the job is.

    Watch for: accounts in a former employee's or a freelancer's name. Sort those out before anyone starts.

  4. 4

    Name what must never break

    Payroll day, the order flow, a report the bank needs. Those parts get tested first and changed most carefully.

  5. 5

    Decide what "done" looks like

    Who will use it, how you'll know it works, and who looks after it next year. Programmers quote very differently when upkeep is or isn't included, so ask for it as a separate number.

A programmer on staff, or the project done for you?

Hire onto staff

When there is years of steady work

  • You can list a year of work for them today, not just one project.
  • Someone in the business can judge their work and set priorities.
  • You can wait for recruiting, and cover holidays and the day they leave.
  • One person usually brings one or two specialties, so the role has to match the work.
Contract the project

When there is a problem to solve

  • The work has a clear outcome, even if the details still need working out.
  • It needs more than one skill, such as a website, a database and an integration.
  • Nobody in-house can review code, so you want a team that checks its own work.
  • After launch it moves to upkeep rather than a full-time seat.

If you can't yet write down a year of work for one person, start with the project. A freelance developer suits small, short jobs, and remote developer covers hiring someone who works from elsewhere.

Questions people ask

We don't know what language or platform we need. Is that a problem?

No. Most people hiring for the first time don't, and they shouldn't have to. Describe the problem as in the brief above. The language and platform follow from what the software has to connect to and who will use it.

What if the work turns out to be really small, like one fix?

Then it should be quoted and done as one fix. A freelancer can be the better choice at that size, and the freelance developer page covers how to hire one safely.

How is this page different from the other 'hire a developer' pages on your site?

The others are for people who already know the skill they want, like PHP, Flutter or databases. This one is for working that out from the problem, and the table above points to the right one once you have.

Do you place programmers in our company, like a recruiter?

No. n-frames doesn't recruit programmers for you to hire. We take the project on with our own developers and deliver the working software. If you already run a development team and want extra hands inside it, the staff augmentation and dedicated team pages explain how that works.

Should we hire a full-time computer programmer instead?

If there's a steady stream of work for years and someone can manage it, possibly. If the need is one system built and then looked after, a full-time hire often ends up underused or stuck working outside their specialty.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.