0% found this document useful (0 votes)
13 views2 pages

Full Stack Developer Test

Uploaded by

adimsd0701
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
13 views2 pages

Full Stack Developer Test

Uploaded by

adimsd0701
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Thank you again for your interest in the Full-Stack Developer internship at Hooman

Group.​

To gauge real-world skill, we ask shortlisted candidates to complete the short
assignment below.

Challenge – “Pet Activity Tracker” Micro-App


Create a responsive mini-application that lets a pet owner:
1.​ Log an activity
●​ Inputs: pet name (text), activity type (walk, meal, medication –
dropdown), duration or quantity, date/time (default = now).
2.​ See today’s summary
●​ Show total walk time, meals, and meds given. Display both numerically
and with a small data-vis graphic (e.g., progress ring or bar).
3.​ An AI chatbot to understand a pet’s contextual memory of the chat history.
4.​ Receive a UX prompt if no walk has been logged by 18:00 local time (“Rex still
needs exercise today!”).

Core Requirements
●​ Tech stack (pick ONE):​
React + Node/Express, Vue + Fastify, or Flutter (web target) + Dart back-end
(shelf).
●​ Data: Keep everything in memory (array/object) – no DB.
●​ API endpoints
●​ UI/UX expectations:​
– Mobile-first responsive design (max-width 480 px look)​
– Clean, pet-friendly palette & accessible colour contrast​
– Instant form validation feedback (e.g., empty field warnings)​
– Lightweight animation on the data-vis element (CSS or Lottie OK)
●​ Code quality: Clear folder structure, meaningful commit messages, concise
comments.

Deliverables
1.​ GitHub/GitLab repo link (or zipped project)
2.​ Short README (≤200 words) that covers: stack choice, run steps, and any
trade-offs.
3.​ 1-minute screen-capture (optional but encouraged) showing the flow.
Email the above to hello@[Link] by 23 Aug 23:59 BST.
Evaluation Criteria
●​ Correctness & API design clarity
●​ UI polish and basic UX heuristics (readable, responsive, intuitive)
●​ Code organisation & naming discipline
●​ Thoughtful handling of edge cases (future dates, empty summary, etc.)

You might also like