How to land a job as a Product Manager? (Deep Dive Inside)

Role Deep Dive: What does a Product Manager do and how can you be one?

We see the role of product managers everywhere. But it’s one of the most misunderstood roles in tech. Many like to think of the Product Manager as CEO of the product. But that’s simply not true.

Product managers need to exert their influence and not their authority. Product managers live in the intersection of user needs, business goals, and technology constraints. They are the glue or the bridge connecting different stakeholders and holding them true to the product vision.

So what does a typical day for a Product Manager look like? Read on below.

Typical PM functions and day-to-day tasks

A product manager shuttles constantly between people, data, and decisions. Almost every day breaks down into three repeating themes:

• Communicate & collaborate

• Learn & analyze

• Decide & document

These loops keep the product vision on track while guiding designers, engineers, marketers, sales reps, and executives toward a shared outcome.

Communicate & collaborate

Daily work starts and ends with conversations such as:

• Morning stand-up with engineering to remove blockers and clarify user stories

• Quick syncs with support or sales to capture fresh customer pain points

• Ad-hoc chats with UX or design to review wireframes or prototypes

• Executive check-ins to confirm the roadmap still aligns with business targets

Learn & analyze

An important part of a PM's job is to make sense of the data that's available to them:

• Pull usage or funnel metrics to see if yesterday’s release moved KPIs

• Read market or competitor updates to spot shifts in positioning

• Watch a user-testing session or customer interview replay and log themes

• Scan support tickets to quantify the impact of new bugs or UX friction

These activities feed tomorrow’s prioritization conversations.

Decide & document

In order to ensure that insight becomes action, PMs document their conversation. Each day a PM may:

• Re-order backlog items or refine acceptance criteria before the next sprint

• Update the product roadmap or “Now-Next-Later” board to reflect fresh evidence

• Write a short problem statement or hypothesis to kick-off deeper research

• Publish release notes or an FAQ draft for the upcoming launch

Key takeaways

• A PM’s day is a series of rapid context switches across various activities.

• Meetings dominate the calendar, but outcome-driven documentation ensures product vision comes to life.

• Continuous learning from users and metrics ensures every decision provides real user value.

Quick Links on Product Management

Where the hidden jobs live

LinkedIn is not the only place where you can find product management jobs. In fact, it is probably one of the worst places to find roles because it's out in the public, and by the time you apply, there could be thousands of applicants.

Check out these lesser-known places to find those hidden PM jobs.

Yeah, but what do they actually ask in an interview for a PM role?

Check out this extensive blog post that covers more than 50 PM questions asked in real interviews.

There couldn't be a better time to be a product manager.

I say this because product managers are the ones with vision, but in the past they had to depend on designers and engineers to build out their vision. Right now, using AI tools, a lot of product managers can bring their vision to life with just a few prompts.

Company Deep Dive: What does it take to work at Perplexity?

Originally founded in 2022, Perplexity is a conversational search engine that blends the power of large language models (LLMs) with real-time web search and transparent sourcing.

Culture & values: What Perplexity looks for

• Being a fast-growing startup, Perplexity's brand centers on curiosity, speed, and transparency.

• Strong fundamentals and technical expertise: Job descriptions emphasize system design, scaling LLM pipelines and end-to-end product thinking.

• Clear written communication: Applicants submit writing samples before the first call so the team can gauge clarity of thought.

• Bias for action: “Small teams, high quality, high velocity” is how CTO Denis Yarats describes the internal ethos; the company favors shipping quickly with minimal bureaucracy.

• User empathy: The mission is to “make reliable knowledge accessible to everyone,” so candidates who think in terms of user first will stand out.

Hiring process

Typical flow for both technical and non-technical roles:

1. Recruiter screen

2. Writing-sample review (submitted up front)

3. Technical or case interview (coding, system design, or role-specific scenario)

4. Hiring-manager interview that often includes deeper technical discussion even for managerial roles

👉 Read candidate experiences on Glassdoor. 

Vacancies

At the time of writing this, there were 56 open roles at Perplexity across domains.

Most positions are in-office in San Francisco or New York, Perplexity follows a hybrid work schedule with three days in the office.

How to stand out

• Study the product. Use Perplexity’s own modes (Web, Academic, Reasoning) to analyze a feature and propose an improvement; this shows user empathy and curiosity.

• Bring a writing sample that demonstrates clear explanation of a complex topic, this is usually the first screening gate.

• Highlight projects shipped under tight timelines.

• Be strong with technical concepts, especially those involving AI and Large Language Models.

So what role and company would you want us to cover next? Just hit reply and let me know, we read every single email!

See you in your inbox next Tuesday with more insights!

Level up your job search with zeke.so