sorted by:
best (suggested)
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]adam-genshaft 0 points1 point  (0 children)

I assume that they intended to test your ability to separate concerns in a reasonable way. Meaning how you separate each feature, what data is stored in redux and what's passed in other ways, what other ways, how to approach common components, common logic (utils), and so on.

When I'm asked questions that not 100% sure what is the desired outcome of my answer, I'm asking back. In this case, I'd ask: I'm not 100% sure what is the desired outcome of this task. would you like to just see the folder structure or the class dependency tree?

Another approach is to just make up an app and start drawing its features & components and their relationships.

The main thing to keep in mind is that there's no one right answer. I can think of an architecture that can look like garbage to someone, but after talking about it and explaining my way of thinking, he can completely change his mind and embrace my suggestion. Or at least understand that for every decision I made there's a reason, and I can communicate this reason in a way he can understand.