Facebook Android engineer onsite

Sorted Fb questions by frequency?

Dm me. I had an onsite last week

Had on-sites for Android positions with offers from several top tech companies. I scheduled some on-sites for more than a month away but certain companies just put an informal date onto a calendar until 2 weeks prior. Look at the systems design white papers people have posted and examples of how apps have scaled for a starting base. Android developers are still expected to have a good idea about how the backend works (at least in my interviews). I'd recommend looking at high profile Android repos and getting a good sense of how people are designing apps and then thinking about apps ex. a newsfeed, photo album, notepad, etc. Think about writing code for unit testing, why Google is pushing MVVM, things like sync across multiple devices, the activity lifecycle, how you download and store data, when data should be push vs pull, device resources and constraints, app versioning/config changes, etc.

I did an Android-track loop at FB that had two design rounds and did well enough (offer in the end, plus apparently strong feedback on the design side of things). You probably shouldn't think of mobile at this level/scale as "front end;" the appropriate mentality should be closer to full stack. There are entire teams there working on Android libraries and systems that technically don't even have a UI. I won't give away the scenarios to preserve the integrity of the process (I'm an interviewer myself), but I will say this: there was virtually no discussion about UI directly (e.g. view classes and the like), and a lot of discussion around things like network (including offline) state and sync, caching and persistence, data modeling, security, and resource constraints and management. A few minutes spent on writing custom draw calls in one round, and we even talked about service API design and the client-service relationship. Hope that helps. Feel free to DM me if you have specific questions.