Jobra
🐞Step 1 of Jobra:AI Debugging Rounds
DSA+AIPreparing you for both.
JOBRA · AI DEBUG ROUND (PREVIEW)sum.cpp
// buggy snippet
int total(vector<int>& a, int n) {
    int sum = 0;
    for (int i = 0; i <= n; i++) { // 🐞        sum += a[i];
    }
    return sum;
}
A real codebase. A real bug. You + AI.

Jobra drops you into a broken repo. Find it, fix it, ship it. AI helps you debug like on the job.

Prompt:Correct the loop condition
Tap 'Let Jobra fix it' below to simulate AI debugging...

SLB Software Engineer Interview Questions & Rounds

34 min read

How the SLB (Schlumberger) software engineer interview works: Java OA, group discussion, technical, managerial and HR rounds, from real candidate experiences.

In this article
On this page

[Draft] How to Crack SLB (Schlumberger): The Software Engineer Interview, From Real Experiences

Last updated November 20, 2026 · 26 min read · For campus software interns and new grads (full-time associate and full-stack roles)

Built by the Codinzhub team. This guide is built from SLB software engineer interview experiences that candidates shared, including posts and OA questions on Codinzhub. The process changes by year, college and track, so treat this as a map, not a promise.

The 30-second version. For SLB (Schlumberger) software engineer roles, hired mostly through Indian campus drives, the process starts with a CV and CGPA shortlist. Next comes an online assessment: in most reports, Java MCQs on theory and code output (two 10-minute sections in three reports), then 2 easy coding questions such as decimal to binary. A group discussion of about 10 candidates per group cut the field hard. Then came usually 2 technical interviews of 30 to 60 minutes, built around your resume projects, with OOP, easy DSA (arrays, strings, linked lists, BST) and SQL. Full-time loops added a managerial round and an HR round, all within one or two days. The key habit: know every line of your resume, answer OOP with an example and code, and stay grounded when asked "Why SLB?".

What this guide is, and what it is not

This guide is built from 11 candidate records of SLB (Schlumberger) software engineer hiring: 8 interview experiences shared on Codinzhub, a set of IIT BHU OA questions shared on Codinzhub, and 2 public candidate write-ups. Two pages from SLB's careers site supply process facts. All candidate records come from campus hiring in India, for software internships and full-time new grad roles. One record is dated 2026 and one 2023; most write-ups give no interview date and were published between 2023 and 2025. Older write-ups from 2017 to 2020 were read but not counted.

It is:

  • A map of the campus process, stage by stage, as candidates described it
  • The question patterns that keep coming back, with a six-week plan and matched practice problems

It is not:

  • A list of leaked questions or a promise of what you will be asked
  • An official description of SLB's process
  • A guide for experienced hires or field engineering roles, which the data does not cover
  • An offer rate. Outcomes in candidate posts are self-reported, not a statistical sample.

Important things to know before you start

These are the SLB-specific facts that should change how you prepare.

The OA tests Java, whatever language you code in. In 5 of the 9 OA records, the MCQs were Java theory and Java code-output or debugging questions, in short sections with their own 10-minute timers. One candidate who had learned DSA in C++ called this part hit or miss. One interviewer also asked for code in Java.

There is a group discussion, and it cuts hard. 6 records describe a GD, usually right after the OA and in groups of about 10. Only the top 3 to 5 per group moved on in the three reports that give a number. Candidates said the panel looked for clear, concise points and teamwork.

Your resume is the interview. Projects came up in 9 of the 10 technical-interview reports, and keywords on the resume drove the follow-ups (Sass, Docker, MongoDB, Firebase). The coding questions were mostly easy, so depth on your own work and on OOP is where candidates were separated.

Two more facts matter. The process is long and fast: the three full-time candidates had 4 to 6 rounds, within one or two days. And the managerial and HR rounds can eliminate you. One candidate with good technical feedback was rejected in the managerial round.

Round-by-round breakdown

Candidates described a campus process with up to seven steps: a CV and CGPA shortlist, a Java-heavy online assessment, a group discussion, usually two technical interviews, a managerial round, an HR round, and a quick decision. Not every drive used every step.

Stage 1: Application, where candidates applied

The 9 candidate records that name a channel all came through on-campus drives in India: 3rd-year software internships and final-year full-time roles. No record mentions a referral or an off-campus application.

