
Lowe's Software Engineer interviews reported by candidates mix coding problems such as Longest Increasing Subsequence and DSA mediums with debugging scenarios, project discussion, and a behavioral HR conversation.
$110K
Avg. Base Comp
$120K
Avg. Total Comp
2-3 rounds
Typical Rounds
Not reported
Process Length
Candidates describe Lowe's Software Engineer interviews as a mix of algorithm practice and conversation about how you think, and the reports differ by hiring route. One candidate who went through a campus drive reports three rounds: a coding assessment with two medium data structures and algorithms problems, a technical round that walked through their background, and a relaxed HR round with behavioral questions. Another candidate, who had a few years of experience, reports a recruiter call followed by two team interviews. The first leaned toward debugging and problem solving, including how to start troubleshooting a printer that suddenly stops printing. It was followed by a Longest Increasing Subsequence coding challenge, so practice that problem and be ready to explain the approach as well as the code.
A third report, for a Senior Software Engineer UI role in Lowe's Innovation Labs, is a different track. That candidate did a short behavioral segment and TypeScript problems on CoderPad (string manipulation and a seating arrangement in a 2D array). The second round was building a React feature live, and the gap between the rounds was about two months. If you apply to a front-end role, expect platform questions, especially around React.
All three candidates report no offer, so use the reports as a guide to question styles rather than a prediction of outcomes. Prepare clean medium-level coding, a structured way to talk through debugging, and clear stories about your own projects and learning approach.
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 Lowe'S Companies, Inc. process.
First round was technical, interviewer asked only about projects and was not that good in experience and asking questions. Payload structure, kafka and related topics, java streams, and questions related to projects.
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 Lowe'S Companies, Inc.
Find the longest increasing subsequence in a list of integers.
| Question | |
|---|---|
| Clickstream Data | |
| Dijkstra implementation | |
| Hurdles In Data Projects | |
| Deer Density | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Monthly Customer Report | |
| Subscription Overlap | |
| Customer Orders | |
| Top 3 Users | |
| Random SQL Sample | |
| Scrambled Tickets | |
| Last Transaction | |
| Size of Joins | |
| Flight Records | |
| Prime to N | |
| Bagging vs Boosting | |
| Job Recommendation | |
| Over-Budget Projects | |
| Over 100 Dollars | |
| Maximum Profit | |
| Manager Team Sizes | |
| Retailer Data Warehouse | |
| Duplicate Rows | |
| Sum to N | |
| Type I and II Errors | |
| Max Quantity | |
| P-value to a Layman | |
| Youtube Recommendations |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report different entry points: a recruiter call before team interviews for an experienced hire, a campus drive for an early-career candidate, and a LinkedIn outreach for an Innovation Labs role. The recruiter screen is described as straightforward, so expect it to cover background and role fit.
The campus candidate reports a first-round assessment with two medium DSA problems that rewarded clean implementation under time pressure. Another candidate reports a Longest Increasing Subsequence problem within a team interview. Practicing medium problems in your strongest language is a sensible way to prepare.
One experienced candidate reports a team round centered on debugging, such as how to begin troubleshooting a printer that stops printing. The campus candidate reports a technical round that walked through their resume and learning approach. Interviewers may probe past projects, so be ready to explain your decisions.
The campus candidate describes a final HR round that was relaxed and mostly behavioral, focused on cultural fit. Prepare a few stories about projects, obstacles, and what you learned, since this stage may not be present in every process.
One Senior UI candidate reports TypeScript coding on CoderPad in the first round and a live React feature build in the second, with about two months between them. This is a single report for a senior front-end role, so treat it as relevant mainly if you are applying to a similar position.