Amazon.com's long-term vision is to enable a seamless experience for all Amazon customers worldwide on any Amazon website and device, in any language and for any culture. This extends the personalization of the shopping experience by allowing our customers to define their preferred language and currency and ensure that we provide an equivalent experience for our customers in their language of preference as we do customers in the default marketplace language.
Our team started in early 2014 and, as of July 2018, we have launched multiple languages in 4 different marketplaces (US, Canada, Japan and Germany). Our goal is to provide a framework allowing us to define and measure the quality of these experiences and accelerate language adoption across marketplaces. We believe that, by establishing a core libraries and services and providing tools and mechanisms, we can broadly influence change across Amazon's while and auditing the quality of our customer experiences.
You're looking for a career where you'll be able to build, to deliver, and to impress. You look at problems holistically, and thrive on the intricate complexity of designing feedback loops and ecosystems.
You want to work on projects where you are implementing solutions to real problems that require creative solutions and deep understanding of the problem space. You challenge yourself and others to constantly come up with better solutions. This highly visible role requires frequent communication with senior leadership in order to help shape and deliver on the product roadmap, and requires you to nimbly switch between strategic and tactical initiatives to achieve technical, business, and customer experience goals. You'll be given the unique opportunity to own and drive initiatives across the Amazon Retail as a whole -- from algorithmic innovation, all the way down to the datasets that the back-end services consume.
About us together:
We're going to change the way that Amazon thinks about supporting our global customer. Along the way, we're going to face seemingly impossible problems.
We're going to argue about how to solve them, and we'll work together to find a solution that is superior to each of the proposals we came in with. We'll make tough decisions, but we'll all understand why. We'll be the dream team.
The ideal engineer for this space will be highly quantitative, have great judgment and passion for building a great customer experience, be inventive, and have a strong track record of delivery. You also have a pragmatic approach and iterative approach to building software: you have an ability to simplify and get things done with a demonstrated track record of building and delivering software and working effectively with external and internal teams.
Some problem spaces we'll be working on:
LANGUAGE AND CURRENCY PLATFORM - we need to develop a platform and provide library support for the Amazon developer community that simplify development for our International customer and provide a unified experience, regardless of their location and preference. We will be instrumental in defining the standards and approaches used broadly across Amazon and developing mechanisms that will audit our customer experience ensuring that we can identify and address any measurable deviation. This platform and the libraries must support our mobile and desktop initiatives and must also be future-proofed to enable Amazon to continuously innovate.
LANGUAGE RELEASE - today releasing a language on an Amazon marketplace and we want to simplify this to be a simple configuration switch, so there is a large gap to bridge. Ultimately, our goal is to reduce the investment necessary such that business owners can ultimately self-serve and release languages as machine translations are available. We need to design a robust and scalable solution that can be adapted to the local marketplace needs while maintaining a consistent quality bar across Amazon.
DATAMART - as we release new languages across marketplaces, our business teams will want to understand customer trends and interactions with these new marketplaces. Ideally, we want to enable our business teams to report on the various languages within a marketplace as if those languages were individual businesses.
As such, we need to create a DataMart that enables all business metrics to be split by language and also enables business users to execute ad hoc queries to answer questions that we have not currently considered. As we create the DataMart, we will have to consider the scale of data that we will be handling (at the scale of Amazon's global retail business) and employ BigData techniques to aggregate and manipulate this data. We will need to design the platform to be robust and to seamlessly recover from disaster, should the need arise. Consistency and validation will be primary concerns as we understand that systems fail, specifically systems upon which we rely for signal and we need to protect our business teams from making decisions based upon incomplete information.
CUSTOMER EXPERIENCE - as arbiters of the customer experience, we need to understand our customers' experience in their languages of preference. Similarly, given the scope of this initiative, it is clear that we will not be able to translate all content in a single release.
As a result, it is critical that we can truly measure the customer experience as a function of our translations (both coverage and quality) throughout their journey within the Amazon marketplace. This is further complicated by the fact that our customers receive a unique experience based upon their browse history, so our method of measurement must be considerate of and support such a dynamic experience. Furthermore, in real time and with zero latency, we want to understand when the experience is broken so that we can take appropriate actions. This is going to be a challenge that may make use of the latest BigData streaming technologies to provide a real-time data and measurement pipeline.
AUDIT - we must put our customers first and foremost and develop mechanisms to drive and audit their multilingual experience. While we understand that the multilingual experience today has many gaps, we need to respect our customers and rapidly iterate to close these gaps and, all the while, measuring the impact to our customers. We will collaborate with the business teams to define the prioritization of features to be localized and provide metrics that make these prioritization decisions data driven.
You may already know if you're a fit, but perhaps you're worried about technology and experience requirements? Don't be - we're looking for smart, proven, engineers; if you're the right candidate, we're flexible.