Stacks & teams

The stacks and platforms we staff

Two pools out of one delivery centre. Product and platform engineers who build software, and enterprise application specialists who configure, extend and integrate the estate — working to the same delivery standard rather than to two.

Product & platform engineering

Building and running software

AI & Machine Learning

The teams behind AI features that ship

AI/ML

Machine learning engineers who put models into production and keep them working, not notebooks that never ship.

LLM & RAG

Engineers who build retrieval-augmented systems that answer from your own data and admit when they cannot.

Data Engineering

Engineers who build the pipelines and schemas everything else depends on, and keep them trustworthy.

MLOps

Engineers who make model delivery boring — versioned, reproducible, monitored and reversible.

Frontend

Interfaces that hold up under real use

Angular

Angular engineers who have shipped and maintained large operational interfaces, not demos.

React

React engineers who have shipped operational products people use all day, not marketing pages.

Next.js

Next.js engineers who know when rendering on the server helps and when it only adds cost.

JavaScript

JavaScript and TypeScript engineers who work across browser and server rather than inside one framework.

Vue

Vue engineers who build for Vue 3 on its own terms instead of porting React habits across.

HTML/CSS

Front-end engineers who turn design into accessible, responsive markup that survives the next redesign.

Backend

APIs, data and the parts that must not fail

Node.js

Node engineers who run services in production and have been on call for the ones they wrote.

Python

Python engineers who build typed, tested services rather than scripts that grew into one.

.NET

.NET engineers who are equally at home in modern .NET and in the Framework estates still running the business.

Java

Java engineers who maintain and modernise the services larger organisations genuinely depend on.

PHP

PHP engineers who write modern PHP 8 and can also stabilise the legacy code you inherited.

Go

Go engineers who use the language where it wins — throughput, concurrency and small deployable binaries.

Mobile

Field apps that work without signal

React Native

Mobile engineers who ship apps that keep working in warehouses, on shop floors and in vans with no signal.

Flutter

Flutter engineers who get one codebase across both platforms without it feeling native to neither.

iOS

iOS engineers who build native apps that meet Apple's review bar and keep meeting it after each release.

Android

Android engineers who handle the device fragmentation that comes with any real field deployment.

PWA

Engineers who use progressive web apps where they genuinely beat shipping a native binary.

Enterprise applications

Configuring, extending and integrating the estate

SAP

Functional and technical people for the SAP estate

SAP Functional

Consultants who know what the process ought to be and where in SAP it is expressed — not only how to click through the configuration.

ABAP

ABAP developers who write enhancements where SAP intended them, so the next upgrade is an event rather than a project.

SAP Fiori / UI5

Fiori and UI5 developers building the screens people actually use, on OData services designed for the screen rather than exposed from a table.

SAP Integration

Consultants for the interfaces around SAP — Integration Suite, CPI, PI/PO, IDoc, and the reconciliation that proves they worked.

Oracle & ERP

Oracle, Dynamics 365 and the data underneath them

Oracle Fusion / EBS

Consultants for an Oracle estate somebody else configured — reading what it does before changing what it does.

Dynamics 365

Dynamics 365 developers and functional consultants who extend the platform where Microsoft intended, and keep the Power Platform around it honest.

Oracle PL/SQL

PL/SQL developers for the packages, batches and reconciliations that hold an enterprise estate together after hours.

ServiceNow & ITSM

Workflow, catalogue and platform development

ServiceNow

ServiceNow developers who build on the platform's own model rather than around it, so an upgrade stays a routine event.

Salesforce

Salesforce developers and administrators who keep the org governable — declarative first, Apex where it is genuinely needed.

SharePoint / M365

SharePoint and Microsoft 365 developers for the internal tools that grew out of a site and now need governing.

Integration & Eventing

MuleSoft, Kafka, APIs and the spine between systems

MuleSoft

MuleSoft developers who design the contract before the flow, and build for the second delivery of the same message.

Apache Kafka

Kafka engineers who treat topic design, ordering and replay as decisions to be made rather than defaults to be inherited.

Elasticsearch

Elasticsearch engineers who treat the mapping and the relevance as the product, not the cluster.

Functional & Business Analysis

Process, configuration and the specification behind it

Business Analysis

Analysts who write the exception path, not only the happy one, and produce something an engineer can build from.

Data Migration

Specialists for the part of a go-live that decides it — extraction, cleansing, load and the reconciliation that proves it worked.

Data & BI

Turning operational data into decisions

Power BI

Power BI developers who build models that stay correct, not dashboards that need explaining every month.

Tableau

Tableau developers who design for the question being asked rather than for the gallery.

QuickSight

Analytics engineers who deliver reporting inside an AWS estate without standing up a second data platform.

D3.js

Engineers who build the visualisations a charting library cannot, and keep them readable.

Snowflake

Snowflake engineers who model the warehouse deliberately and keep the credit bill attached to something someone decided.

Databricks

Databricks engineers who build pipelines that can be re-run safely, rather than notebooks that worked once.

Teams are built for companies in the United States and the Gulf — the UAE, Saudi Arabia, Qatar, Kuwait, Bahrain and Oman. The engineers are in Pune, which matters mostly for the clock. Dubai is ninety minutes behind us and Riyadh two and a half hours, so a Gulf team shares almost the whole working day. New York is nine and a half hours behind, so American engagements run on a written handover and one fixed overlap window rather than on a standing call — a real constraint, and better stated than discovered.

Name the stack and the seniority.

42 stacks and platforms across the two pools, all staffed from the same delivery centre. Tell us which one the work is in, how senior it needs to be and how long you expect it to run, and we will say what we can field and when — or that the stack you need is not one of these, which is also worth knowing before a call.