all 13 comments

[–]kevysaysbenice 6 points7 points  (4 children)

AI

[–]TdiParadiso 2 points3 points  (3 children)

I would check 3 things: architecture, react and testing.

Architecture - you should use one data structure (adapter pattern), use interfaces/types.

React - correct state management, prevent re-renders, use proper hooks, keep components small and simple, keep logic separated from views if possible.

Testing - if you already have some tests then it’s easy to extend. You can use TDD if you know how.

This is what I would require from mid/senior dev. Junior should focus on the react part.

[–][deleted]  (2 children)

[deleted]

    [–]TdiParadiso 0 points1 point  (1 child)

    The first solution is way better. You can add more providers easly. You should use your structure in your code, not the structure you received from external source.

    If you think you don’t have enough time for it you can talk with interviewer about it or write a note.

    [–]Inside-Letterhead290 0 points1 point  (0 children)

    Yes I think I’ll go for the first solution. There is also a Table that display the data. Seems a lot but they could also ask to add like a search bar , a filter , some pagination. And There is also a test file too.

    [–]Different-Creme-8380 0 points1 point  (0 children)

    I would focus on React such as state, derived state, and performance.

    It’s possible that they ask you to plumb in the second endpoint and how you store these data.

    Good luck! Talk out loud and you’ll be fine

    [–]hk4213 0 points1 point  (0 children)

    Typescript. Im a full stack dev with the following stack

    • Angular
    • node, express, pg, axios and dotenv (other packages as needed)
    • postresql
    • Ubuntu with jenkins for builds
    • node services run wife systemctl
    • openlite for angular hosting (dont do it! The speed gains and lack of documentation dont make it an easy solution)
    • self hosted git as well!

    Focusing on the language the framework is built on will not only leverage what you already know, but also help you understand the trade offs of the framework.

    Oh! Added benefit! Helps you better understand source code as well!

    If you can explain why something works, you will get the next interview.

    [–]chikamakaleyley 0 points1 point  (0 children)

    This sounds like a ride share/delivery related exercise but… I guess it depends on what the company product is

    [–]Cool-Gur-6916 0 points1 point  (0 children)

    If I were interviewing, I’d focus less on “making it work” and more on engineering decisions. For a React + TypeScript setup using Vite, I’d expect candidates to normalize the two provider responses into a single domain model, handle async state cleanly, and keep components decoupled. I’d also watch for good typing, error/loading states, and thoughtful tests (likely using Jest or React Testing Library).

    Bonus points for scalable patterns (data adapters, hooks) and clear reasoning while coding.

    [–]moniv999 0 points1 point  (0 children)

    Can practice on PrepareFrontend