League logo

League Android 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

2.8 Rounds average
Average Typical difficulty
16.7% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at League.

Showing 3 of 6
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

Mid Difficult Negative experience No offer 5 rounds
Interview process
Recruiter call Technical screen Take home Onsite Background check
Interview formats
Technical Coding System Design Behavioral

I went through 1 screening with HR, then 1 technical interview where they asked several questions. After that, I had 1 challenge exercise building an android app, followed by 1 challenge exercise on architecture design. Lastly, there was 1 cultural fit interview. I passed 99% of the process but was rejected due to a subjective interpretation of a behavioral question during the cultural fit. It's crazy. I suspect they just found someone cheaper but they won't admit it.

Confirmed questions1 question
  • How would you handle a deadline that seems impossible to meet?
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 Android Engineer Interview Questions

Quoted word for word from League interview reports.

How would you handle a deadline that seems impossible to meet?

Read reports

Were there any basic Android questions during the screening call?

Read report

Could you provide more details on your system design answers?

Read report

Are you able to work across Android, iOS, web, and backend?

Read report

Formats, difficulty and experience

Across all 6 League interview reports.

Interview formats

Technical 40%
Behavioral 20%
System Design 13.3%
Coding 13.3%
Presentation 6.7%

Interview difficulty

Easy 33.3%
Average 50%
Difficult 16.7%

Candidate experience

Negative 66.7%
Neutral 16.7%
Positive 16.7%