Technology notes

Nicole Junkermann on India's AI Engineers and the Wider Picture


On the engineers of India, the conditions they build under, and why the mental map of where useful technology comes from tends to lag a long way behind the real one.

Nicole Junkermann in a white tee shirt, standing in warm daylight against a pale concrete wall

There is a habit, comfortable and quite common in Britain, of picturing artificial intelligence as something that happens in two or three places and is then shipped everywhere else. It was never entirely true, and it is less true with every passing year. India is the clearest illustration, and the reason has little to do with announcements and a great deal to do with the daily work of engineers.

Start with scale, since it is the part that is easiest to underrate. India trains engineers in very large numbers, year after year, and a substantial proportion of them spend their working lives on software that has to function under real conditions rather than ideal ones. Modest hardware. Connections that come and go. Users with no patience whatsoever for a screen that hesitates. Constraints of that kind are not a handicap. They are an unusually strict teacher, and what they teach shows up in the work.

Then there is language. Daily life across the country runs in dozens of languages and several scripts, often within a single conversation. Anything meant to be genuinely useful there has to cope with that from the first week rather than treating it as a translation job to be handled later. That is a hard problem honestly faced, and tools that solve it properly tend to travel well, because the rest of the world is more multilingual than the software written for it usually admits.

What tends to emerge from work done under those conditions is recognisable:

  • A preference for tools that do one thing dependably over tools that do many things approximately.
  • Close attention to what happens on an older phone with two bars of signal.
  • Instructions written for somebody who will read them quickly, once, while busy.
  • An assumption that the person at the other end has no time to be impressed.

None of that is exotic. It is simply good engineering, arrived at by people with enough problems worth solving and enough appetite to keep at them. The wider picture is that such conditions are not concentrated in a few postcodes. They occur wherever trained people, real problems and stubbornness happen to coincide, and they are currently coinciding in India at considerable scale.

The reason this matters to a reader in Britain is modest and practical. It is a correction to the map, not a league table. Nobody needs to rank countries to notice that a good deal of careful work is being done a long way from where the conversation usually points, or that the habit of looking in only one direction gets more expensive the longer it is kept up.

Nicole Junkermann keeps the shorter observations in the tech notes and the longer sources on the reading list. The companion note on reinforcement learning and long horizons went up the day before, and the standards question is set out in what responsible AI looks like when it is done well.

Back to the blog → Read: maintenance as the real engineering →