Hire AWS developers who build your app and infrastructure inside your team

You can hire AWS developers who passed a hands-on AWS assessment before their CV reaches your shortlist.

Abstract 3D illustration of a white cloud form resting on three layered slabs, the middle slab in orangeAbstract 3D illustration of a white cloud form resting on three layered slabs, the middle slab in orange

TECHNOLOGIES

AWS tools our engineers work with

EC2

Lambda

ECS and EKS

S3

RDS and DynamoDB

CloudWatch

IAM and VPC

CloudFormation

CodePipeline and CodeBuild

Terraform

Docker and Kubernetes

Amazon Redshift

Redshift Spectrum

Amazon Athena

AWS Glue

AWS Batch

WHAT THEY OWN

What will an AWS engineer own on your team?

An AWS developer builds your application and the infrastructure under it on AWS, and answers for what both cost to run. To hire one, tell us what the engineer will own. We present vetted candidates, and you interview them before anyone starts.

Prefer to hand over the whole job? We also take on AWS work as a project. Then we run the plan, the team and the milestones, and you make the product decisions. An engineer who joins your team usually owns one or more of these four areas.

Serverless and container apps

Backends on Lambda or on containers in ECS or EKS, with API Gateway in front, SQS, SNS, EventBridge and Step Functions between the parts, and Cognito for user sign-in.

Written in Python, Node.js, Java, .NET or Go. Lambda fits spiky, event-driven work. A service that is busy all day usually belongs in a container.

Data pipelines and warehousing

Our data work on AWS uses Amazon Redshift and Redshift Spectrum, Athena over files in S3, AWS Glue Studio, and AWS Batch with Docker.

Airflow schedules and watches each pipeline, and dbt turns raw tables into the models your reports read.

IaC and CI/CD pipelines

Terraform or CloudFormation, matched to what your team maintains today, with CodePipeline and CodeBuild for builds and releases.

An environment defined in code can be rebuilt from it, and rebuilding one is the quickest test of whether the code is complete.

Security, access and cost

IAM scoped to each role, KMS keys, Secrets Manager, CloudTrail logs, GuardDuty and Security Hub findings, and AWS Organizations with Control Tower when you run several accounts.

On cost, Cost Explorer and AWS Budgets show where the bill goes, and the choice between on-demand, Savings Plans and Spot follows the load.

Tell us which AWS services you run

Send the role, its seniority and the AWS services your product runs on. Matching starts from that brief.

WHICH ROLE

Do you need an AWS engineer, or another role?

Four roles that overlap on AWS, and where each one fits

AWS developers

An AWS developer knows one cloud in depth: its services, its access model and what each design costs to run. They build the application itself, such as a serverless backend on Lambda or a containerized service on ECS or EKS, and they own the CI/CD and the Redshift pipeline wiring of your AWS product. Hire one when the work is centered on that product. When it is centered on a delivery platform shared across clouds or clusters, such as Kubernetes operations and pipelines many teams use, you want a DevOps specialist.

Azure, Google Cloud and data engineers

We also staff Azure engineers. They are the right hire when your product, or a second product of yours, runs on Azure. A product on Google Cloud gets engineers with hands-on Google Cloud experience, who build the application and run its infrastructure there, as an AWS developer does on AWS.

If the work is centered on data modeling and warehouse design, dbt models included, a data engineer is the better fit, and we staff both roles. A quick test: when the first thing anyone will look at is a report, start with the data engineer.

Abstract 3D illustration of four white block stacks side by side, one capped in orange, four roles comparedAbstract 3D illustration of four white block stacks side by side, one capped in orange, four roles compared

HOW WE VET

How is an AWS engineer vetted before your interview?

What a candidate faces before reaching your shortlist

Three vetting steps

Every candidate we present has passed three steps. The technical skills assessment tests the languages and frameworks a candidate claims, at the seniority they claim. For an AWS engineer it covers AWS architecture and services (compute, storage, networking, IAM), IaC with Terraform, and CI/CD. It ends with a practical task on a real AWS setup, judged on what the design leaves exposed and what it costs to run. The soft-skills evaluation covers English, taking feedback and working in a team, and the third step is an analysis of their job history.

