Secureworks logo

Secureworks Software Engineer Interview Questions
& Process

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

Based on 10 interview experiences · FREE TO READ

3 Rounds average
Average Typical difficulty
44.4% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Secureworks.

Showing 3 of 10
Secureworks logo
Secureworks

Software Engineer

Engineering · a year ago

Senior Average Negative experience No offer 3 rounds
Interview process
Phone screen Take home Technical screen Background check
Interview formats
Technical Coding

It started with a phone screen, then a take-home assignment that took up about 4 hours of my Saturday. I did all the work, including a detailed README explaining my thoughts and design, unit and integration tests with Googletest, and even a sample Jenkins CI/CD pipeline. After putting in a lot of work, I didn't hear back for weeks. HR finally asked if I wanted to proceed with final interviews. I said no because the lack of communication and respect for my time was a bad sign. The 'final' stage had 3.5 hours of back-to-back 1:1 technical interviews, which felt like a lot given the take-home already showed my systems programming skills. Given the assignment's scope and Secureworks' focus, I couldn't help but wonder if the work was reused internally, but that's just me guessing. My advice to other engineers: be careful with long take-home assignments unless it's clearly a simple problem or you're sure the company is worth the effort.

Confirmed questions1 question
  • Could you write a Linux userspace process that tracks system status and converts the information to be sent over a socket?
Secureworks logo
Secureworks

Software Engineer

Engineering

Mid Average Negative experience No offer 6 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Technical Behavioral

So after a quick 30min phone screen, I had this big interview block that was like 4-5 hours long. It was split into 5 separate meetings, each about 45-60 minutes each. They dug into my past work, asked some casual questions like about hobbies, and also tested my deeper technical knowledge. They threw in two questions about problem-solving skills. Pretty clear they're looking for solid technical chops. On the downside, nobody even offered me a drink, not even water, during those long sessions. And the worst part is HR was supposed to get back to me in a few days, but I heard nothing. I've emailed and called them multiple times over two months and still no word from SecureWorks. It makes me wonder if they even have actual openings or if they're just building a candidate database for the future.

Confirmed questions2 questions
  • What is the commandline parameter of X to do Y?
  • What is the commandline parameter of X to do Y?
Secureworks logo
Secureworks

Software Engineer

Engineering

Entry Average Positive experience Accept offer 2 rounds
Interview process
Recruiter call Technical screen Offer
Interview formats
Technical Behavioral

The first part of the interview where they asked me about my past projects and stuff went really well. However, I struggled a bit with the technical interview. The interviewer was super nice and chill, making the whole experience really comfortable. They didn't focus too much on my technical abilities. I think I got the offer mainly because of my previous projects, my personality, and my problem-solving skills.

Confirmed questions4 questions
  • Can you discuss your past projects?
  • What are fundamental Java concepts?
  • Are you familiar with HTML?

Secureworks Software Engineer Interview Questions

Quoted word for word from Secureworks interview reports.

Could you write a Linux userspace process that tracks system status and converts the information to be sent over a socket?

Read reports

Formats, difficulty and experience

Across all 10 Secureworks interview reports.

Interview formats

Technical 34.8%
Behavioral 34.8%
Coding 26.1%
System Design 4.3%

Interview difficulty

Easy 20%
Average 70%
Difficult 10%

Candidate experience

Positive 44.4%
Neutral 22.2%
Negative 33.3%