Hire software developers for any role your team is missing

Hire software developers by role, or bring us the problem and we'll name the role. Ours average 7 years of experience, 80%+ senior-level or above.

Abstract 3D illustration of blank profile cards sorted into six role groups, for hiring software developers by roleAbstract 3D illustration of blank profile cards sorted into six role groups, for hiring software developers by role

BACKEND

How does hiring by role work?

Hire by role. Name the role, its seniority and the stack it works in, and we match engineers from our own bench to that brief and send you a shortlist. If you know only the problem, describe it and we'll tell you which role fits, then match for that.

For the back end, the first filter is the stack you already run, since a second backend language is a cost your team keeps paying. For a Dutch eHealth software services provider we built a white-label backend on Spring Boot, and our client's platform passed ISO 27001, NEN 7510 and MedMij.

FRONTEND

Frontend developers

Pick the framework you already ship. A front end rewritten from one framework to another rarely pays for itself, and the screens your users rely on don't care which one built them. Change it when the old one is out of support or slows every release.

On a fintech company's corporate payments platform, we moved the React frontend from a single-page application to microfrontends on single-spa. Our client's users take about 15% less time to prepare and submit payments, mostly thanks to the UI/UX work.

MOBILE

Mobile developers

Cross-platform or native is the first decision, and the phone's hardware decides it. An app that mostly shows data and takes input runs well from one Flutter or React Native codebase. One that lives on Bluetooth, sensors or background work is usually cheaper built native.

We built Arterio, a native Kotlin app patients with hypertension use to record blood pressure, with readings taken from the monitor over Bluetooth. Our client saw 70% less error in blood pressure logs than with paper logs.

DATA & AI

Data and AI specialists

Data work runs in an order. Engineers build the pipelines, analysts turn the data into numbers people trust, and scientists and AI engineers build models on top. Hire a data scientist before the pipelines exist and you pay them to clean data.

For a logistics company, we rebuilt the demand forecasting system on Databricks and Azure, bringing seasonal changes, economic indicators and competitor data into the models. Our client reports forecast accuracy rising from 70% to 92%.

CLOUD & DEVOPS

Cloud and DevOps roles

If your releases still depend on one person's laptop, start with DevOps. This group sets up the cloud your software runs on and the pipelines that test and release it, and certified AWS and Azure engineers are part of it.

An AdTech company's inherited Google Analytics to BigQuery pipeline ran on a server left on all day for jobs that took minutes. We refactored it so those jobs start on an event, and cloud infrastructure cost fell from $10 to $0.25 a day.

PRODUCT & QUALITY

Product and quality roles

Testing and design are the work that slips first when developers do it on the side. Bugs reach users, screens get designed in code review, and nobody owns either until a release goes wrong in front of a customer.

Our designers worked inside a logistics company's team on its transportation management system, and creating one load went from 3 minutes in the old system to 30 seconds. Automated QA ran on the patient portal and the fair lending platform we built.

TEAM OR PROJECT

Who will direct the engineers day to day?

You have a tech lead and a process

Then add engineers to the team you manage. They work in your sprints and your tools and take direction from your tech lead. It suits a team that lacks a skill, or has a known backlog and too few hands.

You'd rather not manage people day to day

We run a managed team of dedicated developers for you. A delivery manager on our side is your regular contact and keeps the team staffed, and you decide what gets built first. It fits when priorities keep moving but the roles can be named up front.

You want a product built end to end

We take on software development projects from discovery to release. Discovery comes first and sets the requirements and the architecture, then the team builds in sprints with a demo every two weeks, and the delivery is ours to answer for.

You need a data platform or an AI feature

We build data platforms and pipelines for reporting and AI, and take on AI development projects through to production. Before an AI build we agree a test set and a go-live bar with you, and discovery tells you when AI isn't the right answer at all.

Your cloud needs building or moving

Our cloud and infrastructure services cover designing an environment on AWS, Azure or Google Cloud, moving existing systems into it and building the CI/CD pipelines your releases go through. We prefer to migrate in waves, each one tested in the target before cutover.

Abstract 3D illustration of four project lanes ending in a stack of cubes, stacked discs, a star-marked disc and cloudsAbstract 3D illustration of four project lanes ending in a stack of cubes, stacked discs, a star-marked disc and clouds

Know the roles, or only the problem?

To hire engineers, send the roles, seniority and stack you're missing. For a build, send the problem, and we'll suggest who should do it.

THREE STEPS, EVERY CANDIDATE

How do you vet your engineers?

Abstract 3D illustration of candidate slabs passing three arched gates, one slab reaching the shortlist at the endAbstract 3D illustration of candidate slabs passing three arched gates, one slab reaching the shortlist at the end

Technical skills assessment

Candidates are tested on the stack and seniority they claim. A data engineer gets SQL on large tables and a pipeline to design, an AWS engineer a real setup judged on security and cost.

Soft-skills evaluation

How they speak English, take feedback and work in a team. Your people will talk to them every day, so we weigh this step as heavily as the code.

Job-history analysis

Our check of the CV and the career behind it. It is one step of three because a CV can't show how someone copes when a deadline moves or the spec changes halfway.

Live coding, for some roles

The candidate writes code live and talks it through, so we see how they reason. In staff augmentation you can watch it as part of your own selection.

Background check, on request

