One Lenovo Business Analyst candidate described a recruiter and hiring manager conversation about past experience, then on-site meetings with peers and managers. Change impact analysis examples were a specific focus.
$78K
Avg. Base Comp
$95K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
The Business Analyst candidate who shared their account describes a conversational process rather than a technical test. The recruiter replied quickly after the application, and the first formal meeting included the recruiter and hiring manager together. They asked about the candidate's technical sales background and how they had handled various situations. The emphasis was on explaining that experience clearly and tying it to the Business Analyst role.
The topic that stood out was change impact analysis. The candidate was asked for concrete examples of how they had approached it in past roles and what insights they drew from the work. Prepare a couple of stories that cover what you analyzed, what you found, and what changed because of it. Be specific about how your analysis supported a business decision.
After those early conversations, the candidate met peers and other managers on site. The questions turned to hypothetical situations and how they would work within the team's structure, and the candidate found the conversations collaborative. Despite following up afterward, the candidate never heard a final decision and did not receive an offer. Treat all of this as a single candidate's experience, and keep other options moving while you wait.
Synthesized from 3 candidate 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 Lenovo process.
I went through a pretty standard Lenovo interview process, but the way it ended was frustrating. The first step was a HireVue that had about five questions total. It was mostly the usual “tell me about yourself” style prompt, plus a couple of sales-focused questions. The main one I remember was why I wanted to work in sales, so it felt more like they were checking motivation and communication than testing anything technical. After that, I had a longer process that stretched over about two weeks and included four interviews, with an invitation to a final interview at the end. One of the recurring questions was to walk through my resume, so I spent a lot of time explaining my background and how it connected to the role.
What stood out most was the lack of communication at the end. The scheduler accidentally sent me ’s resume and then suddenly cancelled my final interview. There was no real explanation, no feedback, and when I asked what happened I was basically told to “stay tuned.” After all of that, I eventually got a generic not selected email. The whole thing took around 2 hours of interview time, not counting prep, and the process felt disorganized enough that it definitely left a bad impression. My takeaway is to be ready for a very standard behavioral/sales screen, but also to expect a process that may not be very polished or responsive.
Prep tip from this candidate
Be ready to give a clean, concise walkthrough of your resume and a strong answer for why you want to work in sales. Since the HireVue was mostly self-intro and motivation questions, practice delivering those smoothly on camera.
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 Lenovo
Describing a data project and its challenges
| Question | |
|---|---|
| Uber Eats Customer Experience | |
| Boosting Instagram Stories | |
| Client Solution Pushback | |
| 2nd Highest Salary | |
| Prime to N | |
| Find the Missing Number | |
| Paired Products | |
| Upsell Transactions | |
| Recurring Character | |
| Retailer Data Warehouse | |
| Experiment Validity | |
| Cyclic Detection | |
| Size of Joins | |
| Random SQL Sample | |
| Google Maps Improvement | |
| Groups of Anagrams | |
| Categorize Sales | |
| Exam Scores | |
| Three Zebras | |
| Twenty Variants | |
| Cumulative Sales Since Last Restocking | |
| Bucket Test Scores | |
| Completed Shipments | |
| Reducing Error Margin | |
| Detecting ECG Tachycardia Runs | |
| Possibly Biased Coin | |
| Out of Stock Inventory | |
| Seller Type Modeling | |
| Walking Robot |
Synthesized from candidate reports. Individual experiences may vary.
The candidate heard back from the recruiter quickly after applying, which gave them confidence early on. The first detailed conversation came in the joint meeting with the hiring manager.
The first formal interview had the recruiter and hiring manager together. Questions were conversational and covered the candidate's technical sales background and how they had handled various situations. The goal seemed to be whether you can explain your experience clearly and connect it to the Business Analyst role.
The candidate was asked for concrete examples of change impact analysis and the insights drawn from that work. Prepare one or two examples that explain your approach, what you learned, and what outcome you influenced, rather than describing the topic in the abstract.
The candidate then met peers and other managers on site. The conversations felt collaborative, with hypothetical situations and questions about working within the team's structure. The candidate followed up afterward but did not hear a final decision and did not receive an offer.
