Ho sostenuto un colloquio presso Upside (New York, NY)
Colloquio
Upside’s interview process typically covers your mobile engineering experience, ownership of features from design to launch, and how you think about architecture, scalability, and performance in a consumer app. They assess Kotlin coding skills through a practical live exercise, explore system and mobile design concepts like modularization and state management, and evaluate collaboration, mentorship, and problem-solving through behavioral questions to ensure strong product thinking and team impact.
Ho presentato la mia candidatura online. La procedura ha richiesto 4 settimane. Ho sostenuto un colloquio presso Upside nel mese di ago 2025
Colloquio
- People I interacted with were great and cordial.
- Applied from LinkedIn, initial phone call with the HR person, then hiring manager and two devs for coding interview.
- They were very accommodating when I had to reschedule due to an emergency.
Domande di colloquio [1]
Domanda 1
(Paraphrasing, don't remember the exact words)
- Asked my about my experience.
- How I handle and communicate scope changes in project
Ho presentato la mia candidatura tramite un selezionatore. Ho sostenuto un colloquio presso Upside
Colloquio
A recruiter sent me a dm via linkedin and I scheduled a call. He went over the basic stuff like what upside is and asked about my experience. Then he outlines their interview process by saying first it's a hiring manager chat followed by live coding with an engineer on the team. I ask whether this is leetcode or android, and he replies it is android coding.
In the interview invitation I am sent a link to an online platform for their live coding interview. So I email the recruiter again to confirm whether this coding is data structures and algorithms based or android, and he confirmed it was android specific.
My call with the manager was pleasant and we talked about my experience and the way I approached different issues at work. But in my coding round I was asked to solve a data structures and algorithms question. I spent the days before the interview studying stuff like compose and other android topics. I tried to proceed but I was rusty and failed. I prepared for meta months ago, and actually saw a similar problem during that period so I'm pretty sure I'd be able to solve it but my preparation was for what the recruiter told me, an android specific coding interview.
After I sent an email to my recruiter explaining the situation and asked for a re-interview because of the miscommunication but was ignored. It's frustrating in a tough market to be told misinformation that causes you to miss an opportunity. The company is using compose and kotlin multiplatform so I thought android live coding was going to evaluate you about newer android specific technologies but it is a typical data structures and algorithms style interview.
Domande di colloquio [1]
Domanda 1
MVVM vs MVI, what is the difference between the two?