SDS logo

SDS Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 12 interview experiences · FREE TO READ

3.1 Rounds average
Average Typical difficulty
66.7% Positive experience

Which role are you interviewing for?

9 roles · 12 reports

Candidate interview experiences

First-hand accounts from people who interviewed at SDS.

Showing 4 of 12
SDS logo
SDS

User Experience Designer

Design · nearly a year ago

Mid Average Negative experience Decline offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite Offer
Interview formats
Behavioral Technical Presentation

The interview process for this User Experience Designer role is pretty standard. It involves a few stages to assess your skills and fit for the team. We want to see how you approach design challenges and collaborate with others.

Confirmed questions0 questions

No confirmed questions were included in this interview report.

SDS logo
SDS

Software Engineer

Engineering · more than a year ago

Mid Difficult Positive experience No offer 6 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite Panel Background check Offer
Interview formats
Behavioral Technical Coding System Design

So I interviewed for a Software Engineer job at SDS Inc. It was pretty intense but fair, they really dug into both my tech skills and if I'd fit in. Started with a recruiter call, where we talked about my background and why I wanted the job. Then I had a technical phone interview with a senior engineer, which included some coding on a shared screen, mostly testing my algorithms, data structures, and problem-solving abilities. After that, they had me come in for a full day of virtual onsite interviews. There were four parts to the onsite: a coding challenge with tough algorithm problems and time limits, a systems design part where I had to design a scalable system, a behavioral interview asking about past situations and teamwork, and then a final chat with the team lead about culture fit. It was tough but a good way to see if I was the right fit.

Confirmed questions6 questions
  • Could you tell me the difference between an array and a linked list, and how does garbage collection work in Java (or a language you know well)?
  • How would you go about optimizing a database query that's running slowly?
  • Can you explain what RESTful APIs are?
SDS logo
SDS

Business Analyst

Analytics

Senior Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Technical Behavioral

A recruiter called me about the job. After I said I was available, they explained the role and asked if I had any concerns. The first round was a phone call with a Senior Recruitment Manager who assessed my technical and functional skills. It was clear they knew what they were looking for and were willing to pay for the right person; it was a very honest interview with feedback provided at the end. I also had a short technical/IQ test. The final round was with the Global Head, lasting 15 minutes on Skype, and felt like a commitment check. They gave me time to think before answering questions. I liked how everything went.

Confirmed questions1 question
  • Can you mention something you didn't like about the interview process?
SDS logo
SDS

Software QA Test Engineer

Engineering

Entry Average Positive experience No offer 7 rounds
Interview process
Recruiter call Technical screen Take home Onsite Panel Background check Offer
Interview formats
Behavioral Technical Coding

I went to a walk-in interview last Saturday. There were two rounds of interviews, both about my previous project. The first round asked about my project, my daily activities, the purpose of sprint planning meetings, what testers do before a sprint starts, examples of high severity/low priority issues from my project, and the difference between test cases and test scenarios. The second round asked me to introduce myself and my project again, identify boundary values from given examples, understand and explain a given requirement, write test modules for my project, answer questions about testing paths and test cases for those modules, and some basic testing questions like smoke and sanity. There was also a machine test where I had to write test cases based on a requirement because they would ask questions from it later. Then, they gave me an application and asked me to take screenshots to show I understood its flow. The fifth round involved questions from the third and fourth rounds. Finally, there was a manager round and an HR round. The first two rounds were on the same day. They called a week later if I was selected.

Confirmed questions1 question
  • What is smoke and sanity testing?

SDS Interview Questions

Quoted word for word from SDS interview reports.

Describe the difference between an array and a linked list, and explain how garbage collection functions in Java or a similar language.

Read report

What are the main ideas behind Object-Oriented Programming (OOP)?

Read report

How would you go about optimizing a database query that's running slowly?

Read report

Could you tell me the difference between an array and a linked list, and how does garbage collection work in Java (or a language you know well)?

Read report

Formats, difficulty and experience

Across all 12 SDS interview reports.

Interview formats

Behavioral 34.5%
Technical 31%
Presentation 13.8%
Coding 13.8%
System Design 3.4%

Interview difficulty

Easy 16.7%
Average 75%
Difficult 8.3%

Candidate experience

Negative 16.7%
Positive 66.7%
Neutral 16.7%

Reports by job function

Engineering 5
Design 2
Analytics 2
Research 1
Operations 1
HR 1