ChannelWhat candidates said
Campus drive (internship)Software intern drives, one for the Pune location. One drive was open to CSAI, CS and IT students.
Campus drive (full-time)One drive listed Associate Software, Cloud, Data and DevOps Engineer and Business Analyst profiles. Another was open to CE, IT and EnTC. At IIT Kharagpur, an SLB Tech full-stack role was open to CS, EC and EE with a CGPA of 7 or more.
Careers site (official)SLB's careers site says you apply to one role at a time and can join a talent network. For digital technology roles it describes a recruiter conversation first, then interviews with the hiring manager and team.

What helped. The IIT Kharagpur candidate called the CV shortlist the first real filter, and advised 1 or 2 complete software projects or internships that show the data structures you used. In that candidate's view, positions of responsibility and extracurriculars had no value for the software role.

Recruitment fraud. SLB's careers site says it never asks for money during recruitment, and that genuine emails end in @slb.com, @careers.slb.com or @esign.slb.com.

Stage 2: Shortlisting, how candidates moved forward

Shortlisting started before the online assessment (OA) and continued after every round.

  1. CV and CGPA shortlist. Two intern drives shortlisted 200 students for the OA on CGPA and resume, one of them from about 1,500 applicants. A full-time drive sent the OA link to 333 of about 600. At IIT Kharagpur, the CV shortlist led straight to interviews.
  2. Communication-check call (two reports). In one Pune-location intern drive, the hiring portal FirstNaukri ran the first two rounds. The second was an abrupt call of about 1.5 minutes: introduce yourself, and is a team player or a team leader more important? Friends got "What do you know about Schlumberger?" and "Tell me about one of your projects". A full-time data-engineering drive had a telephonic round on hobbies and background.
  3. Cuts after each round. One 2023 intern drive went from 200 at the OA to 48 at the group discussion, 12 at the first technical interview, 6 at the second and 4 at HR.

What to do. The communication call can come without warning, so keep a 30-second introduction and a one-minute project summary ready once OA results are out.

Stage 3: Online assessment

Most drives in the data started with an online assessment (OA), a timed test taken before any interview. No record describes a separate phone screen. The IIT Kharagpur full-time drive went from the CV shortlist straight to interviews.

Online assessment

How it works. 6 of the 8 records that describe the format report multiple-choice questions (MCQs) plus 2 coding questions. In three of them the MCQs came as two sections of 10 Java questions, each with its own 10-minute timer: first theory, then code snippets to dry-run (trace by hand) or debug. Candidates called the coding easy: 20 minutes were enough for one, and another rated it LeetCode easy. The MCQ timers were the hard part. One candidate found 10 minutes too little for the long snippets. Test-case visibility and AI-tool policy were not reported.

At a glance

  • Length: Two 10-minute MCQ sections, then the coding part, about 60 to 90 minutes in all (3 of the 4 reports that give timing). A full-time data-engineering OA ran 1 hour 10 minutes.
  • Questions: MCQs plus 2 coding questions (6 of 8 reports). Other versions: 60 MCQs plus 1 coding question; aptitude plus 1 coding question; 2 coding questions plus 6 MCQs.
  • Platform: Not reported as a pattern. DoSelect (from home), an offline sitting and the FirstNaukri portal are each named once.
  • What was asked: Java theory and code-output MCQs (5 of 9 OA records) plus easy coding on number conversion, Fibonacci numbers and strings.
  • Most common: Decimal to binary conversion is the most repeated coding question, in 3 records.

The MCQs covered try-catch-finally, StringBuffer, inheritance and, in one report, serializable. One full-time candidate said the coding questions differed between candidates, though not in difficulty. The cut was steep: 48 of 200 and 55 of 200 moved on in two intern drives, and 121 of 333 in a full-time drive.

QuestionWhat it testsLevel
Java MCQs: theory, then predict the output or find the error in snippetsJava language depth, dry-running codeIntern, New grad, SWE
Convert a decimal (integer) number to binaryBase conversionIntern, New grad
Check whether a given number is a Fibonacci numberFibonacci propertyIntern
Convert a decimal number into an irreducible fractionFractions and GCDIntern

One full-time OA also asked whether two strings are anagrams; that task is listed under the technical interviews, where it also came up.

OA questions shared on Codinzhub. These IIT BHU pages are listed under the spelling "Schlumbergera", with the pattern "2 DSA + MCQs". Only the title and the start of the statement are public, so the technique is marked Not reported.

