Leidos Business Analyst interview typically runs 2 rounds: a group case discussion and an individual behavioral interview. It is usually in person and structured, often completed in one day.
$94K
Avg. Base Comp
$102K
Avg. Total Comp
2
Typical Rounds
1 day
Process Length
Our candidates report that Leidos is looking for a Business Analyst who can operate comfortably in a room full of stakeholders, not just someone who can talk through business concepts in the abstract. A recurring theme is the emphasis on resume-backed experience: interviewers had the candidate’s background in front of them and kept pulling on specifics around project coordination, budgets, timelines, and working with different people. That tells us the bar is less about polished theory and more about whether your past work maps cleanly to the day-to-day realities of the role.
We’ve also seen that Leidos cares about whether you understand the BA craft in a practical, delivery-oriented way. Multiple candidates reported questions on Agile requirements gathering and scrum processes, plus a light Excel check like VLOOKUP, which suggests they want confidence with the tools and language of execution. The non-obvious challenge here is the group case dynamic: with several people in the room, it can be harder to create momentum, so candidates who can speak clearly, stay concise, and contribute without dominating tend to stand out. In other words, Leidos seems to reward people who can translate experience into structured, collaborative problem solving under a fairly formal panel setup.
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 Leidos process.
The interview was in person and felt pretty structured, but also a little crowded. I was brought in during the day in DC, so between the commute, mass transit, and taking PTO, it was a bit of a hassle before the interview even started. The process had two parts. First, I was put into a group of four and given a case study to discuss for about 30 minutes, then we presented it to the interviewers. After that came an individual behavioral interview with two interviewers who had my resume in front of them and asked about my background and experience.
The behavioral portion was mostly about how I’d worked with different people on projects, along with questions about budgets, timelines, and group work. They also asked about Agile requirements gathering and scrum processes, so they did want to hear that I understood the BA side of the role, not just general teamwork. There was also a light technical Excel question, specifically how I would use VLOOKUP. The overall feel was more resume- and experience-based than algorithmic, but the panel style made it a little harder to build momentum because there were so many people in the room. I didn’t get any feedback afterward, and I ended up not getting an offer. If you’re preparing for this role, I’d be ready to talk clearly about Agile work, project coordination, and basic Excel functions, plus be comfortable speaking up in a group case discussion.
Prep tip from this candidate
Be ready to explain your experience with Agile requirements gathering and scrum in concrete terms, and practice a short case discussion/presentation since that was a core part of the in-person round. Also review basic Excel usage like VLOOKUP, since that came up directly.
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 Leidos
Write a function `sorting` from scratch to sort a list of strings in ascending alphabetical order
| Question | |
|---|---|
| Hurdles In Data Projects | |
| Your Strengths and Weaknesses | |
| First Touch Attribution | |
| Employee Project Budgets | |
| Detecting Firearm Sales | |
| P-value to a Layman | |
| Swipe Precision | |
| Project Budget Error | |
| Forecasting New Year Revenue | |
| Classification and Regression | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Slow SQL Query | |
| Liker's Likers | |
| Why Do You Want to Work With Us | |
| Client Solution Pushback | |
| Empty Neighborhoods | |
| 2nd Highest Salary | |
| Customer Orders | |
| Cumulative Distribution | |
| Rolling Bank Transactions | |
| Comments Histogram | |
| 500 Cards | |
| Employee Salaries | |
| Closest SAT Scores | |
| Button AB Test | |
| Top Three Salaries | |
| Subscription Overlap | |
| Month Over Month | |
| Paired Products |
Synthesized from candidate reports. Individual experiences may vary.
The process was conducted in person at the DC office and felt structured but crowded. Candidates were brought in during the day, and the interview included multiple interviewers in the room, making it feel more like a panel-style onsite than a simple one-on-one screen.
The first part of the interview was a group exercise with four candidates discussing a case study for about 30 minutes. The group then presented its recommendations to the interviewers, so candidates needed to contribute clearly and collaborate in a team setting.
After the group exercise, candidates completed an individual behavioral interview with two interviewers who had the resume in front of them. Questions focused on prior project experience, working with different stakeholders, budgets, timelines, group work, Agile requirements gathering, scrum processes, and a basic Excel/VLOOKUP question.