Washington State University logo

Washington State University Software Engineer Interview Questions
& Process

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

Based on 5 interview experiences · FREE TO READ

2.4 Rounds average
Easy Typical difficulty
80% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Washington State University.

Showing 3 of 5
Washington State University logo
Washington State University

Applications Developer

Engineering · more than a year ago

Mid Easy Positive experience Accept offer 5 rounds
Interview process
Recruiter call Phone screen Onsite Background check Offer
Interview formats
Behavioral Technical Coding System Design

I applied for this Applications Developer job online through the WSU careers website. After about a month, I heard back via email and had a phone interview. Following that, I was invited for an on-site interview. The on-site part started with behavioral questions, and then I had to design a database. They also wanted me to bring along code samples related to databases and client-server interactions for discussion. After the on-site, the next step was a background check, and then I received the offer.

Confirmed questions4 questions
  • Can you tell me about your past work that is relevant to this role?
  • Your task is to design a database that's like the one we use here.
  • We'd like to ask you some behavioral questions to start.
Washington State University logo
Washington State University

Software Developer

Engineering · more than a year ago

Entry Easy Neutral experience Accept offer 2 rounds
Interview process
Recruiter call Technical screen Onsite Offer
Interview formats
Technical Presentation

It was a multi-interviewer process. Initially, a friend of the interviewer did a basic check to see if I had a grasp of fundamental programming concepts. Next, I had to propose solutions for a core job-related task. Then, I spoke with the hiring team, who understood what they needed but lacked a technical background. They asked very open-ended questions, including requesting that I explain a basic programming concept to them. After that, hiring was finalized quickly.

Confirmed questions2 questions
  • The only challenging question was about string matching with overlaps. The answer I gave wasn't direct but aimed to show I could understand a potential solution.
  • How do you match up strings that overlap?
Washington State University logo
Washington State University

Software Engineer

Engineering · more than a year ago

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

The interview experience was relaxed and not stressful, but it did have very technical questions. My new manager, a future coworker, and other tech team members were involved. They were all ready with good questions about my software development knowledge and my thoughts on working in the field.

Confirmed questions2 questions
  • I was given a somewhat mathematical software problem to solve. I don't recall the exact details, but it involved a lot of interpretation regarding the best way to find a solution that both yielded accurate results and met the (somewhat vague) goals.
  • Although it was challenging, this problem was a great example of the type of issues encountered in the actual job, and it led to a good amount of discussion between me and the interviewers.

Washington State University Software Engineer Interview Questions

Quoted word for word from Washington State University interview reports.

What's your approach to finding the most frequent value within an array of integers?

Read reports

Your task is to design a database that's like the one we use here.

Read reports

Please bring a code sample that we can review and talk about.

Read reports

The only challenging question was about string matching with overlaps. The answer I gave wasn't direct but aimed to show I could understand a potential solution.

Read report

I was given a somewhat mathematical software problem to solve. I don't recall the exact details, but it involved a lot of interpretation regarding the best way to find a solution that both yielded accurate results and met the (somewhat vague) goals.

Read report

Although it was challenging, this problem was a great example of the type of issues encountered in the actual job, and it led to a good amount of discussion between me and the interviewers.

Read report

We'd like to ask you some behavioral questions to start.

Read report

Formats, difficulty and experience

Across all 5 Washington State University interview reports.

Interview formats

Technical 41.7%
Coding 25%
Behavioral 16.7%
Presentation 8.3%
System Design 8.3%

Interview difficulty

Easy 80%
Average 0%
Difficult 20%

Candidate experience

Positive 80%
Neutral 20%