How to Hire an AI Developer Without a Technical Background

You can hire an AI developer without being able to read code. Your job is to define the business problem, assess whether candidates understand it and appoint someone qualified to review their technical work. Ask candidates to demonstrate what they built, explain trade-offs in ordinary language and complete a paid task with clear acceptance criteria. Recruitment vetting helps select candidates; your company still needs technical oversight for its own systems.

First decide which specialist you actually need

Start with the work that needs an owner. An AI developer builds applications using language models, company information and software integrations. Retrieval-augmented generation, or RAG, means retrieving relevant material for a model to use when answering. An automation specialist connects business systems and manages workflows. Some projects need both skills.

Do not use a tool label as a substitute for assessing engineering ability. Custom integrations and sensitive data can appear in any of these roles. The comparison between an AI automation specialist and AI developer can help you define the boundary.

Turn the business problem into a brief candidates can challenge

Describe the current process before choosing a model or platform. A credible candidate should question assumptions, including whether the problem needs AI at all.

• State who experiences the problem, what they do now and which delay or error you want to reduce.
• List the systems involved, the information available and the person who owns each system.
• Define the expected output, who approves it and what should happen when information is missing or a service fails.
• Name the owner of the repository, cloud accounts, credentials, documentation and production monitoring.
• Separate the initial deliverable from continuing maintenance, support and improvement.

How Borderless Recruit helps

Borderless Recruit recruits dedicated, full-time AI and automation specialists from the Philippines. It handles sourcing, vetting, local employment contracts, payroll and HR; the employee works only for your company during your UK or European business hours. Vetting includes a live English interview, a personality/reliability assessment and, for AI developers, a working RAG or agent build with edge cases. You interview the finalists. The total monthly client fee for an AI developer starts at £1,330 / €1,540 ($1,750), as listed on the AI Developer role page.

Review a portfolio without reading the code

Ask the candidate to open a project, trace a realistic request through it and deliberately trigger a failure. You are looking for evidence of authorship, judgement and operational thinking. Respect previous clients' confidentiality: an anonymised walkthrough or a candidate-owned demonstration is a reasonable alternative to private source code.

• Ask what the candidate personally designed, coded and deployed, and what colleagues or third-party tools contributed.
• Request the original problem, constraints and rejected approaches. Ask why the design changed.
• Ask for a walkthrough of tests, logs or version history, with confidential details removed.
• Change a requirement and ask what would break, what might cost more and what needs retesting.
• Ask them to explain the system to an operations manager, including its limitations.

Clear communication is valuable, but it does not prove the code is secure or maintainable. Record what you observed and pass technical claims to your reviewer.

Interview questions a non-technical employer can score

Write down the evidence behind each judgement. A confident answer without a demonstration remains unproven. Do not let presentation skills compensate for an unresolved access-control or reliability concern.

Use a paid work sample that resembles the real job

Illustrative assessment: provide synthetic CRM records, an approved product-information document and a mock enquiry inbox. Ask the candidate to classify an enquiry, retrieve supporting information, draft a response with its source and pause for human approval. Give candidates the same brief, agreed payment, time allowance and rules on using AI coding tools. Keep the exercise separate from productive client work.

Request the source repository, setup instructions, test results and a short explanation of unresolved risks. Ask your independent reviewer to rerun the sample, inspect permissions and secret handling, and assess whether another developer could maintain it. Passing this exercise is evidence for hiring, not proof of production readiness. Adapt the AI developer practical assessment to your systems.

Recognise warning signs before making an offer

• The candidate cannot explain their contribution beyond screenshots or tutorial language.
• They promise flawless answers, compliance or savings before examining the requirements.
• They dismiss failure handling, human approval or ongoing operating costs.
• They insist on keeping production code or credentials in personal accounts.
• They resist reasonable questions about limitations or cannot explain how someone else would take over.

Build a comparable monthly hiring budget

A staffing fee, employee salary and agency project quote cover different things. The catalogue's standard AI developer price is from £1,330 / €1,540 per month ($1,750), covering the staffing service described above catalogue pricing. This is the client's monthly staffing cost, not the developer's salary or the total cost of running an AI application.

For a local hire, ask finance for a fully loaded monthly figure covering salary, employer contributions, benefits, recruitment, equipment and HR support. Ordinary UK employer National Insurance is 15% on earnings above the applicable threshold GOV.UK employer rates. The minimum employer contribution under automatic enrolment is generally 3% of qualifying earnings, subject to the scheme rules GOV.UK workplace pensions. These percentages apply to different earnings bases; simply adding them to the whole salary gives a misleading calculation.

For a European hire, use the relevant country's payroll calculation and the actual benefits package. Keep software and infrastructure assumptions consistent across options. Budget separately for model usage, hosting, databases, licences and independent technical review, and ask what is included in each proposal. Avoid treating a headline salary range or a generic employer-cost uplift as a complete employment budget.

Choose the engagement around ownership: a freelancer may suit a bounded audit or integration, an agency may suit a project needing several disciplines, and a dedicated developer may suit continuing maintenance and improvement. For UK contractors working through an intermediary, check who must determine employment status and whether off-payroll rules apply GOV.UK IR35 guidance.

Make working hours and decision-making explicit

Philippine staff work a shift that overlaps UK or Central European working hours. The Philippines has no daylight saving, so document how UK and European clock changes affect the agreed schedule. Confirm meeting availability, handovers and any support needed outside the contracted shift.

Give the developer a named business owner who can answer process questions and accept work. Use written requirements, recorded demonstrations and an issue tracker. Keep responsibility for technical review explicit after hiring, particularly when the developer proposes consequential changes.

Protect data, intellectual property and production access

Giving an overseas developer access to personal data can constitute an international transfer. The assessment depends on the parties and actual data flows, including remote access. Check the applicable ICO guidance on UK GDPR transfers and European Commission guidance on EU data transfers. Employment arrangements alone do not resolve data-transfer obligations.

• Document confidentiality, intellectual-property ownership, permitted data use and return or deletion obligations.
• Use company-controlled repositories, cloud accounts and model-provider accounts.
• Grant named users only the access they need; keep secrets out of code and shared documents.
• Use synthetic recruitment data. Removing names alone may leave people identifiable.
• Require qualified review before consequential changes reach production.
• Agree incident reporting, access removal, backups and handover responsibilities.

Manage the hire through observable checkpoints

At each checkpoint, ask for a demonstration against the original acceptance criteria. Record what passed, what remains uncertain and who owns the next action. Measure engineering work the developer can influence: defects resolved, documentation kept current, incidents communicated and costs monitored. Revenue or savings also depend on adoption, data quality and business decisions.

Make the final decision from evidence

Proceed when the candidate has demonstrated relevant work, the paid sample meets your criteria and a qualified reviewer has assessed the technical risks. Confirm the ongoing owner, budget, access arrangements and handover expectations before work begins. If a material concern remains unresolved, ask for the missing evidence before making an offer.