The frontend team at trivago consists of around 80 people organized into squads led by product managers and supported by product designers, engineers, and QA specialists. They perform extensive A/B testing and use various automation tools to ensure comprehensive test coverage. Continuous learning is encouraged through regular
•8m read time• From tech.trivago.com
Table of contents
Can you describe the structure of the frontend team at trivago?How many tests are typically running at the same time, and what does this mean for the frontend team?How do we avoid things breaking on the frontend, and what role does the QA team play in this important process?What technologies/tools are used in the QA team to ensure comprehensive test coverage?Can you share one or two examples where A/B testing have brought us learnings and changes to our frontend?Any recently accomplished project in the frontend team and its impact on our business that you would like to highlight?How do you foster a culture of continuous learning in trivago?Sort: