1. It all starts with an interview with HR. The usual, see if you are a cultural fit. Specially because it’s such a diverse company from people all around the world. Are you energetic and driven. Proof you are proactive. And experience. 2. General Interview with head of product. 3. Product Manager take home test with Product Team. 4. On-SIte visit: 1. Interview with engineers 2. Interview with Solutions Consulting 3. Interview with PMs 4. Probably Lunch or coffee with the whole team 5. Senior Engineers/Systems Architect interview and case 6. CTO 7. CEO 5. Offer/No Offer 1. Initial Interview with Head of Product: Asks general questions of how you work as a PM. i.e. What products and projects you’ve been working on. -Go through the whole workflow of you get from idea to actually shipping feature or product. -If you’ve managed team and how you’ve done that. -Under which methodology (They use scrum) If he likes you then he will assign you homework, which in the past has been to pitch a new feature or product for Payworks. 2. Product Manager take home test: - For the assignment I got a week and when I presented other PMs from the team where joining him to ask me questions from my presentation. *Tips: Research thoroughly how Payworks work, their products and the POS/Payment industry. Don’t worry much on telling why, just focus on a feature that fits perfectly with the POS/Payment industry and you’ll be on the other side. Product team won’t ask much technical questions even though the team is very technical. As mentioned before focus on pitching a feature that fits. After the interview, the PM team gives feedback to HoP and he makes a decision if they move forward with next round. Next round is an on-site interview (you get flown to Munich which is pretty cool). 3. On-site interview: - Head of solutions consulting: Great guy, very technical but amazing for business as well. Will ask you mostly technical questions such as "What does a webhook do?" - Engineers: General technical questions, management and knowledge of agile methodology. How do you write user stories, how do you cope with client requirements. And personal questions. - Systems architect/Senior Engineers: They will get you with a couple of their senior engineers with most experience and time in the company, and test you on a technical case or problem solving case. However, the problem solving case will be industry related. They will first give you an overview on how a payment workflow works. Then build a case with a problem such as “What happens when shopper goes to store and makes payment, on the backend we don’t get a response from Acquirer, timeout is x amount and has a retry mechanism. What happens with charge?” Answer would be something like payment declined and then client gets charged after a while causing a double charge issue for shopper. Stuff like that. So try to do a bit of homework on payment workflows, however they will help you and guide you step by step. They want to see how you think and solve problems but be advise, all the company is very technical and you have to demonstrate that you have technical skills. - CTO: Very technical. Will ask you general questions about your experiences and some technical questions such as “How does the internet work” or “What is a DNS” - CEO: Will ask you about your experience, your life and motivations. "Do you have the drive to be part of the team?" - In the same on-site they will probably take you to lunch with a bunch of people or some coffee time. During this time, all the team will be evaluating you on a personal level, they want to get to know you, so don’t be shy. Also if you’re a good cultural fit. There has been cases int he past where candidate was great but could’t connect with people and got rejected. The whole process sounds really long but it’s extremely quick, or at least it used to be like that, since know they are hiring like crazy.