QuestionDriveTopic
Distance of two points from the originIIT BHU, date not shownNot reported
Count vowels whose neighbours are both consonantsIIT BHU, date not shownNot reported
Remove single vowels from a stringIIT BHU, date not shownNot reported

See all SLB OA questions in the question bank.

Stage 4: The interview loop

After the OA came a group discussion, then technical interviews, then managerial and HR rounds. 6 of the 10 records that describe technical interviews report 2 technical rounds, and the three that give a length put each at 30 to 60 minutes. Rounds often ran back to back: one full-time candidate finished every interview within 1.5 days, and another spent about 6 hours on campus, including a 3-hour wait. Interviews were in person in some reports and on MS Teams in one. No record describes an online code editor, so expect paper, a whiteboard or a shared screen.

Group discussion

At a glance

  • Format: One topic per group of about 10 candidates (4 of 6 reports). One 2023 intern drive split 12 students into two teams of 6, speaking for the topic for half the time and against it for the rest.
  • Length: Not reported as a pattern. One intern report describes two 1-minute turns per person.
  • What was asked: Current-affairs topics on social media, AI and electric vehicles (5 of 6 reports name a topic).
  • Most common: Social media (boon or bane, or its impact) is the most repeated topic, in 3 records.

The group discussion (GD) was a real filter: the top 3 per group of ten moved on in one intern drive, and about 4 or 5 per group in two other reports. Candidates said the panel watched communication, clarity, confidence and teamwork, and preferred concise points. Only 4 distinct topics were reported, so this round is short of the 5-question minimum.

Reported prompts.

  • Social media: boon or bane (its impact) (intern and full-time)
  • Which vehicles are better: fuel combustion or EVs? (intern)
  • AI: pros and cons (SDE, IIT Roorkee, 2026)
  • Artificial intelligence vs human intelligence (full-time)

Technical interviews

At a glance

  • Length: 30 to 60 minutes per round (3 of 3 reports that give a length).
  • Rounds: 2 technical interviews (6 of 10 reports).
  • Questions: A project discussion plus 2 to 4 short coding or concept questions, in the reports that list them.
  • What was asked: Resume projects (9 of 10), easy DSA coding (8 of 10), SQL or database questions (6 of 10) and OOP concepts or class design (5 of 10).
  • Most common: "Walk through a project on your resume" is by far the most repeated prompt, in 9 records. Writing classes with inheritance (a drone camera, a car) is the most repeated coding task, in 4 records.

Nearly every technical-interview report includes the resume, usually at the start of the round. Keywords on the resume drove the questions: Sass and CSS grid, Docker, MongoDB and Firebase. Stack questions also covered Node.js, Spring Boot, REST APIs and MERN. One intern report said the interviewer expected multiple approaches and a logical explanation, not just code. Another interviewer rejected a hashing answer and asked for O(1) extra space. A third wanted the code in Java although the candidate preferred C++.

Reported coding questions

QuestionFollow-upLevel
Write classes for a given object using inheritance (drone camera, car)Class design on a whiteboard from scenariosIntern, SWE
Insert into a BST, then level-order and zigzag traversalDelete a node and dry-run itNew grad, SWE
Find the one duplicate in an array in O(n) time and O(1) spaceInterviewer rejected the hashing answerSWE
Detect a loop in a linked list and remove itExplain more than one approachIntern
Linked list vs array, then sort a linked listQuestions on the candidate's merge sortNew grad
Check whether two strings are anagrams (brute force, then better)Write it in JavaNew grad, SWE

Reported OOP, database and other questions

QuestionFollow-upLevel
Walk through a project on your resume: what you built, why, and howDraw an ER diagram; a real-life problem the project facedIntern, New grad, SWE
Polymorphism: types, and a real-world example (vs abstraction)Not reportedIntern
Four pillars of OOP, then abstraction vs encapsulationTypes of inheritanceIntern
MySQL vs MongoDB (SQL vs NoSQL): real-life uses; MongoDB or Firebase?How do you connect to MongoDB?Intern, New grad
Design a database for a canteen management systemCross-questions and suggested changesNew grad
Puzzle: blind man and coinsTrain-and-man aptitude question in the same roundIntern

Other reported tasks (string and array basics, more linked-list work, SQL, a Dockerfile, two more puzzles) are in the question bank.

