SUSE logo

SUSE Software Engineer Interview Questions
& Process

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

Based on 15 interview experiences · FREE TO READ

2.1 Rounds average
Average Typical difficulty
46.7% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at SUSE.

Showing 3 of 15
SUSE logo
SUSE

Senior Software Engineer

Engineering · nearly a year ago

Senior Average Negative experience No offer 1 round
Interview process
Recruiter call
Interview formats
Behavioral

I had an initial phone call with a recruiter and it went well. They said I would hear back about the next steps. But then, there was complete silence. I sent follow-up emails asking for updates and got no response. Two months later, they replied briefly saying they would let me know soon. Another month passed and I still haven’t heard anything.

Confirmed questions1 question
  • Can you discuss your background and what motivates you?
SUSE logo
SUSE

Software Engineer

Engineering · a year ago

Staff Average Neutral experience No offer 3 rounds
Interview process
Recruiter call Take home Background check
Interview formats
Behavioral Technical

First, I talked to HR about why I want to work at SUSE, if I know the company, and salary expectations. Then, the Hiring Manager and I discussed the product and my experience. He seemed really interested, which gave me hope. They sent me a home assignment, and after I submitted it, I got a rejection saying I wasn't senior enough. I asked for feedback on the assignment, but never heard back.

Confirmed questions1 question
  • Can you tell me why you are interested in SUSE and what you know about the company?
SUSE logo
SUSE

Software Developer

Engineering · a year ago

Mid Difficult Positive experience Accept offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Technical Coding

It began with a quick chat with HR, and then the main event was a two-hour technical deep dive. The vibe was pretty chill, even though the questions were tough. My interviewer was really nice, making the whole thing feel more like a collaborative think-tank than a formal interview. It was less about rapid-fire Q&A and more about building on ideas. Like, we'd discuss a problem, then explore potential pitfalls and how to navigate them. The interviewer was super helpful, offering guidance when I needed it.

Confirmed questions4 questions
  • Can you explain how you would implement the livepatching process?
  • What's your strategy for approaching the given problem?
  • What potential challenges could arise during this process?

SUSE Software Engineer Interview Questions

Quoted word for word from SUSE interview reports.

Using a shell script, how would you modify all the .c file extensions in a specific folder to .h?

Read reports

Can you identify potential issues associated with kernel live patching support?

Read reports

Can you explain how you would implement the livepatching process?

Read report

What potential challenges could arise during this process?

Read report

What's your strategy for approaching the given problem?

Read report

Can you tell me why you are interested in SUSE and what you know about the company?

Read report

Could you describe your experience with eBPF, specifically any projects where you've used it?

Read report

Formats, difficulty and experience

Across all 15 SUSE interview reports.

Interview formats

Technical 41.4%
Behavioral 37.9%
Coding 20.7%

Interview difficulty

Easy 0%
Average 86.7%
Difficult 13.3%

Candidate experience

Negative 33.3%
Neutral 20%
Positive 46.7%