We run it only when a client asks for one. It confirms the CV is genuine. Whether the person can do the job well is what the vetting steps test.

HIRING PROCESS

How a staffing hire runs

The times on each step are the usual ones. What we commit to is presenting matched candidates within 7 days of your request. Your interview is the step that moves the most, because it runs on your team's calendar.

  1. STEP 1

    Requirements discovery

    We talk through the roles, seniority, skills and team setup you need, and agree what a good match looks like.

    1 day

  2. STEP 2

    Candidate matching

    We match engineers to the brief and send you a shortlist, with the reason behind each match.

    1–2 days

  3. STEP 3

    Your interview

    You interview the shortlist and decide who joins. You can turn anyone down, on the CV or after the call.

    1 day

  4. STEP 4

    Contracts and access

    We sign the contracts and the NDA, and your team opens the accounts the engineer will work in.

    1–2 days

TERMS OF WORK

Engagement models and terms

Staff augmentation

Our engineers join your team and work in your process and tools. You manage them; we source, vet and contract them.

Hourly rate per engineer by role and seniority, invoiced monthly.

  • If an engineer isn't the right fit, we replace them within 14 days at no extra cost.
  • Knowledge transfer to the replacement engineer isn't billed.
  • There is no free trial period.
  • 30 days' notice to take an engineer off or end the engagement, with no minimum term beyond it.
  • Out-of-hours on-call only if agreed with you; we set its hours and billing together.
  • After two years, moving an engineer onto your own staff is something we can discuss.

Managed team

An agreed team capacity that we manage. We coordinate delivery and handle the team's make-up. You set the priorities and own the backlog.

Per-engineer rates, or a fixed monthly fee for the agreed capacity.

  • We handle replacements ourselves, and the team keeps its agreed capacity and pace.
  • Engineers work full-time for your team only.

Project delivery

We deliver an agreed scope end to end: plan, team, milestones, QA and release. You make the product decisions and accept each milestone.

Fixed price per milestone after discovery, or time and materials against an estimate.

  • Scope changes go through change requests.
  • On fixed-price projects, a warranty period agreed in the contract, usually 30–60 days.

Whichever model you choose

  • We reply to an inquiry from the contact form within 24 hours.
  • We sign an NDA before work starts, and IP passes to you on payment.

ACCESS AND DATA

Who can reach your code and data?

You get our own engineers, employed by Octalance, some under a B2B contract. Only when our bench can't cover a role in time does a partner supply vetted engineers, and they pass the same steps. They work across Eastern Europe on CET/CEST by default, and we shift the schedule to match yours. For a US team we can arrange 4+ hours of daily overlap with the West Coast, and more with the East Coast.

In your cloud and tools, they work through named accounts you issue in your own IAM or SSO, with only the access their role needs. When an engineer leaves the engagement, all of it is removed.

Systems we control are hosted in the EU, and we work under GDPR as an EU company. Code and data in your own systems stay wherever you keep them. Where we handle client data, we sign a data processing agreement.

Abstract 3D illustration of a code repository block opened by one named key, with the other locks around it left closedAbstract 3D illustration of a code repository block opened by one named key, with the other locks around it left closed

CASE STUDIES

Projects that show these roles at work

Each role group on this page has one project in these cards, so you can see that kind of work in a shipped product. A case page names the stack, what our team was responsible for and the results our client reports.

Read each for the part that was ours. On the payments platform we built the frontend, and the client's teams built the backend. On the logistics redesign our designers set the patterns first, then our team took part in the build, Angular on the front end and Node.js on the back.

Not sure which roles you need yet?

"If nobody on your side can review a pull request, more engineers will wait on you. That's when we suggest a project instead."

Dzmitry Kuchynski, Chief Operating Officer, Octalance

FAQ

What buyers ask us before they sign

How much does it cost to hire a developer?

It comes down to how many engineers you use, and the role and seniority behind each one's rate. Rates are agreed per engagement, so the quickest way to a figure is to send us the roles. How each model is billed, from an hourly rate under staff augmentation to a fixed price per milestone on a project, is in Engagement models and terms on this page.

Do I interview the engineers myself?

Under staff augmentation, yes, every one of them. With a managed team or project delivery, we set up the team and answer for it, so you can interview the key roles, and we select the rest.

What happens if an engineer isn't the right fit?

On a managed team, replacements are ours to handle and the team keeps its capacity. On a project, the team's make-up is ours, because we answer for the scope. Under staff augmentation we replace them within 14 days at no extra cost.

Will the engineers work only for us?

A UI/UX designer can be placed part-time if the work calls for it. Engineers work full-time for you alone, under staff augmentation and on a managed team, where we guarantee it.

Who owns the code you write for us?

You do. The code usually lives in your own repositories, sometimes in ours, and if you'd like an NDA before you share project details, we sign one at that stage. IP passes to you on payment, and handing everything over at the end is a routine part of the engagement.

How soon can an engineer start?

The start follows your interview. Once you've chosen someone, contracts and access usually take one to two days. The commitment in our hiring process covers presenting candidates, not a start date. A managed team starts within a month, depending on its size, and can begin with a few developers.

Do you staff roles that aren't listed here?

Yes. We also staff PHP, Go and JavaScript developers, Power BI and Google Cloud developers, project managers, business analysts and product managers, and site reliability and platform engineers. Name the role and the stack it works in when you write to us.