Managerial round

At a glance

  • Length: Not reported.
  • Who: A manager or a project manager (2 of 4 reports).
  • What was asked: Motivation, goals, competing offers, work style and your most significant project (3 of 4 reports give prompts).
  • Most common: "Where do you see yourself in a few years?" is the most repeated prompt, in 4 records across managerial, HR and technical rounds.

The round was conversational, and the IIT Kharagpur candidate said it felt similar to HR. It still eliminated people. One candidate with positive technical feedback was rejected here, and later felt she had sounded overconfident and talked a lot about a company where she had interned.

Reported questions.

  • Where do you see yourself in 3 to 5 years? What are your goals?
  • If Google (or your internship company) offered you a job, would you still pick SLB? If not SLB, what?
  • How comfortable are you in a group setting?
  • What qualities do you look for in an organisation you join?
  • How important are people at the office, and do personal connections affect your work?
  • How do you define success?
  • Introduce yourself apart from your technical side (family, schooling)

HR round

At a glance

  • Length: About 30 minutes in the one report that gives a length.
  • Who: Two HRs in one full-time drive. Other reports do not say.
  • What was asked: Why SLB, what you know about the company, goals, strengths and weaknesses, salary and relocation (4 of 4 reports).
  • Most common: No single prompt leads. "Why SLB?" and "What do you know about SLB?" each appear in 3 records.

One candidate was asked what they had learned from the company presentation, so take notes at the pre-placement talk.

Reported questions.

  • Why do you want to join SLB (Schlumberger)?
  • What do you know about SLB? How would you explain SLB to a new person?
  • What did you learn from the company presentation?
  • What skills do you bring to the table?
  • Your strengths and weaknesses
  • What are your salary expectations?
  • Are you willing to relocate to the assigned location?

See all managerial and HR questions in the question bank.

Stage 5: Decision and offer

Decision. No record describes a hiring committee, team matching or a level change. Decisions came quickly. The IIT Kharagpur candidate got an offer after 4 interviews on Day 1 of campus placements. A full-time data-engineering candidate was selected after 6 rounds, all within 1.5 days. Another full-time candidate was told results would come by the end of the day, after about 6 hours of rounds and waiting, and was rejected. SLB's careers site describes a final decision stage after the interviews and says applicants are told the status and outcome.

Offer. Offer types in the data were campus software internships and full-time campus roles (Associate Data Engineer, and a full-stack software engineer role at SLB Tech). Compensation and negotiation were not part of the records used for this guide, so they are left out.

The Codinzhub Next-Round Playbook

Candidates who moved on cleared a fast Java OA, held their own in the group discussion, explained their projects in depth, and stayed specific and grounded in the managerial and HR rounds.

To get past the application

  • Have 1 or 2 complete software projects or internships on your CV. The IIT Kharagpur candidate called the CV shortlist the first real filter.
  • Mind your CGPA. Two intern drives shortlisted for the OA on CGPA and resume, and one IIT Kharagpur role had a cut-off of 7.

To get past shortlisting

  • Some drives made a short, unannounced communication call. Keep a 30-second introduction and a one-minute project summary ready.

To get past the OA

  • Practise Java output prediction under a timer. Three reports had 10 minutes per 10 MCQs, and one candidate ran out of time on long snippets.
  • Do the 2 coding questions fast and cleanly. They were easy, and only about a quarter to just over a third of candidates moved on in three reports.

To get past the group discussion

  • Make 2 or 3 clear, distinct points and let others speak. The panel preferred concise, confident points and teamwork.
  • Read up on social media, AI and electric vehicles, the themes of the reported topics.

To get past the technical interviews

  • Prepare every project and every resume keyword. Projects came up in 9 of 10 technical-interview reports.
  • Answer OOP with a definition, an example and code, and give a brute force before a better approach. Be ready to code in Java: one interviewer insisted on it.

To get past the managerial and HR rounds

  • Prepare "Why SLB?", "What do you know about SLB?" and "Where do you see yourself in 3 to 5 years?", the most repeated prompts.
  • Stay confident but not overconfident, and keep answers about SLB rather than another company.

To get through the decision

  • Plan for a long day. Results came the same day or within 1.5 days in the two reports that describe timing.

How the loop differs by level

