Engineers first, since 2014
We started with twelve engineers and a rule about honesty. The firm has grown to 850 people. The rule has not moved.

Only promise what we can build and run

2014
Twelve engineers and one rule
Tarka started in 2014 with twelve engineers and one rule: only promise what we can build and run. Most IT services firms sell the plan and subcontract the work. We wanted to be the people who write the code, carry the pager and answer for the result.

The practices
One practice at a time, built by people who had shipped it
That rule shaped how we grew. We took on problems in the order we could solve them well: data platforms and cloud migrations first, then automation, then the machine learning and GenAI work that sits on top of them. Each practice was built by engineers who had already shipped the thing before we sold it.

Today
850 engineers, 11 countries, the same rule
Today 850 of us work across seven service lines for clients in 11 countries. The firm is bigger now and the rule is unchanged: scope what we can deliver, deliver it in production, and stay to run it if you want us to.
- Engineers and consultants, up from twelve in 2014
- 850+
- Countries where our clients work
- 11
- Engagements delivered
- 200+
- Client retention
- 94%

A note from our CEO
“We started Tarka with twelve engineers and one rule: only promise what we can build and run. Today 850 of us work across AI, data and cloud for clients in 11 countries, and the rule hasn’t changed.”
Rohan KaulCo-founder & CEO
Industries we work in
Five sectors where regulated data, large estates and round-the-clock operations make delivery discipline matter.
- Financial Services
- Banks and lenders that need GenAI and data work to pass model risk review, and finance teams that want the close measured in days.
- Healthcare
- Insurers and care providers automating document-heavy operations, with auditable evaluation and strict handling of personal data.
- Retail & E-commerce
- Omnichannel retailers who want faster, safer releases on the platforms their customers actually shop on.
- Logistics
- Groups moving workloads to the cloud and putting demand forecasting on top, then keeping the bill under control.
- Energy & Utilities
- Utilities that need customer systems available around the clock, run to a service level and improved every quarter.
How we hire and grow engineers


Hire for fundamentals
Candidates work through a short engineering exercise drawn from real delivery problems, with an engineer who will later work beside them. We look at how they reason, not which tools they have memorised.
Pair before you lead
New engineers join a live engagement alongside a senior engineer before they own a workstream. Reviews are about the code and the decision behind it.
Rotate across the stack
Engineers move between practices. A data engineer who has spent time on the AI team, and on a managed-services rota, designs better pipelines.
Run what you build
Engineers take part in the support rota for systems they shipped. It is the quickest way to learn what makes software easy to operate.
See how we work first-hand
Start with a conversation. A practice lead will walk you through the delivery model and the engineers you would work with.




