Schlumberger software engineer candidates report coding screens with heavy time and space complexity questions, project walkthroughs, technical interviews, and behavioral or manager conversations.
$113K
Avg. Base Comp
$129K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Candidates for Schlumberger software engineering roles describe a process where explaining your reasoning matters as much as producing working code. One candidate's HireVue coding screen put time and space complexity front and center. The first 15 minutes involved analyzing five code snippets, followed by three coding problems: two at roughly LeetCode medium level and one harder. That candidate's code ran but they did not advance, which suggests clear complexity reasoning matters.
Projects are the second major theme. Candidates report being asked to present or walk through a past project and explain their own role, the decisions they made, the motivation behind the work and the challenges they faced. One intern candidate gave a 10 to 15 minute project presentation followed by detailed follow-up questions.
Technical rounds vary. One candidate who received an offer describes two screen-shared technical rounds covering Scrum basics, low-level and some high-level system design, DSA, Java and SQL. Another describes an online test on computer science fundamentals and OOP, a group discussion, a DSA problem, and a round focused on REST APIs. Behavioral and manager conversations appear in later stages, covering teamwork, problem-solving, fit and why you want to work at the company.
Round counts and formats vary by role and team, so confirm the steps with your recruiter and review the fundamentals listed in your job description.
Synthesized from 24 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 Schlumberger process.
I applied through a career fair and the process started with a HireVue coding interview, which was the part that stood out the most to me. The first 15 minutes were not actual coding yet — they showed me five different code snippets and asked me to analyze each one’s time and space complexity. After that, I moved into three coding problems, where two felt like standard LeetCode medium-level questions and the last one was harder. The coding itself was fairly straightforward, but they kept coming back to complexity, so I had to explain my reasoning clearly instead of just getting the code to run.
Before that, I had a first round that was lighter: a short technical question plus a walk-through of myself and the projects I had worked on. That round was more about explaining my logic process than being difficult. I also heard the process could include a group discussion, a harder second technical round, and then HR and managerial rounds, while another path had a 60-minute interview focused on CV and full-stack topics like React and Flask, followed by a coding question and a coffee chat with the manager. In my case, the HireVue coding round was the main filter, and I didn’t make it through even though my code ran successfully. The biggest takeaway for me was that they care a lot about how you reason through complexity and how clearly you can talk through your projects, not just whether you can produce working code.
Prep tip from this candidate
Practice explaining time and space complexity out loud for multiple code snippets, not just solving problems. Also be ready to talk through your projects clearly and, if your path includes it, review basic DSA plus full-stack topics like React and Flask.
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 Schlumberger
Create top_ads with the top 3 ads and return the row counts for inner, left, right, and cross joins with ads
| Question | |
|---|---|
| Hurdles In Data Projects | |
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Prime to N | |
| Bagging vs Boosting | |
| The Brackets Problem | |
| 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 | |
| Why Do You Want to Work With Us | |
| Azure Kubernetes Infrastructure | |
| Client Solution Pushback | |
| 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 entering through a career fair or a direct application, and one describes a behavioral phone screening about background and interest in the company. Formats vary by role and team, so confirm with your recruiter which steps apply to you.
One candidate reports a HireVue coding screen that opened with complexity analysis of five code snippets, then three coding problems. Another describes an online test on computer science fundamentals and OOP plus two easy-to-medium coding problems. Explaining time and space complexity clearly appears to matter.
Candidates report technical rounds that probe past projects and fundamentals. Topics mentioned include system design, DSA, Java, SQL, REST APIs and Scrum basics. One candidate describes screen-sharing and talking through their thinking live, and the exact topics appear to vary by team.
Some candidates describe presenting or walking through a past project, in one case for 10 to 15 minutes followed by follow-up questions. Others describe panels probing their role, technical decisions and challenges on each project. Prepare to discuss your contributions and design choices in depth.
Candidates report behavioral or managerial interviews covering teamwork, problem-solving, motivation for the company and values. Outcomes differ: some candidates report offers and others did not advance.