The data covers campus interns and campus full-time hires, with no experienced-hire records. Four records do not state a level. Each row rests on three or four reports, so read them as examples, not rules.

LevelWhat candidates describe
Intern (3rd-year campus internship)Four reports. A CGPA and resume shortlist, a Java MCQ OA with 2 easy coding questions, a group discussion, then 1 or 2 technical interviews on projects, OOP and easy DSA, with HR after that in one 2023 drive. One Pune-location drive used FirstNaukri for the test and a short communication call before a resume round on MS Teams.
New grad (full-time campus roles)Three reports: Associate Data Engineer, Fullstack Developer and an SLB Tech full-stack role. 4 to 6 rounds within one or two days: an OA or a CV-only shortlist, sometimes a GD or a telephonic check, 2 technical interviews (projects, basic DSA, SQL, database design), then managerial and HR rounds.
Level not stated (SDE, Software Developer)Four records with the same campus shape: an OA (2 coding questions plus MCQs), a group discussion, technical rounds on projects, OOP and DSA (BST insertion and traversals, a duplicate in O(1) space), and a managerial or HR round.

With four intern reports, interns are covered here rather than in a separate guide.

Most-asked topics

11 records have OA or technical-interview content; the counts show how many report a specific question on each topic. The signal is breadth at an easy level, not hard algorithms.

TopicSeen inReported examples
Resume and project deep dive9 of 11 recordsWalk through a project; draw its ER diagram; a real-life problem the project faced
Number conversion, math and bit tricks7 of 11 recordsDecimal to binary; Fibonacci check; irreducible fraction; duplicate in O(1) space
Java and OOP concepts, class design6 of 11 recordsJava code-output MCQs; polymorphism with examples; drone camera class
Easy array and string coding5 of 11 recordsAnagram check; reverse a string; sort 0s and 1s; remove duplicates
SQL and databases4 of 11 recordsMaximum salary; MySQL vs MongoDB; canteen management database
Linked lists3 of 11 recordsDetect and remove a loop; sort a linked list; rotate a list
Trees and BST3 of 11 recordsBST insert, then level-order and zigzag traversal; tree height trade-off
Web stack from your resume3 of 11 recordsSass vs CSS; start a back-end server; write a Dockerfile
Puzzles and aptitude2 of 11 recordsBlind man and coins; train and man; three squares from eight sticks

The question patterns that keep coming back

The questions group into seven patterns. None is hard on its own; gaps in breadth are what hurt.

1. Resume and project deep dive

The most repeated prompt, in 9 of 11 records. Interviewers follow every keyword: what the project solves, why this stack, how a part works, the data model. Prepare a two-minute walkthrough per project, plus one hard problem you hit.

Reported examples. Walk through a project and its implementation; draw an ER diagram for your project; a real-life problem with your OS project; MongoDB and Docker questions from resume keywords; Sass vs CSS because a project used Sass.

2. Java and OOP concepts, then class design

OOP shows up in the OA MCQs and in 5 of the 10 technical-interview records. The OA tests what a Java snippet prints; interviews test definitions, then ask you to write classes. Answer with a definition, an example and a few lines of code.

Reported examples. The four pillars; abstraction vs encapsulation; polymorphism types with an example; the ambiguity problem in multiple inheritance; a drone camera class using inheritance; a car class; all the ways to create an object in Java.

3. Number conversion, math and bit tricks

This pattern carries the OA coding, in 7 of 11 records. Know base conversion, a Fibonacci test, GCD and XOR tricks.

Reported examples. Decimal to binary; check whether a number is a Fibonacci number; decimal to an irreducible fraction; one duplicate in O(1) extra space; the element that appears three times when the rest appear twice.

4. Easy array and string coding

Short tasks of one loop, two pointers or a hash set, in 5 of 11 records. Interviewers asked for a brute force and then a better approach. State the complexity as you finish.

Reported examples. Anagram check (brute force, then better); reverse a string; reverse an array; sort 0s and 1s; remove duplicates; turn "SHWETA" into "S_H_W_E_T_A".

5. Linked lists, trees and BST

Linked lists appear in 3 records and trees in 3: classic pointer problems plus trade-offs, such as linked list vs array. Draw the pointers first.

Reported examples. Detect and remove a loop; sort a linked list; rotate a list; a circular singly linked list; BST insert, then level-order and zigzag traversal; is a greater or smaller tree height better?

6. SQL and databases

