Overview: One round, Android technical. Short experience, but worth sharing so others don't go in blind as I did. The Android Round,  Honest Feedback: The task involved a specific advanced Jetpack Compose component that most Android developers wouldn't encounter regularly. No prior heads-up about what the round would cover. No written problem statement, everything communicated verbally only. I was able to work through most of the task despite not having used that specific component before. The problem-solving approach was clear, execution was strong, but one niche API I hadn't encountered before created a gap. That gap alone seemed to define the outcome. Here's the reality,  give this same task to most experienced Android developers without any warning and the majority won't complete it fully. That is not a skills gap. That is a setup. What It Felt Like: A process built to find reasons to reject rather than reasons to hire. No written brief, no disclosure of tools in advance, tight time limit on niche APIs, it raises serious questions about whether the intent is genuine evaluation at all. Reading other Glassdoor reviews, this pattern seems consistent across multiple candidates. Draw your own conclusions. To Future Candidates: * They may tell you the task involves parsing an API and displaying data on screen, but that description does not tell the full story * The actual task goes significantly deeper into advanced Compose specifics * Ask upfront exactly what the round will cover * Do not assume standard Android questions * If you have other interviews lined up, prioritize those. Companies that genuinely want to hire make it obvious from how they run their process. There are better opportunities out there, and I ended up finding one To Robinhood: Transparency costs nothing. A fair interview shows what someone can do, not whether they've happened to use one specific niche API before.