During the interview process candidates usually have a lot of questions about the team at foodpanda. This post tries to address the most common questions.
Where is the team located?
How big is the team?
Where is everybody from?
The members of the tech team come form 30 different countries, with Germany (17), Poland (11), Brasil (9), Spain (5) and Russia (4) being the Top5.
Needless to say that the common language is English. Speaking German is not needed …but pretty useful when living in Germany. Therefore foodpanda offers free classes twice a week.
What is the average age?
Meanwhile the average age is 31.7 years.
What hardware, OS and IDE do I have to use?
foodpanda provides every member of the tech team a new MacBook Pro with OSX or a ThinkPad with Linux / Windows. We allow / provide any software people need to be as productive as possible, no matter if they prefer to work within Vim / Docker / VMWare / professional IDEs / Sublime / etc.
How is the team structured?
After some other approaches in the past (for sure worth its own article some day), since the beginning of 2016 the tech team is structured in 5 main pillars, called “Stakeholder Verticals“. Each Vertical focuses their work towards one of foodpanda main stakeholders (see business model) and has its own goals, roadmap, blueprint country, KPIs, etc. Within these Verticals in many cases there are sub teams, temporary feature teams or other kinds of structures.
This Vertical approach was so successful in streamline efforts towards stakeholders and their needs that in summer 2016 also all other team at foodpanda (Marketing, CRM, Operations, Payment, etc) have been structured accordingly.
What process do the teams use?
The most important principle at foodpanda is that teams should be independent of each other. They should have no or only little dependencies between them and be able to accomplish their goals autonomously. Therefore team have full freedom regarding their processes. The only requirement is, that whatever they do, it needs to be documented, understood by all team members and under some kind of iterative review/improvement process. As a result some teams work according to SCRUM in most aspects, some selected KanBan and others something completely different – usually dependent on the size of the team, their seniority, the kind of product they build and at what stage of the product-life-cycle they are.
Is it possible to switch teams?
We try to keep teams as stable as possible to assure the maximum level of happiness and productivity, but we also support team members changing their team occasionally. Often this provides the possibility to engineers to work with different tools and technologies within our stack – eg switching from a LEMP Stack, to a node.js/angular.js or a Java environment.