SQL or database questions appear in 6 of the 10 technical-interview records, from a one-line query to a small schema. For schemas, list entities, keys and relations, then adapt to new requirements.

Reported examples. Maximum salary; which query shows a table's rows and columns; MySQL vs MongoDB with real uses; MongoDB or Firebase; a canteen management database.

7. Puzzles and aptitude

Two records include puzzles inside a technical round. Think aloud: the reasoning is what gets watched.

Reported examples. Blind man and coins; the train-and-man problem; exactly 3 squares from four 10 cm and four 5 cm sticks; which way a drawn bus is going.

Preparing for the managerial and HR rounds

The last two rounds are conversations about you, your goals and why SLB. They are not formalities: one candidate who passed the technical round was eliminated in the managerial round.

Build your story bank. Prepare short, real answers, each under two minutes, for the themes candidates were asked about:

ThemeReported prompt (paraphrased)Follow-up to expect
MotivationWhy do you want to join SLB?What do you know about SLB, and what did you learn from the presentation?
CommitmentIf Google or your internship company made an offer, would you still pick SLB?If not SLB, then what? Which company is your top choice?
GoalsWhere do you see yourself in 3 to 5 years?Long-term and short-term goals
Work styleHow comfortable are you in a group setting? Team or alone?How important are people and personal connections at work?
Self-awarenessYour strengths and weaknesses; how do you define success?Personal attributes; what skills you bring
LogisticsSalary expectations; willing to relocate?Not reported

Know the company. "What do you know about SLB?" and "Why SLB?" each appear in 3 records. Read what the business does and attend the company presentation.

Keep the focus on SLB. When asked about other offers, answer honestly and bring the answer back to why SLB fits you.

Use real experiences, and say "I" for your own actions.

A six-week plan

This plan follows the patterns above, most frequent first, and ends with mocks of the real rounds. Plan on two focused hours a day, and favour breadth over hard DSA.

  1. Week 1: Your resume and projects. Write a two-minute walkthrough and an ER diagram for each project. List every resume keyword and prepare two questions on each. Habit: explain one project out loud daily.
  2. Week 2: Number conversion, math and bit tricks. Decimal to binary, the Fibonacci check, fractions and GCD, XOR tricks. Habit: code each one in Java and in your main language.
  3. Week 3: Java and OOP. The four pillars, abstraction vs encapsulation, polymorphism, multiple-inheritance ambiguity, object creation, class hierarchies. Do 20 Java output-prediction questions a day on try-catch-finally, StringBuffer and inheritance.
  4. Week 4: Arrays, strings, SQL and databases. Anagrams, reversal, duplicates, 0s and 1s; basic SQL (maximum salary, reading table structure); MySQL vs MongoDB; one small schema such as a canteen system. Habit: brute force first, then better.
  5. Week 5: Linked lists, trees and puzzles. Loop removal, sorting and rotating a list, a circular list, BST insert and delete, level-order and zigzag traversal. Practise classic puzzles out loud.
  6. Week 6: Mocks. Two timed OAs (two 10-minute sections of 10 Java MCQs, then 2 easy coding questions), one group discussion with friends, two technical mocks that start from your projects, and one managerial and HR mock.

Interns can go lighter on database design: the reported schema prompt came from a full-time round. Full-time candidates should practise managerial answers early, because their loops had more rounds.

Only two weeks? Spend 3 days on projects and resume keywords, 3 on Java and OOP with timed MCQs, 3 on easy array, string and number-conversion coding, 2 on linked lists and BST, 1 on SQL, and 2 on OA, GD and HR mocks.

Practice problems that match these experiences

These practice problems match the patterns above. They are not claims about SLB's question bank unless a row says the problem was asked as-is. The OOP, project and managerial patterns have no single practice problem, so prepare them from your own projects and notes.

#Practice problemPatternSeen in these experiences as
1Decimal to Binary Conversion ProgramNumber conversionAsked as-is in OAs in 3 records
2Check if a Given Number is Fibonacci number?Number propertiesAsked as-is in OAs in 2 records
3Convert given Decimal number into an irreducible FractionFractions and GCDThe only coding question in a FirstNaukri-run intern test
4Valid AnagramCharacter countingAsked as-is in one OA and one technical interview
5Detect and Remove Loop in Linked ListFast and slow pointersAsked as-is in an intern technical round
6Sort ListMerge sort on a linked listAsked as-is in a full-time technical round
7Binary Tree Zigzag Level Order TraversalLevel-order traversalThe last step after BST insertion and level-order traversal
8Find the Duplicate NumberConstant-space duplicate findingSimilar to the one-duplicate question asked with an O(1) space limit
9Single NumberXOR tricksSimilar to finding the element that appears three times
10Add BinaryString arithmetic with carryAsked as-is in a full-time technical round