Some roles also get a live coding interview, where the candidate writes code and talks through their choices. A background check runs only when a client asks for one.

Why the task is judged on cost

Two designs can pass the same functional test and cost very different amounts to run. Picture a nightly job that takes ten minutes. One candidate gives it a server that stays on all day. Another starts it on a schedule and lets it stop. Both work, and one of them bills you for nearly 24 idle hours a day.

Your own interview

With staff augmentation, you interview each candidate before anyone starts, and you can turn one down on the CV or on the interview. Our technical interview and live coding, where the role has it, can be part of your own selection, with full visibility.

To test a candidate yourself, ask how they would keep an S3 bucket private, what they check in a Terraform plan before it is applied, and where they look first when the monthly bill jumps. The last answer tells you the most.

Abstract 3D illustration of white server blocks under an orange lens, one block lifted out for inspectionAbstract 3D illustration of white server blocks under an orange lens, one block lifted out for inspection

BY THE NUMBERS

7 years

Average experience, company-wide

80%+

Senior-level or above, company-wide

50+

Projects our team has delivered

3

Vetting steps for every candidate

AWS WORK

What AWS work have we done?

A patient portal and a lending platform on AWS

We built a Dutch eHealth provider's portal for patients and a UK-based fintech startup's lending platform, both Java and Angular applications that ran on AWS. Each served its Angular front end from S3 through CloudFront and ran its backend on EC2 behind an Application Load Balancer, with RDS PostgreSQL (Multi-AZ, KMS encryption), S3 for documents and files, Secrets Manager and CloudWatch.

A warehouse that couldn't keep up with a day's data

Our AWS data warehouse work for a mobile software developer started with extraction so slow that a day's data couldn't be downloaded within the day. We moved the pipelines from plain Python scripts to Airflow, changed the Redshift cluster and moved the heaviest data sources to Redshift Spectrum. We also built a separate pipeline on AWS Batch and Docker for an ML model's calculations. On that project, computing resources used fell 98.8%.

Fivetran and dbt pipelines into Amazon Redshift

A professional education company already had its warehouse on Amazon Redshift and needed pipelines to fill it. After studying its data sources, reporting needs and existing architecture, we chose Fivetran to load data from Salesforce, Shopify and SAP, and dbt to transform it inside Redshift, with validation and monitoring built into the workflows.

A warehouse on S3, Athena and AWS Glue Studio

A Web3 platform that evaluates DAO contributors kept paying for the same third-party API calls. We built it an external data warehouse on S3, Athena and AWS Glue Studio, with Python, Airflow and dbt, so the platform reads its own copy of the data. Updates went from weekly to daily.

Competitor ticket prices, collected on a schedule

For a bus travel company, we built a price-monitoring system that runs on AWS. It collected competitor prices from bus carriers and ticket aggregators weekly at launch, and daily as the system evolved. Each source has its own Airflow workflow, so a new aggregator is one more workflow and none of the others change. PostgreSQL stores the prices, and the client's main application uses them to adjust its own.

Overnight loads in place of nested views

We replaced the nested views in an overnight-loading warehouse for a biopharmaceutical company on AWS with tables that load incrementally. The views had fed one another so densely that changing one could disrupt the whole process. Now Airflow runs the Python loads in parallel within a 4–5-hour overnight window, and our client's Customer 360 dashboards are refreshed by the start of each working day.

Large course uploads straight to S3

Some course packages were too large to send through the backend, so we built signed-URL uploads to S3 for a compliance platform. The browser sends each package straight to S3, on a URL that expires within minutes and allows one file to one location. On the same project, we set up the CI/CD pipelines and the IaC.

Abstract 3D illustration of white data blocks flowing into an orange warehouse cylinder beside a row of server slabsAbstract 3D illustration of white data blocks flowing into an orange warehouse cylinder beside a row of server slabs

CASE STUDIES

AWS projects, from the code to the pipeline

