Three candidates describe L3Harris software engineer interviews built around resume walkthroughs, behavioral and fit conversations, and basic technical topics such as OOP and C++ memory, not heavy algorithm drills.
$114K
Avg. Base Comp
$150K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
The three candidates who shared their L3Harris software engineer interviews describe conversations that center on your resume and your motivation far more than on algorithm puzzles.
One candidate met a recruiter at a career fair and had a single phone screen of about an hour. It covered their resume, whether they preferred front-end or back-end work, and why L3Harris appealed to them. There was no coding. They were sent an offer and declined it.
An internship candidate met the team at a job fair and then had two rounds. The first was a relaxed online behavioral panel of four people, covering past projects, challenges overcome and willingness to pick up hardware skills. The second was meant to be technical, and the candidate remembers a question on the pillars of OOP. They did not receive an offer.
The third candidate describes a fast process: a first conversation within a week of applying and an offer seven days after that. It mixed phone screening, management reviews, and technical and HR interviews. The technical questions focused on C++ fundamentals, including OOP principles and stack versus heap memory, plus a foundational live coding problem. Interviewers also asked how the candidate had actually built the projects on their resume.
To prepare, be ready to explain your projects, including the decisions you made and what you learned. Review OOP and, for C++ roles, memory management. Have a clear answer for why this mission and this kind of work appeal to you.
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 L3Harris Technologies 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 L3Harris Technologies
Swap the values of `a` and `b` in the dictionary without declaring any other variable
| Question | |
|---|---|
| International e-Commerce Warehouse | |
| Top 3 Users | |
| Over-Budget Projects | |
| Scrambled Tickets | |
| Hurdles In Data Projects | |
| Priority Queue Using Linked List | |
| Merge N Sorted Lists | |
| Nightly Job | |
| Slow SQL Query | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Loan Model | |
| User Event Data Pipeline | |
| Distributed Training Instability | |
| The Longest Journey | |
| Deciding Between Solutions | |
| Text Editor With OOP | |
| Seller Type Modeling | |
| Testing Constraints | |
| Client Solution Pushback | |
| The Pirate’s Hunt | |
| Triangle as Binary Array | |
| Repository Policy Enforcement | |
| Safe Deployments | |
| Distributed Authentication Model | |
| Fixed-Length Arrays: Deletion | |
| Why Do You Want to Work With Us | |
| Azure Kubernetes Infrastructure | |
| Your Strengths and Weaknesses | |
| Robotics Upgrade Tradeoff |
Synthesized from candidate reports. Individual experiences may vary.
Two candidates report meeting L3Harris people at a career or job fair before interviewing. A third reports a first conversation within a week of applying. However you get in, be ready to introduce yourself and your interests early.
Candidates report conversations about their resume, past projects and why they want L3Harris. One described a roughly one-hour phone screen with no coding. Another described a relaxed online panel of four that covered challenges overcome and openness to hardware work.
Where a technical round occurred, candidates report foundational topics. One was asked about the pillars of OOP. Another was quizzed on OOP, stack versus heap and memory management, and given a live coding problem described as foundational. Nobody described LeetCode-style depth.
One candidate reports management reviews and HR interviews mixed in with the technical ones, followed by an offer seven days after the first conversation. Another received an offer after a single phone screen and declined it. The internship candidate was not offered a role.
