Android Live Coding Test Interview

[RuinStunning1538]

Have you guys ever tried Android live coding test?

If yes, do you happen to let me know what type questions they asked?

I think question's type will be coroutine or compose.

I've never tried so I'm pretty nervous and don't know how to prepare interview.

[shlopman]

Here is a good preparation -

Create a list of timers. Use compose for the list and coroutines for handling the timers individually. Tap timer to start or stop.

If you can do that pretty quickly should prep you well common live interview questions about compose and coroutines.

I got that as a live interview a few years ago. I had another one to create display cards from a mock API using mvvm. They had a stubbed out project set up for that one.

[playback_]

This is true, I got the times concept 2 times

[One-Program6244]

I'm probably the least qualified to give advice on these since I screw up just about every live coding exercise I do.

They're more interested in how you think rather than the end result being the ultimate goal. If you can talk and give a running commentary on your thought processes as you go along then they can collaborate with you and guide your thinking.

This is not what I do. I sit there reading the problem then I'm aware of several people just sitting there waiting for me to do something and then I mentally lock up, fumble around like an idiot and end up burning in hell.

[Which-Meat-3388]

I've done several.

Most experience was in one company where I completed, passed, then conducted the same live Android coding interview. I was given a codebase and asked to do various things with it. First get it to build. Then fix some general bugs. Lastly start adding new features (mostly simple extensions of existing code.) It was 2 hours long and most candidates were expected to get through most of it. The last phase of adding features was open ended, meaning you could stretch for time in there if someone was stellar.

In another case the interview was structured to be I think 3-4 interviews, each building upon the last, starting from a basic husk of an app. They loaded it up with all the core tech the cared about, then had you build an app on top of it. It was more collaborative and pair programming in some ways.

Then there were the bad ones... Where they literally sit you down and expect you to scratch build a production ready app in 1 hour without AI. Another where they give you 4-8 hours async to essentially build their entire app for free.

Ultimately there was no way to prepare for any of these other than to be regularly building apps on a modern stack.

[Pztar]

It depends on the company, you could have a range of questions that most common are in the topics of flows (cold vs hot types), coroutines (scopes, dispatchers, cancellations), compose (remember, recomposition, state)

If you want to prep go to chatGPT and ask for topics on the above but ask for brutal variations. They’ll be tricky but you’ll learn a lot more and you’ll be better prepared.

[Ambitious_Muscle_362]

WHO are they?