
Progressive Business Analyst interviews, as candidates describe them, are behavioral and STAR-driven. Reports mention a recruiter screen, a video interview, and live conversations with a hiring manager or peer.
$90K
Avg. Base Comp
$100K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Candidates describe Progressive's business analyst interviews as conversations about past behavior rather than technical tests. The one report for the exact Business Analyst title came from a candidate who received an offer. They had braced for heavy technical questioning and instead moved through a recruiter call, a video interview made up of roughly eight behavioral prompts, and a phone interview scheduled about a week after the video. Prompts asked for a time they helped a customer beyond their normal duties and what attracted them to the role. They found that tight, clear answers landed well, and that asking about the team and day-to-day responsibilities helped.
A related report, for a senior IT business systems analyst position, describes two 45-minute conversations, first with a peer of the hiring manager and then with the manager. Topics included gathering requirements, handling conflict, adapting to change, and influencing others. That candidate saw no case studies or technical exercises and was turned down eight days later, even though both conversations felt positive.
The practical move is to build a short bench of specific stories: one on requirements, one on conflict or influence, one on improving a process, and one centered on a customer. Practice telling each in STAR order, and be ready to say plainly why Progressive and this role appeal to you. One candidate says missing the video stage means waiting six months to reapply, so treat it as a real screen. With only a couple of analyst-type reports, expect some variation by team.
Synthesized from 4 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 Progressive Insurance process.
I went into this interview expecting a rigorous technical deep dive, but Progressive kept things pretty straightforward and behavior-focused. The process started with a recruiter screen covering standard job-centered questions and my salary expectations—nothing tricky, just trying to get a sense of my background and fit. They were upfront about the next steps, which I appreciated.
The video interview came next with about eight typical behavioral questions spread across different rounds. They asked things like telling them about a time I went above my job duties to assist a customer, and they wanted me to frame answers around the STAR format. The questions leaned heavily into motivation and what actually drew me to the role itself, rather than complex problem-solving. I learned that being concise with my answers was key—the interviewing team seemed to appreciate clarity over rambling. I also made sure to ask thoughtful questions about the team dynamics and specific responsibilities, which seemed to resonate with them.
Once I completed the video interview, there was a phone interview scheduled within about a week if you moved forward. The whole process had a professional pace to it, and I never felt rushed or grilled. Multiple team members were involved, and everyone came across as genuinely nice. The main takeaway was that Progressive values behavioral clarity and cultural fit over technical fireworks in this role. If you don't pass the video interview, you have to wait six months to reapply, so it's worth taking it seriously even though it feels conversational.
Prep tip from this candidate
Prepare 4-5 solid STAR-format stories about specific accomplishments, especially examples of going above and beyond for customers or process improvements. Progressive heavily weights behavioral fit and motivation for the role, so practice articulating why the company and position genuinely interest you—vague answers stand out negatively.
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 Progressive Insurance
Describing a data project and its challenges
| Question | |
|---|---|
| Testing Constraints | |
| 2nd Highest Salary | |
| Bagging vs Boosting | |
| Employee Salaries | |
| Top Three Salaries | |
| P-value to a Layman | |
| Experiment Validity | |
| WAU vs Open Rates | |
| Size of Joins | |
| Total Spent on Products | |
| Random SQL Sample | |
| Get Top N Frequent Words | |
| Fair Coin | |
| Assumptions of Linear Regression | |
| Always Excited Users | |
| Three Zebras | |
| Precision and Recall | |
| Recruiting Leads | |
| Delivery Estimate Model | |
| Instagram TV Success | |
| Poker Pair | |
| Group Success | |
| Target Indices | |
| Success Measurement | |
| Classification and Regression | |
| Duplicate Rows | |
| Covariance vs Correlation | |
| Possibly Biased Coin | |
| HHT or HTT |
Synthesized from candidate reports. Individual experiences may vary.
The Business Analyst candidate says the process began with a recruiter call covering routine questions about the job and salary expectations. The recruiter laid out the next steps clearly. Plan to summarize your background, explain your interest in the role, and have a pay range ready, though the format may differ by team.
Next came a video interview of around eight behavioral prompts, where answers were expected in STAR format. One asked about going beyond your duties to help a customer, and others probed motivation for the role. Concise responses were appreciated. This candidate reports that not passing this stage means a six-month wait before reapplying.
The Business Analyst candidate was scheduled for a phone interview about a week after the video stage. Separately, a senior IT business systems analyst candidate describes two 45-minute sessions, one with a hiring manager's peer and one with the manager, on requirements gathering, conflict, adaptability and influence. Neither mentions technical exercises or case studies.