How to handle a question you have never seen

SLB's technical rounds mix projects, OOP, easy coding and the odd puzzle, often pulled from your resume. A steady method matters more than a memorised answer.

  1. Restate the question with one example. For coding, write a small input and its output. For a concept or puzzle, say what you think is being asked.
  2. Say the simple approach first. One interviewer expected multiple approaches, so a brute force is a start, not a failure.
  3. Improve it out loud. Name what is slow or uses memory. One interviewer pushed from hashing to O(1) extra space.
  4. If it is outside what you studied, say so and reason from what you know. One intern hit MERN and API questions beyond the syllabus. Tie the question to something you built instead of going silent.
  5. Code in small pieces while talking, in the language asked for (Java in one report).
  6. Trace one example by hand, as one candidate did on a sample BST, and fix what breaks.

Why candidates were rejected

Six rejected reports are in the data, and most give no reason. Read this section as lessons from self-reflection and one piece of interviewer feedback, not as SLB's stated criteria.

  • Stack questions you could not answer. A 2023 intern's second technical round moved to MERN, REST APIs, testing and file formats the candidate had not studied, and the candidate was not moved to HR. Another candidate could not answer all the ways to create a Java object, or Spring Boot with React.
  • Weak use of your own experience. One candidate's interviewer said she had not made good use of her internship. She was later eliminated in the managerial round, and felt she had sounded overconfident and talked too much about another company.
  • Easy answers are not enough on their own. One intern answered every easy coding question and was not selected for round 3. No reason was given.
  • Project rounds can end the process. A 2026 SDE candidate at IIT Roorkee was rejected in a round on an OS project and a real-life problem with it. A Pune-location intern was eliminated in a resume-probing round.
  • Code that breaks under questions. One full-time candidate described a "broken" merge-sort answer for sorting a linked list, and was rejected at the end of a 6-round day. No reason was given.

Selected vs. rejected: do this, not that

Only two selected candidates described their rounds, so this table leans on rejected candidates' reflections.

Do thisNot thatWhat the reports show
Own every resume keyword: be ready to explain and code with each tool you listPadding the resume: listing a stack you used onceInterviewers picked Sass, Docker, MongoDB and Firebase questions from resumes. One intern lost a round to MERN and API questions beyond what they had studied.
Give a definition, an example and code for OOP questionsReciting definitions onlyOne intern was praised for concept clarity after giving real-life examples. The same topics recur across records.
Show more than one approach: brute force, then betterStopping at the first working answerOne interviewer expected multiple approaches. Another rejected a hashing answer and asked for O(1) space.
Talk through your code as you write itCoding in silenceA rejected intern advised saying out loud whatever you are doing on paper.
Stay grounded in the managerial round: confident, specific and focused on SLBOverconfidence or praising another companyOne candidate felt these two habits cost her the managerial round after strong technical feedback.

If you remember only five things

  1. The process is a campus funnel. A CV and CGPA shortlist, a Java OA, a group discussion, usually 2 technical interviews, then managerial and HR rounds. Full-time loops ran in one or two days.
  2. The OA tests Java under short timers. Two 10-minute MCQ sections on Java theory and code output, then 2 easy coding questions such as decimal to binary.
  3. Prepare for the group discussion. It cut groups of about 10 down to 3 to 5 in the reports that give numbers.
  4. Projects decide the technical rounds. Projects came up in 9 of 10 technical-interview reports, alongside OOP, easy DSA and SQL.
  5. Do not coast through the managerial and HR rounds. Prepare "Why SLB?", what you know about SLB, and your goals, and keep the focus on SLB.

FAQ

Does every drive start with an online assessment?

No. Most drives in the data started with one. The IIT Kharagpur full-time drive went from a CV shortlist straight to 4 interviews.

Do I have to know Java?

For the OA, yes in most reports. 5 of the 9 OA records describe Java-only MCQs. Language rules for the coding questions were not reported, and one interviewer asked for interview code in Java.

