Leidos Software Engineer interviews typically mix a recruiter screen, a resume-focused technical conversation, and easy-level coding or OOP trivia, with round counts and follow-up speed varying widely across teams.
$123K
Avg. Base Comp
$160K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Leidos software engineer interviews lean more on resume depth and practical tool familiarity than on heavy algorithmic grinding. Candidates typically start with a recruiter contact, phone screen, or digital interview covering background and motivation. They then move into one or more technical conversations with a hiring manager, software architect, team lead, or small panel. Coding, when it appears, usually stays simple: reversing the words in a sentence, a basic array question, or a small coding question in a Java-focused round. One graduate candidate described a moderately hard coding challenge in a digital interview that also included a code review section.
What recurs most often is a deep dive into the candidate's own resume and projects. Interviewers ask for the specific tools, libraries, and implementation choices behind past work rather than textbook definitions. Expect OOP fundamentals and basic Java, Spring, or database questions. You may also get checks on technologies named in the job posting, such as Rust, OAuth, or the ELK stack, framed as practical screening rather than live coding. Some candidates also report:
Round counts and timelines vary by team and level. Formats range from a single 45-minute panel to multi-stage processes; one candidate waited nearly a month between rounds, and another described a three-to-six-month application process. One candidate who did not receive an offer never got a proper follow-up after multiple screens, so staying proactive with recruiters may help close the loop.
Synthesized from 18 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 Leidos 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 Leidos
Write a function `sorting` from scratch to sort a list of strings in ascending alphabetical order
| Question | |
|---|---|
| Hurdles In Data Projects | |
| KNN From Scratch | |
| Your Strengths and Weaknesses | |
| First Touch Attribution | |
| Employee Project Budgets | |
| P-value to a Layman | |
| Project Budget Error | |
| String Mapping | |
| Slow SQL Query | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Seller Type Modeling | |
| Liker's Likers | |
| Why Do You Want to Work With Us | |
| Client Solution Pushback | |
| 2nd Highest Salary | |
| Closest SAT Scores | |
| Employee Salaries | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Merge Sorted Lists | |
| Rolling Bank Transactions | |
| String Shift | |
| Customer Orders | |
| Comments Histogram | |
| Top 5 Turnover Risk | |
| Like Tracker | |
| Random SQL Sample |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report starting with a recruiter email, a phone screen, or an online application followed by a digital interview. These cover background and interest in Leidos. One candidate's digital interview included video questions, text responses, a code review section, and behavioral prompts. The tone is typically low-pressure and conversational.
A common thread is a thorough walk-through of resume projects. Interviewers ask for the specific tools, libraries, and implementation choices behind the work rather than high-level summaries. Candidates report this happening with a hiring manager, software architect, or small technical panel, and it often doubles as the main gauge of experience depth.
Candidates describe OOP trivia such as what public static void main means, basic Java, Spring, or database questions, and topics like C versus C++ or smart pointers. Others were asked about technologies named in the job posting, such as Rust, OAuth, or the ELK stack. These typically came up as conversational checks rather than live coding.
When a coding component appears, candidates describe simple problems like reversing the words in a sentence or a basic array question. One junior candidate faced a whiteboard technical test, and one graduate candidate described a moderately hard coding challenge. Others, including an intern, reported no live coding at all.
Later rounds can involve a panel of two to four people, including managers, senior or lead engineers, or project managers. Questions cover design patterns, working with difficult coworkers, and handling competing tasks. Camera-off interviewers were reported in more than one account, so format may differ by team.
Most candidates in these accounts received offers. However, one candidate who went through multiple screens never received a proper follow-up. Timelines also vary: one candidate waited nearly a month between stages, and another described a three-to-six-month application process.
