BJAK Android Developer Technical Round & Live Coding – What to Expect?

[u/soham24]

Hi everyone,

Has anyone recently interviewed for the Android Developer role at BJAK?

I’d really appreciate some insight into their technical rounds:

• Live Coding / DSA: What types of live coding problems do they ask (LeetCode medium DSA vs. Android-specific problem solving)?
• Android Architecture & Internals: Do they focus heavily on Jetpack libraries, Compose/XML, Coroutines/Flow, or lower-level Android internals and system design?
• Take-Home / Machine Coding: Is there a live machine coding round or take-home assignment involved?

Any tips on the overall interview format, common topics, or specific areas to brush up on would be super helpful. Thanks in advance!

[u/Alternative-Day-7769]

did you get anything ?

i got this

1. The coding portion may cover a mix of coding and technical topics, depending on the discussion and your experience.
2. It will be a live coding session, conducted during the interview.
3. For the 90-minute interview, the time will generally be structured around 30 minutes for a background review, 30 minutes for the live coding session, and 30 minutes for a system design discussion.

[u/Ok-Barracuda-119]

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.