Candidates describe a Sel software engineer process that starts with a short screen. Technical rounds then test C/C++ fundamentals, OOP, data structures and design reasoning, and one report includes a take-home and panel.
$81K
Avg. Base Comp
$90K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Candidates who interviewed for software roles at Sel describe a process that rewards fundamentals and clear explanation more than exotic puzzles. Three software-focused reports show a short recruiter or HR screen first, followed by technical conversations. The balance between coding and conceptual questions differs from report to report.
The C/C++ and OOP fundamentals theme is the most consistent. One software engineer candidate faced a one-hour Teams interview with no coding. It covered C++, object-oriented programming, operating systems, embedded concepts such as UART, watchdog timers and PWM, threads, mutexes, semaphores, the volatile keyword, caching and assembly-level questions. That candidate did not receive an offer and attributed it to gaps on basic C++ questions. An intern candidate was asked about bitwise versus logical OR and overloading versus overriding, alongside medium LeetCode-style problems, and received an offer.
An associate-level candidate reported a different shape: a logistics-focused recruiter call, a 24-hour take-home with two problems, and a panel of three meetings. Interviewers pressed on data structures, OOP, design patterns and the candidate's own take-home choices and trade-offs. That candidate received no offer despite positive feedback and reported long gaps between steps.
Practice talking through your reasoning aloud, since the intern candidate described interviewers as more interested in the thought process than a perfect answer. Be ready to defend every project on your resume. If the role leans embedded, review memory management and concurrency basics. Reports are limited, so expect some variation by team and level.
Synthesized from 5 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 Sel process.
I applied online and heard back within a few days for a phone screening. That was pretty quick—just a ten-minute call to assess my problem-solving approach. They were less interested in whether I got the perfect answer and more focused on how I thought through problems and explained my reasoning. A few days later, I was invited in for an in-person interview.
The technical rounds covered LeetCode-style medium questions along with some C/C++ conceptual material. They asked things like the difference between bitwise OR and logical OR, and what distinguishes function overloading from function overriding. Nothing too exotic—they were genuinely evaluating my thought process rather than trying to stump me. I also had a portion where they tested my knowledge based on the languages I'd listed on my resume. What stood out was how conversational it felt; the interviewers seemed interested in understanding how I'd approach a problem, not just the final answer.
The overall vibe across my interviews was approachable and focused on fundamentals. I received an offer and accepted.
Prep tip from this candidate
Focus on explaining your problem-solving process clearly, especially for C/C++ fundamentals like bitwise vs. logical operators and OOP concepts like overloading vs. overriding. They care more about your reasoning than a perfect solution.
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 Sel
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Prime to N | |
| Size of Joins | |
| Bagging vs Boosting | |
| The Brackets Problem | |
| Hurdles In Data Projects | |
| Real-Time Transaction Streaming | |
| Find Duplicate Numbers in a List | |
| Multi-Reaction | |
| RAG Strict Source Control | |
| Worker Distribution Dilemma | |
| Seller Type Modeling | |
| The Pirate’s Hunt | |
| Gas Station Counting | |
| Safe Deployments | |
| Fixed-Length Arrays: Deletion | |
| Text Editor With OOP | |
| Your Strengths and Weaknesses | |
| Azure Kubernetes Infrastructure | |
| Client Solution Pushback | |
| Why Do You Want to Work With Us | |
| Generative AI Privacy | |
| Closest SAT Scores | |
| Employee Salaries | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Merge Sorted Lists | |
| String Shift |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report a quick first call after applying online. One software engineer candidate got questions on company values, motivation for Sel and about six easy technical questions. An associate candidate was asked about start availability, salary expectations and relocation. An intern candidate described a ten-minute call on problem-solving approach.
One associate-level candidate reported a 24-hour take-home with two coding problems after the initial screen. The same candidate was later questioned on implementation choices and trade-offs. Other reports did not mention a take-home, so it may not apply to every software role or level.
Candidates report conceptual and coding questions covering C/C++ fundamentals, OOP, data structures and LeetCode-style mediums. One software engineer candidate had a one-hour Teams interview with no coding. It focused on resume projects, embedded concepts, threads and mutexes, memory management and assembly-level topics.
An associate candidate described three separate panel meetings with a director, team leads, and a lead plus architect. They focused on design patterns, data structures and the take-home. An intern candidate was invited in person and described a conversational format that tested knowledge of the languages on their resume.
Outcomes in the software reports were mixed. The intern candidate received and accepted an offer. The software engineer candidate heard back four days after the technical round with a rejection. The associate candidate received an automated rejection after a slow process with unexplained gaps between steps.
