
What one Pluralsight Product Manager candidate reported: a recruiter phone screen, a video interview with the hiring manager, and weeks of silence afterward. Includes pay context and tips for handling a slow process.
$123K
Avg. Base Comp
$151K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
The one Pluralsight Product Manager interview report we have describes a short process: a recruiter phone screen, then a video interview with the hiring manager. The candidate says the recruiter screen went smoothly. The second round started with a broken video link, and the candidate says the recruiter had left the company between rounds without anyone telling them. The candidate then reached the hiring manager directly to start the call.
The hiring manager conversation felt natural to this candidate, but the questions were generic. It opened with "tell me about yourself," and the candidate felt the interviewer was not especially prepared. So prepare a concise, role-relevant career story and be ready to steer the conversation toward your product experience yourself. Don't count on tightly structured questions.
The outcome was no offer and no response. The candidate sent a thank-you note, followed up after a week and again at three weeks, and heard nothing. Applicants should keep their own pipeline moving, follow up politely once or twice, and not read silence as a verdict on their performance.
Pluralsight builds SaaS learning products, so examples of shipping software with engineers and designers on cross-functional teams are a sensible thing to have ready.
Synthesized from 1 candidate report by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Pluralsight process.
The process started simply enough with a recruiter phone screen, which went smoothly. Round two was scheduled as a video interview with the hiring manager, but the link didn't work—and it turned out the recruiter had been fired between rounds and no one had communicated that to me. There was some awkward scrambling to get a new link and connect directly with the hiring manager. Once we were on, the conversation felt natural and I thought it went well. She seemed engaged and agreeable with my responses. But as the call went on, I started noticing signs that she wasn't particularly prepared. The questions were pretty generic—the opener was just "tell me about yourself"—and her energy dipped noticeably as we talked. I left feeling like it had been decent, sent a follow-up thank you, checked in after a week, then again at three weeks. Nothing back. Complete radio silence. No rejection, no offer, no explanation. Just ghosted. It's hard not to feel frustrated when you've invested time in their process, especially after getting the sense that the hiring manager herself wasn't fully locked in. Looking back, I suspect the internal chaos—losing a recruiter between rounds, no communication, unprepared hiring manager—probably says something about how things run there. The silver lining is I found something much better.
Prep tip from this candidate
If you interview at Pluralsight, understand that internal communication issues may affect your experience. The hiring manager may ask very basic questions, so don't assume lack of depth means a strong signal either way. Most importantly, be prepared for the possibility of no response at all—follow up professionally once or twice, but don't assume silence means anything other than poor process.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Pluralsight
Explain what a p-value is to someone who is not technical
| Question | |
|---|---|
| Hurdles In Data Projects | |
| Digital Classroom System Design | |
| Related Jobs Optimization | |
| Your Strengths and Weaknesses | |
| Empty Neighborhoods | |
| Experiment Validity | |
| 2nd Highest Salary | |
| Top 3 Users | |
| Button AB Test | |
| Top Three Salaries | |
| Find the First Non-Repeating Character in a String | |
| Closest SAT Scores | |
| Manager Team Sizes | |
| Testing Price Increase | |
| Upsell Transactions | |
| Longest Streak Users | |
| Group Success | |
| Size of Joins | |
| Customer Orders | |
| Rolling Bank Transactions | |
| Comments Histogram | |
| Random SQL Sample | |
| User Experience Percentage | |
| Last Transaction | |
| WAU vs Open Rates | |
| Instagram TV Success | |
| Subscription Overlap | |
| Google Maps Improvement | |
| Employee Salaries (ETL Error) |
Synthesized from candidate reports. Individual experiences may vary.
The candidate reports the process began with a recruiter phone screen that went smoothly. Applicants may expect a basic introductory conversation, but the report doesn't describe specific questions. Have a short summary of your background and why you want this product role ready.
The candidate says this round was scheduled as a video interview with the hiring manager. The link failed, and the recruiter had reportedly left the company, so they connected with the manager directly. The questions were generic, starting with "tell me about yourself." Prepare a clear career narrative with product examples.
After the hiring manager call, the candidate sent a thank-you note and followed up after one week and again at three weeks. They report receiving no rejection, offer or explanation. Applicants may want to follow up politely a couple of times and keep other opportunities active while waiting.