Who runs Octalance and how we vet engineers before you meet them

Every engineer we put forward, ours or a partner's, has passed three vetting steps. We present matched candidates within 7 days of your request.

Illustration of glossy building blocks fitting into a larger structure, standing for engineers joining a client's teamIllustration of glossy building blocks fitting into a larger structure, standing for engineers joining a client's team

The company

Who is Octalance?

Octalance is a software development outsourcing company. Our engineers are our own people, employed by Octalance or working with us on business-to-business contracts. When our bench can't fill a request fast enough, we bring in a partner's engineer and vet them the same way. Projects run in English. Systems we control are hosted in the EU. We work under GDPR as an EU company and sign a data processing agreement where we handle client data. Our engineers and delivery managers travel to your site for a kick-off or a workshop when you ask.

Our work runs through four practices, software engineering, data and analytics, AI development and cloud engineering. Each works two ways, with engineers who join your team or a project we deliver, and clients move between them. The page on how we work with clients compares all five models. Most of our published cases are in healthcare, fintech, telecommunications, travel and logistics, and the rest cover retail, edtech, AdTech and a few more fields. One eHealth software provider came back after we built its platform, and we went on to build its patient portal on top of it.

Locations and hours

Where our engineers work, and in which hours

Poland

CET/CEST, UTC+1, and UTC+2 in summer. Our default business hours run on this clock.

Lithuania

EET/EEST, UTC+2, and UTC+3 in summer. One hour ahead of Poland all year.

Ukraine

EET/EEST, UTC+2, and UTC+3 in summer.

Belarus

UTC+3 all year, with no clock change.

Georgia

UTC+4 all year, with no clock change.

Armenia

UTC+4 all year, with no clock change.

Hours for US, UK and EU teams

CET/CEST business hours are our default, and EU and UK clients get the full working day. For a US team we choose the location and shift the schedule, for 4+ hours of daily overlap with the West Coast and more with the East Coast.

Your choice of location

We staff strictly by your requirements. If a location doesn't suit you, we staff from another one.

Dot map with six highlighted points, one for each country our engineers work fromDot map with six highlighted points, one for each country our engineers work from

People

The people behind Octalance

Our engineers average 7 years of experience, and 80%+ are senior-level or above. Our team has delivered 50+ projects, counting our key engineers' work before Octalance. We have certified AWS, Azure, Databricks and Snowflake engineers. To add one to your team, start with the engineers you can hire.

Portrait of Dzmitry Kuchynski, Chief Operating Officer at Octalance

Dzmitry Kuchynski

Runs delivery at Octalance, including how our teams are put together, the architecture calls on client projects and the engineering read on data and AI work.

Chief Operating Officer

Portrait of Uładź Dzienisiewicz, Chief Business Development Officer at Octalance

Uładź Dzienisiewicz

Leads business development, starting with the first conversations with a new client about what they need and who on their side has to agree.

Chief Business Development Officer

Portrait of Mihail Gishkelyuk, Head of Technology Partnerships at Octalance

Mihail Gishkelyuk

Heads client partnerships: which engagement model fits, what drives scope and cost, and how we staff the team.

Head of Technology Partnerships

Vetting

Three vetting steps for every candidate

Illustration of small pieces passing through a row of arched gates and gathering in a tray at the endIllustration of small pieces passing through a row of arched gates and gathering in a tray at the end

Technical skills assessment

We test what a candidate claims. A data engineer gets a pipeline design task, an AWS engineer a real-world AWS setup, and a lead is tested differently from a mid-level engineer.

Soft-skills evaluation

We assess communication in English, how a candidate takes feedback and how they work in a team. A strong coder who bristles at every code review costs a team more than they add.

Job-history analysis

Our check of the candidate's CV. A CV says where someone has been, and the technical skills assessment says what they can do now, so the two steps answer different questions.

Live coding, for some roles

For some roles the candidate also writes code in a live session and talks us through it. It shows how they reason about a choice, which a take-home task hides.

Background check, on request

When you ask for one, we verify that the candidate's CV is genuine. The job-history analysis alone does not make that claim, so this is the step that does.

Process

How a staffing request runs, step by step

Each step shows its usual time. What we commit to is presenting matched candidates within 7 days of your request. Engineers who join your team work in your process and tools. A team we run works remotely in Agile sprints, with a demo every two weeks, Jira for tasks and Slack for daily work.

  1. STEP 1

    Role requirements

    We talk through the role you need to fill, its skills and seniority, and how the engineer will work with your team.

    1 day

  2. STEP 2

    Candidate matching

    We match candidates who have passed our three vetting steps, plus live coding where the role calls for it, against your requirements and build your shortlist.

    1–2 days

  3. STEP 3

    Your interview

    You interview the shortlist before anyone starts and can turn down any candidate. If you want, our technical interview and live coding can be part of your selection, with full visibility for you.

    1 day

  4. STEP 4

    Onboarding

    We sign the contracts and set up security and access with you, through named accounts you issue, so the engineer can start in your tools.

    1–2 days

How we 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.

Tell us who you need, or what you're building

Use the contact form to describe the roles you need or the product you have in mind, and we'll suggest where to start.