How hard is the coding?

Mostly easy: OA coding was rated easy, and interview coding was short array, string, linked-list and BST tasks. One interviewer still pushed for O(1) extra space.

Is system design asked?

Rarely. One full-time candidate designed a database for a canteen management system. Several had to write classes using inheritance, the closest common task.

Is it virtual or in person?

Both appear. Some reports describe in-person rounds on campus, one Pune-location intern drive held its resume round on MS Teams, and one OA was taken from home.

About this guide

The Codinzhub team researched and wrote this guide from 11 records of SLB (Schlumberger) software engineer interviews, including experiences and OA questions shared on Codinzhub, plus SLB's careers site for process facts. We kept only what candidates described. The questions are our own short summaries, and the practice links are similar problems unless marked as asked as-is. If you interviewed recently, share your experience on Codinzhub and we will update this guide.

Disclaimer. SLB's process changes by role, year and college. Use this guide to build a foundation, and confirm the current format with your placement cell or recruiter.

Search the question bank

The questions from each round above, with practice links for similar problems. Log in to search every question we collected for this role, including questions shared on Codinzhub.

Showing 20 of 100 questions

  • Distance of two points from the origin

    A Schlumberger Slb online assessment question shared on Codinzhub (IIT BHU, date not shown).

    On CodinzhubIIT BHU, date not shownNot reportedCodingOnline assessment
  • Count vowels whose neighbours are both consonants

    A Schlumberger Slb online assessment question shared on Codinzhub (IIT BHU, date not shown).

    On CodinzhubIIT BHU, date not shownNot reportedCodingOnline assessment
  • Remove single vowels from a string

    A Schlumberger Slb online assessment question shared on Codinzhub (IIT BHU, date not shown).

    On CodinzhubIIT BHU, date not shownNot reportedCodingOnline assessment
  • Java MCQs: theory, then predict the output or find the error in snippets

    Level: Intern, New grad, SWE.

    Java language depth, dry-running codeCodingOnline assessment
  • Convert a decimal (integer) number to binary

    Level: Intern, New grad.

    Base conversionCodingOnline assessment
  • Check whether a given number is a Fibonacci number

    Level: Intern.

    Fibonacci propertyCodingOnline assessment
  • Convert a decimal number into an irreducible fraction

    Level: Intern.

    Fractions and GCDCodingOnline assessment
  • Write classes for a given object using inheritance (drone camera, car)

    Level: Intern, SWE.

    Class design on a whiteboard from scenariosCodingRound not stated
  • Insert into a BST, then level-order and zigzag traversal

    Level: New grad, SWE.

    Delete a node and dry-run itCodingRound not stated
  • Find the one duplicate in an array in O(n) time and O(1) space

    Level: SWE.

    Interviewer rejected the hashing answerCodingRound not stated
  • Detect a loop in a linked list and remove it

    Level: Intern.

    Explain more than one approachCodingRound not stated
  • Linked list vs array, then sort a linked list

    Level: New grad.

    Questions on the candidate's merge sortCodingRound not stated
  • Check whether two strings are anagrams (brute force, then better)

    Level: New grad, SWE.

    Write it in JavaCodingRound not stated
  • Walk through a project on your resume: what you built, why, and how

    Level: Intern, New grad, SWE.

    Draw an ER diagram; a real-life problem the project facedCodingRound not stated
  • Polymorphism: types, and a real-world example (vs abstraction)

    Level: Intern.

    Not reportedCodingRound not stated
  • Four pillars of OOP, then abstraction vs encapsulation

    Level: Intern.

    Types of inheritanceCodingRound not stated
  • MySQL vs MongoDB (SQL vs NoSQL): real-life uses; MongoDB or Firebase?

    Level: Intern, New grad.

    How do you connect to MongoDB?CodingRound not stated
  • Design a database for a canteen management system

    Level: New grad.

    Cross-questions and suggested changesCodingRound not stated
  • Puzzle: blind man and coins

    Level: Intern.

    Train-and-man aptitude question in the same roundCodingRound not stated
  • Resume and project deep dive

    Level: Walk through a project; draw its ER diagram; a real-life problem the project faced.

    9 of 11 recordsCodingRound not stated
Page 1 of 5

Keep preparing on Codinzhub

Ready for the next topic?

Keep track of what you’ve learned.