I spent 12 weeks of Summer 2020 interning at LinkedIn as an Associate Product Manager, and it was nothing short of amazing. But if you are anything like me before the internship, you probably have very little idea what to expect or how to succeed.
I worked on the Messaging Abuse team under Trust, which meant my job was to prevent abusive messages on LinkedIn. Overall, my days involved a lot of meetings but also individual work time. Given this, my day roughly resolved around three themes:
Working on Main Project(s)
Envisioning what we should build. Intern projects are usually carved out by managers prior to the summer to make sure you're set up for success. That said, given the problem statement, there's still a lot of flexibility on the approach you take to solve it. So I spent a lot of time researching and brainstorming with teammates in order to come up with the right solution. This culminates in a doc called the Product Requirements Document (PRD) outlining the problem we're facing, why it's important, and how we're solving it; this was my main final deliverable.
Personally, I worked on one big project all summer from start (not to finish) because of its scope and complexity; I also knew other interns who worked on and shipped multiple smaller projects.
Getting the resources to build. Now you know what to build, you need to get the resources (time, headcount, technologies) to make it happen. For interns, this might has already been taken care of; but if your internship collides with quarterly planning season, you may get to participate the process of fighting for your projects to get funded, making prioritization decisions for the team, etc.
Building. Finally, with the solution in mind and resources in hand, you can start building! This involves setting timelines with engineers, designers, UX researchers, etc, and making sure that the project sticks to the timeline. When the project finally gets to ship, you will roll it out by phase (e.g. 1% → 10% → 50% → 100%) and closely follow the impact by working with data scientists (DS). Voila, that's the entire cycle!
Crises Diagnosis and Mitigation
As PMs, we look at metrics (data) a lot, and when unexpected irregularities happen, we need to find out what happened. This is a lot like working through product execution questions such as "as the PM for Instagram Stories, identify the root cause for a 10% drop in views last week." I worked a lot with business operations, DS, and eng in these cases.
When we do identify the root cause, we come up with mitigation plans, for both short and long terms. They might already be in our pipeline or completely new projects.
Personal Development & Social Events
One of my favorite part of the work is interacting with people with different functions, perspectives, and backgrounds. It's also worth highlighting the variety of roles in tech: you definitely don't have to code to work in tech! So here are some roles I worked closely with (again, these are simply how I interacted with them and by no means reflect their whole job):