Please help me prepare a game plan for my onsite.
2.5 years of experience working on Android development.
Recruiter is calling me today to schedule my onsite, I'm pretty nervous about it though. Is it ok to schedule it at least 1 month from now?
What's the best way to prep for system design for frontend engineers? Everything I've looked up basically points to system design in general, but nothing specific for mobile development.
Been leetcoding all of Facebook tagged questions, which is over 500 right now.. any suggestions to streamline the process or any tips in general that can help me get max results.
Thank you!
Want to see the real deal?
More inside scoop? View in App
More inside scoop? View in App
blind
SUPPORT
FOLLOW US
DOWNLOAD THE APP:
FOLLOWING
Industries
Job Groups
- Software Engineering
- Product Management
- Information Technology
- Data Science & Analytics
- Management Consulting
- Hardware Engineering
- Design
- Sales
- Security
- Investment Banking & Sell Side
- Marketing
- Private Equity & Buy Side
- Corporate Finance
- Supply Chain
- Business Development
- Human Resources
- Operations
- Legal
- Admin
- Customer Service
- Communications
Return to Office
Work From Home
COVID-19
Layoffs
Investments & Money
Work Visa
Housing
Referrals
Job Openings
Startups
Office Life
Mental Health
HR Issues
Blockchain & Crypto
Fitness & Nutrition
Travel
Health Care & Insurance
Tax
Hobbies & Entertainment
Working Parents
Food & Dining
IPO
Side Jobs
Show more
SUPPORT
FOLLOW US
DOWNLOAD THE APP:
comments
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.
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.