League logo

League Interview Questions
& Process

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

Based on 148 interview experiences · FREE TO READ

2.9 Rounds average
Average Typical difficulty
37.2% Positive experience

Which role are you interviewing for?

30 roles · 148 reports

Candidate interview experiences

First-hand accounts from people who interviewed at League.

Showing 4 of 148
League logo
League

Senior Android Developer

Engineering · half a year ago

Senior Easy Negative experience No offer 4 rounds
Interview process
Take home Technical screen Presentation Panel Group Background check Offer
Interview formats
Technical System Design Presentation Behavioral Other

So I'm giving feedback because League requested it. A lot of people mentioned the take-home assignment takes way longer than a couple of hours, and I agree, getting the project to sync and doing thorough testing can really eat up time. The interviewers themselves were great, no issues there. But the interview loop itself had some major problems. First off, the whole process dragged on way longer than expected. I was told it would be about 2.5 weeks from the take-home to an offer, but mine took a full month, which was pretty frustrating. Second, the amount of work outside the actual interviews was way more than usual. For this role, I did the take-home, then had to submit a system design diagram, and after the technical panels, I had to complete a 115-question online personality assessment. All that extra work added up to almost 6 hours, and with 4 one-hour interviews, it’s easily over 10 hours of commitment, not counting talking to the recruiter. I've interviewed at tons of places, and 5 hours total has been the max before. The biggest issue, though, was the lack of transparency. Right before my final interview with the execs, I noticed the job posting was changed to a mid-level role, but no one mentioned it, and they kept referring to it as a Sr. role. In that final interview, one person seemed disengaged, and their questions felt shallow. They asked about my cross-platform skills, and I mentioned I could do both iOS and Android, needing a bit of a ramp-up on iOS but nothing major since I'd done it before. After that, it was radio silence for a few days until I followed up. They said they'd decide by the end of the week, but then missed that deadline. The next week, they blamed a hackathon for shifting timelines. Two weeks later, I finally got an update. It wasn't a standard rejection; the reason they gave was I was too specialized for a Sr. Android role, which is what they were hiring for! Then they said they changed priorities to someone who could do Android, iOS, web, and backend. It's baffling they'd ask me to spend extra time on a personality test and do the final exec interview if they weren't really considering me, especially after changing the scope. It felt really disrespectful of my time. There seem to be serious internal misalignments, and this pattern of bad interview experiences confirms it. I used to think highly of League, but not anymore. Someone I know internally confirmed that no one actually does all the platforms they asked for; everyone is dedicated to their own platform.

Confirmed questions5 questions
  • Can you describe your approach during the assignment review?
  • Could you provide more details on your system design answers?
  • Tell me about your experience with cross-functional platforms.
League logo
League

Android Developer

Engineering · nearly a year ago

Entry Average Positive experience No offer 2 rounds
Interview process
Recruiter call Take home
Interview formats
Technical

I had a screening call that was followed by a take-home assessment that took about 3-4 hours. The judging criteria weren't clear, though it seemed to follow industry standards. I ended up getting a rejection email without any explanation, which is somewhat understandable, but spending 4-5 hours of personal time shouldn't be the norm.

Confirmed questions3 questions
  • Were there any basic Android questions during the screening call?
  • Did the screening call cover thread management?
  • Were testing tools discussed in the screening call?
League logo
League

Software Engineer

Engineering · nearly a year ago

Senior Average Negative experience No offer 2 rounds
Interview process
Technical screen Recruiter call
Interview formats
Technical Behavioral

I had a technical interview with two engineers, but they didn't seem very knowledgeable about application security and tools like SAST/SCA. It wasn't a great experience because I felt I wasn't selected despite answering all their questions correctly, due to their lack of knowledge. When the Director of Talent told me the result, I asked for specific feedback from the last interview or the reason I wasn't selected. I also offered to provide feedback on the interview, but I didn't hear back.

Confirmed questions2 questions
  • Can you tell me about a past project you worked on?
  • What key aspects do you consider when reviewing code?
League logo
League

Software Development Manager

Engineering · more than a year ago

Manager Average Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Presentation Background check Offer
Interview formats
Behavioral Technical System Design Presentation

The recruiter reached out on LinkedIn. After that, there were several rounds. First, an introductory call with the Dev Manager to go over my experience and the role. Then, a leadership interview, a 1-hour call with the Product team and another Dev Manager, focusing on leadership topics like team performance, hiring, and roadmaps. Next, a system design round where I had to present a design for a problem sent a week in advance, which involved a lot of preparation. This was a good session with 3 interviewers. Unfortunately, things went downhill after this. Despite following up immediately because I thought it went well, they were unresponsive. The recruiter did respond, and confirmed the negative reviews about ghosting are true. Reasons given were vacation, salary pushback, and finally that they found someone with more experience, even though multiple roles were open. It seems they might be exploiting the current market. Overall, it was a learning experience, but their communication is poor.

Confirmed questions6 questions
  • What is your approach to managing an underperforming team member?
  • Can you describe how you would manage a low performing team member?
  • Tell me about your experience and discuss the role.

League Interview Questions

Quoted word for word from League interview reports.

Can you tell me if a given number is odd or even in Python?

Read reports

RabbitMQ should be pub-sub. Why do you say it's a message queue?

Read reports

What distinguishes Observable, Single, and Maybe in terms of their functionality?

Read reports

Have you seen a concert at the venue you are going to visit?

Read reports

If a remote image is updated before the cache period expires, what would be your approach?

Read report

Regarding caching, what duration would you set, and how would you manage it if a remote image updates before that time is up?

Read report

For an application designed to upload images along with their associated metadata, what architectural approach would you suggest?

Read report

Can you explain how to incorporate a local store within the architectural diagram?

Read report

Could you build a simple web app that fetches data from a 3rd party health info API, formats it, and displays the data?

Read report

Formats, difficulty and experience

Across all 148 League interview reports.

Interview formats

Behavioral 40.6%
Technical 28.4%
Coding 10.9%
Presentation 9.1%
System Design 7.2%

Interview difficulty

Easy 22.3%
Average 67.6%
Difficult 10.1%

Candidate experience

Negative 53.4%
Neutral 9.5%
Positive 37.2%

Reports by job function

Engineering 61
Operations 20
Sales 12
Other 10
Product 10
Analytics 8