Product Manager Intern Review

Enter at 09:00. In the morning, as most of my team are based in the States, I perform data analysis tasks, ideate solutions or set up meetings with stakeholders. From 12:30 to 13:30, I'm on lunch break. The afternoon is sometimes filled with meetings. Towards the end of the day, I consolidate my findings. I finish at 17:30, though some days I stay later if I meet with Seattle stakeholders.

I've learned how to use software like Miro and Jira. I've learned how to manage dependencies within a team - especially if international communication leads to delays. I've developed professional confidence and an ability to drive meetings. I've developed my problem solving skills, focusing more on scalable processes rather than individual solutions.

I was given a lot of responsibility as I was the point of call for my particular initiative; this meant that stakeholders who were interested in the initiative were directed to me. On the flip side, I was responsible for chasing down stakeholders to drive momentum for the initiative. I was given assistance when I asked for it; however, this particular role requires a self-driven attitude.

I received a fair amount. There were company wide events for developing soft skills. Project specific guidance was given when I'd request it; however, I would say the first few weeks felt a little isolated as we were figuring out the line between asking for assistance and establishing independent thinking. Leaning too much on the latter meant it took a few weeks to feel like the project had momentum.

Great. The office is a fantastic place to work (free snacks, open kitchens, a games room, a rooftop terrace) and the employees are generally friendly and happy to help if you need it. The dress-code is incredibly relaxed. Furthermore, managers don't micromanage your day-to-day work. If you're a few minutes late to work, nobody bats an eye. What matters is the work you do. There were many social events, too.

I can genuinely say I've really enjoyed my time here. The culture had a large part to do with that, but the project specific support and responsibility given to me made me feel like my work was valued.

Yes

Prepare for the interview. Research the role you've applied for and look up mock interviews on YouTube. Don't be afraid to stop and think when asked a question. Write down your thoughts if it helps. At least for my role, a methodical approach with clear communication is a must at the interview stage. From there, if you get the role, I'd recommend being self-driven and taking ownership of your project.