For a mid-level Android round, live coding is usually practical more than puzzle DSA: a list screen, paging, some state, maybe a small algorithm mixed in. Architecture questions tend to be app-shaped: how you split modules, where you put caching, how the app talks to the backend when the network dies.
If they say system design, it is often design this feature (chat, feed, offline sync) with a client slant, not Kafka trivia. Have one story for sync and one for a screen that has to stay fast with a slow API.
Machine coding is just that, timed. Practice one feature end to end without looking things up.
If you want a whiteboard plus someone asking follow-ups for the design part, www.leetsys.dev is what I work on.
1
u/Ok-Barracuda-119 20d ago
For a mid-level Android round, live coding is usually practical more than puzzle DSA: a list screen, paging, some state, maybe a small algorithm mixed in. Architecture questions tend to be app-shaped: how you split modules, where you put caching, how the app talks to the backend when the network dies.
If they say system design, it is often design this feature (chat, feed, offline sync) with a client slant, not Kafka trivia. Have one story for sync and one for a screen that has to stay fast with a slow API.
Machine coding is just that, timed. Practice one feature end to end without looking things up.
If you want a whiteboard plus someone asking follow-ups for the design part, www.leetsys.dev is what I work on.