On each of these projects our engineers wrote the software and set up the CI/CD that releases it to AWS. What runs there differs from one project to the next, from an app on ECS to a warehouse on Redshift and a data stream on MSK and EMR.

Ask any AWS candidate, ours included, whether they only wrote code that calls AWS or also owned how that code was built and released to production. An engineer who joins your team is usually asked to do both.

DAY TO DAY

Access, changes and who you get

Abstract 3D illustration of white blocks lined up at a keyed gate, one orange block let through to a white cloud formAbstract 3D illustration of white blocks lined up at a keyed gate, one orange block let through to a white cloud form

Access through accounts you issue

Engineers reach your AWS account only through named IAM or SSO accounts you issue, limited to what their role needs. When one leaves the engagement, all of that access is removed.

Changes through your process

Infrastructure changes are code in pull requests. Each one is reviewed with its plan before it is applied, and it follows your own change process.

Certified AWS engineers

We have certified AWS engineers on the team. A certificate shows someone passed an exam. The practical task shows whether they design something you would pay to run.

Hours that overlap with yours

US teams get 4+ hours of daily overlap with the West Coast, and more with the East Coast. EU and UK teams get the full CET/CEST day, and we shift schedules to match.

PROCESS

What happens after you send the role

These are usual times. What we commit to is presenting candidates within 7 days of your request, and no one joins until you have interviewed them. Hiring for other stacks too? We staff technology experts across languages and clouds.

  1. STEP 1

    Define the AWS role

    We pin down what the engineer will own, which AWS accounts and pipelines that covers, and who on your side they work with.

    1 day

  2. STEP 2

    Match vetted candidates

    We shortlist AWS engineers who join your team. Each has passed our three vetting steps, the AWS practical task included.

    1–2 days

  3. STEP 3

    Interview your shortlist

    You interview the candidates you choose and decide who joins.

    1 day

  4. STEP 4

    Contracts and access

    We handle contracts, the NDA and security setup, and you issue the engineer's named accounts in your AWS account.

    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.

Engineers for running AWS cheaply and safely

"Building on AWS and running it cheaply and safely are different skills. We hire for the second: it's what you pay for every month."

Dzmitry Kuchynski, Chief Operating Officer at Octalance

Dzmitry Kuchynski, Chief Operating Officer, Octalance

FAQ

Questions to settle before you add AWS engineers

Can an AWS engineer who joins us grow into a managed team?

Yes. Engineers placed through staff augmentation can grow into a dedicated AWS team that we manage. It is the next step when your priorities keep moving, the roles and capacity can be set up front, and you would rather not run the team day to day. You still set the priorities and own the backlog.

Can your engineers join our on-call rotation?

Yes. An engineer placed through staff augmentation can take part in your on-call rotation or incident process, on terms we agree with you, hours and billing included. Out-of-hours cover happens only when it is part of that agreement. We don't run shifts, so there is no 24/7 cover and no published response time.

Who owns the infrastructure code your engineers write?

You do, once it is paid for. The code usually lives in your repositories, and sometimes in ours. That includes the Terraform or CloudFormation that rebuilds your environments, so the setup doesn't live only in one engineer's head. We sign an NDA before the start, and at the end transition-out is routine.

How much does it cost to hire an AWS developer?

Staff augmentation is an hourly rate per engineer, set by role and seniority and invoiced monthly. What moves the total is how many engineers you use and how senior they are. Rates are agreed with each client once you have described the role, so the site lists none. A managed team and a project each have their own price type, set out under Engagement models and terms.

Are you an AWS partner, and are your engineers certified?

We are not an AWS partner and hold no partner tier. We do have certified AWS engineers on the team. What we can show you is the practical AWS task each candidate passes and the AWS projects we have delivered.

Can we ask for a lead-level AWS engineer?

Yes, under staff augmentation. A lead suits a piece of work nobody on your team has done before, such as a first move to containers or a new account structure, and your tech lead still sets the priorities. We assess leads a little differently from mid-level engineers, and you interview a lead like any other candidate.