SAS logo

SAS Interview Questions
& Process

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

Based on 621 interview experiences · FREE TO READ

2.6 Rounds average
Average Typical difficulty
69.3% Positive experience

Which role are you interviewing for?

30 roles · 621 reports

Candidate interview experiences

First-hand accounts from people who interviewed at SAS.

Showing 4 of 621
SAS logo
SAS

Application Architect

Engineering · nearly a year ago

Senior Average Negative experience No offer 2 rounds
Interview process
Recruiter call Phone screen
Interview formats
Behavioral Technical

I applied for two roles online. Then I set up a screening call with a recruiter. We realized my skills were broader than the roles offered. The recruiter said they'd connect me with a manager for a role that fit my background. Everything was going well. Then I shared my current salary. I never got that call with the manager. I think the recruiter is a nice guy, but I don't think they were upfront about what they'd pay for my experience level. I know people who worked at SAS and many have left. You hear the same stuff about their cafeteria piano and low pay. My sense is they're worried about AI and other things that can do their job. I think they're probably a decent company, but my experience was bad.

Confirmed questions3 questions
  • Can you describe your background and skills?
  • What is your current salary?
  • Can you share your salary expectations?
SAS logo
SAS

Network Automation Engineer

Engineering · nearly a year ago

Mid Average Positive experience No offer 2 rounds
Interview process
Recruiter call Phone screen Technical screen Panel
Interview formats
Technical Behavioral

So, first, I got a call from HR and they did a quick phone interview right then, it was about 20 mins. They asked some quick questions on Python, Networking, and Docker to see what I knew. Then, I had two actual interview rounds, both with panels. The first one had two people, and it was like a rapid-fire session with questions on Python, FastAPI, Networking, Linux, and Docker. The second round was with the senior folks, like the people from the onsite team, there were four of them. This one was more of a discussion, with scenario-based questions mixed in. I really liked the vibe, everyone was super positive and encouraging. Unfortunately, I didn't get the job after the second round because I didn't have a networking background, and they ended up hiring someone who did.

Confirmed questions4 questions
  • Questions on Python specifics like decorators, mutable/immutable types, and list comprehensions
  • Questions about Docker, covering topics such as volumes and networking
  • Networking questions including DNS resolution, VLANs, and the differences between IPv4 and IPv6
SAS logo
SAS

Software Engineer in Test

Engineering · a year ago

Entry Average Negative experience No offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Panel
Interview formats
Behavioral Technical

Applied for Software Engineer In Test. The recruiters were really bad, very robotic and seemed like they didn't even read my resume. They asked a lot of questions about why I wanted to work at SAS and how much I knew about the company, but didn't give me much info about the actual job. They got annoyed when I asked about the salary range instead of giving my desired salary. Benefits were just described as 'good'. After that, I had a call with the hiring manager and a lead, which was better but still had that 'company hype' feel, and the job description seemed a bit misleading. The recruiter said a panel round would be scheduled soon, but it took a week to even get a request for availability. I gave them wide open slots and mentioned a pending offer to maybe speed things up. Then they told me my slots didn't work and they'd schedule me for a time that did, asking me to be flexible. I withdrew my application because of this poor scheduling and communication. To top it off, they didn't remove me from their system and I still got an email about them finishing interviews and making a decision.

Confirmed questions5 questions
  • What motivated you to apply for this role at SAS?
  • Specifically, what draws you to SAS as an employer?
  • What aspect of SAS do you find most compelling?
SAS logo
SAS

Intern

Engineering · a year ago

Intern Average Positive experience No offer 4 rounds
Interview process
Recruiter call Technical screen Take home Onsite
Interview formats
Technical Coding Other

The R&D interview process at SAS is usually in a few parts to see if you're a good fit technically and as a person. First, there's an aptitude test covering logic, math, and English skills. Then, you'll face technical multiple-choice questions on Data Structures & Algorithms, databases, operating systems, object-oriented programming, and basic C/C++/Java, plus some SQL. After that, expect 1 or 2 coding problems, usually medium difficulty, focusing on common areas like arrays, strings, trees, graphs, and recursion. This whole thing is to figure out if you're right for the role.

Confirmed questions3 questions
  • Two questions on Data Structures and Algorithms
  • One question on SQL query
  • A question on Computer Fundamentals

SAS Interview Questions

Quoted word for word from SAS interview reports.

Given two points on a line and a list of an object's vertices, how would you check if the line intersects the object?

Read reports

Given a tab and two jars, one 5-oz and one 3-oz, how can you accurately measure exactly 4-oz of liquid using only these items and without visual estimation?

Read reports

What are some techniques you can utilize to avoid overfitting in a deep neural network?

Read reports

How can you add context to input data to ensure that the neural network learns that context?

Read reports

Can you explain how to implement JWT in a web application, covering SSO and SAML as well?

Read report

Regarding Accessibility, Location, and Language selection, how would you set up and verify these features?

Read report

What recent papers or research in the field are you most excited about?

Read report

Regarding the expected forecast in Latin America, what would be your strategy to achieve it?

Read report

Can you compare two programming languages, outlining their pros and cons using technical terms that a mid-level engineer could grasp?

Read report

Formats, difficulty and experience

Across all 621 SAS interview reports.

Interview formats

Behavioral 43.5%
Technical 30.9%
Presentation 10.4%
Coding 6.2%
Other 4.1%

Interview difficulty

Easy 22.2%
Average 62%
Difficult 15.8%

Candidate experience

Positive 69.3%
Neutral 16.4%
Negative 14.3%

Reports by job function

Engineering 246
Sales 100
Other 69
Analytics 50
Consulting 49
Operations 34