Globalization Platform Lead
Fetch approached me when they wanted to support multiple languages, countries, and currencies. The problem was that they didn't know where to start.
Here's what we did
- We created a plan to focus on US Spanish first. Fetch couldn't have 100% of developer capacity dedicated to I18N work; staying within the US allowed us to simplify the amount of upfront work.
- I worked directly with BE engineers to architect a microservice which connects internal teams with external translation vendors. This service helped teams keep their commitment of < 10ms response time for each API call.
- I built a team of translators across multiple timezones. This team was built to adapt to Fetch's rapid pace of marketing content.