University of Wisconsin-Madison Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 6 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at University of Wisconsin-Madison.
University of Wisconsin-Madison
Software Engineer
Entry Average Positive experience Decline offer 1 round
Interview process
Recruiter call
Interview formats
Behavioral
The process to get an interview set up was good. The people involved were friendly, and the atmosphere was low key. I would consider working here in the near future because of the great work-life balance, nice people, and nice buildings.
Confirmed questions1 question
- Can you describe a time when you completed a challenging project?
University of Wisconsin-Madison
Student Developer
Intern Average Neutral experience Accept offer 2 rounds
Interview process
Phone screen Onsite
Interview formats
Behavioral Technical
had a phone interview then an onsite interview. They asked some basic questions about my resume, but not technical coding questions. Every question was based on my resume and my programming language experience.
Confirmed questions5 questions
- Could you discuss your project history?
- Tell me about your teamwork experiences.
- What are you most weak at?
University of Wisconsin-Madison
Software Engineer
Entry Easy Positive experience Accept offer 4 rounds
Interview process
Recruiter call Technical screen Take home Onsite
Interview formats
Behavioral Technical
I sent in my resume and cover letter. Then I had a phone call where they asked about my interest in the role and my personality. After that, I was given a work sample to show I could code. Finally, I went for an onsite interview where we talked more about my technical skills and if I'd fit the team culture. I actually met one of the interviewers at a local software meetup before the onsite.
Confirmed questions2 questions
- Could you explain the distinction between a class and an object?
- Tell me about a time you had a conflict with a coworker and how you handled it.
University of Wisconsin-Madison Software Engineer Interview Questions
Quoted word for word from University of Wisconsin-Madison interview reports.
“Could you explain the distinction between a class and an object?”
Read reports →“What are you most weak at?”
Read reports →“What programming languages have you worked with?”
Read reports →“How do you like to be managed?”
Read reports →“Tell me about a time you had a conflict with a coworker and how you handled it.”
Read report →“Can you describe a time when you completed a challenging project?”
Read report →“Can you talk about your resume?”
Read report →“Tell me about your teamwork experiences.”
Read report →“Can you tell me about your front-end experience?”
Read report →Formats, difficulty and experience
Across all 6 University of Wisconsin-Madison interview reports.