Full Sail University logo

Full Sail University Interview Questions
& Process

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

Based on 69 interview experiences · FREE TO READ

2 Rounds average
Average Typical difficulty
75% Positive experience

Which role are you interviewing for?

21 roles · 69 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Full Sail University.

Showing 4 of 69
Full Sail University logo
Full Sail University

Advocate

Other · nearly a year ago

Entry Easy Positive experience Accept offer 1 round
Interview process
Recruiter call Background check Offer
Interview formats
Behavioral

It took a few weeks to hear back after applying, but the interview part was actually pretty fast and easy. I interviewed in late December, and I was already starting my job and in orientation by the middle of January. The questions they asked were really focused on solutions, and I used the STAR method to answer them.

Confirmed questions2 questions
  • What are some standard behavioral questions you can ask?
  • Can you tell me about your previous experience?
Full Sail University logo
Full Sail University

Software Team Lead

Engineering · more than a year ago

Lead Average Negative experience No offer 4 rounds
Interview process
Recruiter call Technical screen Technical screen Onsite
Interview formats
Behavioral Technical Coding

This was a super unprofessional interview process. Full Sail is behind the times with quality and automation. They'll doubt your honesty and waste your time. My whole experience, with two interviews and two tech tests, took over five weeks. I really don't recommend this. They were hiring a team lead and I applied through a good recruiting firm. They'd been trying to fill it for a while, but no one passed the tech assessment. The process had two tech assessments and two interviews. First, I had a meet-and-greet with a director. He mentioned wanting to improve his team's deliverable quality. I have lots of experience there and was upfront about what I could offer. At the end, I asked if I had what he was looking for, and he said yes. The next part was an offline tech assessment. The hiring team really stressed avoiding cheating, which felt like they were questioning my integrity right off the bat. It involved solving a problem a senior Java dev would likely know. I had to use an online IDE I wasn't familiar with, which took some getting used to. The current team lead wanted a set of unit tests to pass for it to be considered a success. I found the 20 or so unit tests to be amateur and non-standard; I could've tested all the business requirements with about five or six JUnit tests. I even found a bug in one of them. I solved the problem without much issue. Then, they told me I'd do an online coding assessment where the lead would 'change' the test conditions to prevent cheating. Again, questioning my integrity, which was annoying, but I agreed to the second tech interview. Changing the assessment requirements meant rewriting 95% of the code to use a different, harder strategy. I didn't finish within 40 minutes, so I tried to explain the design patterns I'd use to solve it. The lead didn't get my explanation. I later learned he doesn't know any GoF design patterns, can't describe metrics for code maintainability or reliability, doesn't document code, only has unit test automation, mocks code linters, and has no idea how much technical debt he has or how to fix it. I was stunned by how backward their shop is. He wouldn't pass my tech interview, but I still saw the role as a chance. I did finish the changed assessment on my own that night. My approach worked as I explained, but it might not have been the best way. The last step was another interview with the director, the lead, and a senior team member. They asked tough leadership questions, and I asked mine. I only realized afterwards how vague they were about their overall code quality and how they planned to improve it. It took them six days to reject me. The reason? 'Too much QA experience.' I wasn't shocked. I don't even care about the rejection. I never felt totally comfortable with the lead I would have replaced. I think he's worried about how bad he'll look to upper management if his team's code is analyzed with industry-standard metrics. He shouldn't be, as 90% of companies have decent software measurement processes, and everyone should get a pass the first time. What bothers me is the arrogance of that whole team. Their lazy approach was so unprofessional. I paused my job search when the final interview was set up until I got the rejection because I didn't want to mess anyone around, expecting feedback in a day or two at the latest. Stopping my search during those six days cost me actual money. Interestingly, I got an offer from another company just two weeks later. Their process was a total contrast to Full Sail's. It included a 60-minute tech interview, harder than both Full Sail's assessments, followed by a 30-minute behavioral interview. The whole thing, from applying to offer, was done in eight days.

Confirmed questions2 questions
  • Could you elaborate on your leadership approach?
  • Tell us about your leadership style.
Full Sail University logo
Full Sail University

Web Developer

Engineering · more than a year ago

Mid Average Negative experience No offer 3 rounds
Interview process
Recruiter call Take home Onsite Background check
Interview formats
Technical Coding Behavioral

This interview process took two months, and then they ghosted me. I had an initial interview, completed a test project, and then had another interview where I was told I was among the final five candidates. After my last interview, they never got in touch, and the HR representative ignored my follow-up emails. It was extremely disrespectful.

Confirmed questions1 question
  • I don't recall the questions because the process lasted two months.
Full Sail University logo
Full Sail University

Technical Support

Operations · more than a year ago

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

I applied online and they called me back about a week later. They gave a quick overview of the job and asked a little about me. Then they set up a zoom interview for a week later, and I learned more about the job and they learned more about me. A couple days later, we had a mock call/chat over zoom. I also had to complete a Google Form with my typing speed and review sample phone calls. About two weeks after that, they emailed to say I didn't get the job.

Confirmed questions2 questions
  • Could you describe your experience in customer support?
  • Tell me about your technical experience.

Full Sail University Interview Questions

Quoted word for word from Full Sail University interview reports.

Would you rather have one horse sized duck or ten duck sized horses?

Read reports

If you were in a battle, would you rather fight 10 ducks the size of horses or 10 horses the size of ducks?

Read reports

If a student approached you with concerns about an instructor cancelling class, what would be your course of action?

Read reports

How would you manage outstanding balances when there's no documentation?

Read report

What was your experience like having an admissions guide for college?

Read report

Formats, difficulty and experience

Across all 69 Full Sail University interview reports.

Interview formats

Behavioral 59.5%
Technical 15.5%
Presentation 12.1%
Other 6.9%
Group 4.3%

Interview difficulty

Easy 39.1%
Average 58%
Difficult 2.9%

Candidate experience

Positive 75%
Negative 16.2%
Neutral 8.8%

Reports by job function

Operations 21
Other 20
Sales 11
Marketing 5
Engineering 4
Finance 4