> Chrome Mobile teams in Seattle and Kirkland, spanning four sub-teams in Chrome, with an emphasis on ...
It's not the number of engineers working on Chrome. It's the number of engineers who worked in that guy's Chrome Mobile team in a specific location. (It's not clear whether there were other teams working in Chrome Mobile in other offices). That's a team making mobile-specific improvements to Chrome or adapting it to the mobile environment, not a team making a browser from scratch. So it's ignoring the people working on the layout engine, rendering engine, the javascript engine, security, the desktop UI, codecs, web APIs, developer tools, networking and protocols, extension APIs and store, etc.
There is also absolutely no way Chrome had 23 engineers in 2012, but since you didn't give the source, I have no idea of exactly what tiny subset that number was actually representing.