Lightricks Product Manager interview typically runs 5-6 rounds: HR screen, two home tasks, interviews, and senior leadership. It usually takes about 3.5 months and is often slowed by long gaps between stages.
$86K
Avg. Base Comp
$268K
Avg. Total Comp
5-6
Typical Rounds
3-4 months
Process Length
Our candidates report that Lightricks cares less about polished storytelling and more about whether you can stay steady when the process shifts under you. The clearest signal is the mismatch between what HR said and what senior leadership actually asked for: one candidate was told there would be no presentation, then was pressed to walk through research and present the work anyway. That kind of last-minute change suggests the team is watching for composure, adaptability, and ownership of your work more than for a rehearsed script.
A recurring theme is the amount of work expected for a Product Manager role. Multiple home tasks came up as a notable burden, and the candidate experience suggests the company uses take-home work to probe how you think through product problems in depth. We’ve also seen that the questions themselves can be fairly standard on the surface — like describing a product you built and the challenges behind it — but the real evaluation seems to happen in how concretely you connect decisions, tradeoffs, and outcomes. In other words, they want evidence that you can move from product intuition to execution without hand-holding.
What makes this process especially hard is not just the workload, but the lack of transparency around expectations and feedback. The candidate described long gaps between rounds and no response after asking for feedback, which means you should assume you may need to self-advocate for clarity at every step. The people who do best here are usually the ones who can handle ambiguity without losing momentum, and who can defend their work even when the format changes at the last minute.
Synthetized from 1 candidates reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Lightricks process.
The most frustrating part of my Lightricks process was how long it dragged on. It ended up taking about three and a half months and felt like five or six stages overall, depending on whether you count the initial HR screen. After each round, I often waited weeks, sometimes close to three weeks, just to hear whether I was moving forward, which made the whole thing feel much more drawn out than it needed to be.
The process included two home tasks, which already felt like a lot for a Product Manager role. The final stage was with senior leadership and was supposed to be a case study discussion. I was told by HR that I wouldn’t need to prepare or present anything, but once I got into the interview, they asked about my research and then asked me to present my work anyway. That mismatch was especially frustrating because it felt like the expectations had changed at the last minute. The only specific question I remember from the earlier part of the process was a fairly standard product question: tell me about a product you’ve built and the challenges you faced during development. Overall, the feedback I got along the way was positive, but the lack of transparency and the amount of time required made the experience exhausting. In the end I was rejected by email, and when I asked for feedback afterward, I never heard back.
Prep tip from this candidate
Be ready to walk through a product you built in detail, including the challenges and tradeoffs, and don’t assume a leadership case study will be purely conversational. Given the two home tasks and the final-stage presentation surprise, it would also be smart to clarify expectations in writing before investing time.
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 Lightricks
The role of A/B testing in measuring the success rate of an analytics experiment
| Question | |
|---|---|
| Best DAU | |
| Empty Neighborhoods | |
| Employee Salaries | |
| Button AB Test | |
| Top Three Salaries | |
| Subscription Overlap | |
| Experiment Validity | |
| Download Facts | |
| Liked Pages | |
| User Experience Percentage | |
| Distance Traveled | |
| Third Purchase | |
| Last Transaction | |
| Random Bucketing | |
| Hurdles In Data Projects | |
| Google Maps Improvement | |
| Network Experiment Design | |
| Attribution Rules | |
| Revenue Retention | |
| Fractional Shares | |
| Ad Comments | |
| WAU vs Open Rates | |
| Search Ranking | |
| Amateur Performance | |
| Uber User Journey | |
| Daily Retention Summary | |
| Christmas Dinner Ingredient Optimization | |
| Testing Price Increase | |
| Cancellation Fees |
Synthesized from candidate reports. Individual experiences may vary.
An initial screening with HR to discuss your background, role fit, and general interest in the Product Manager position. This appears to be the first step and may be counted separately from the rest of the process.
A product-related take-home task that likely evaluates your approach to product thinking, research, and problem solving. The candidate reported completing two home tasks in total, which made the process feel unusually long for the role.
A second take-home assignment, suggesting multiple rounds of asynchronous work before the final interviews. The experience indicates that Lightricks uses more than one written or case-based exercise in the PM process.
An interview focused on your product experience and how you handled challenges in building a product. One recalled question was: 'Tell me about a product you've built and the challenges you faced during development.'
The final stage was with senior leadership and was framed as a case study discussion. In practice, the candidate was asked about their research and then asked to present their work, despite being told beforehand that no preparation or presentation would be needed.