Training Data: https://docs.google.com/spreadsheets/d/1yLDum7yWr3IH0KivluCBEvqHGlfvFW_S/edit?usp=sharing&ouid=107676686611527271344&rtpof=true&sd=true
Test Data: https://docs.google.com/spreadsheets/d/1lCvTufEhGgtDJp6b9oYyFXpCZqWPirSX/edit?usp=sharing&ouid=107676686611527271344&rtpof=true&sd=true
Theme: From Understanding Humans → To Guiding Them
At ArvyaX, we are building AI systems that go beyond prediction.
We aim to create intelligence that can:
understand human emotional state
reason under imperfect and noisy signals
decide meaningful next actions
guide users toward better mental states
After immersive sessions (forest, ocean, rain, mountain, café), users write short reflections.
These reflections are:
messy
short or vague
sometimes contradictory
We also collect lightweight contextual signals:
sleep
stress
energy
time of day
previous mood
⚠️ Important : This is NOT a standard classification problem.
Real-world systems must handle:
noisy text
missing data
conflicting signals
imperfect labels
Your goal is to build a system that can understand → decide → guide.
Objective
Build a system that takes user input and produces:
predicted_state
predicted_intensity (1–5)
Your system must decide:
➤ What should the user do?
(e.g., breathing, journaling, deep work, rest)
➤ When should they do it?
now
within_15_min
later_today
tonight
tomorrow_morning
For each prediction:
confidence (0–1)
uncertain_flag (0 or 1)
👉 A strong system knows when it is unsure.
Generate a short human-like response explaining the recommendation.
Example:
“You seem slightly restless right now. Let’s slow things down. Try a short breathing exercise before planning your day.”
You are provided with a dataset containing: id, journal_text, ambience_type, duration_min, sleep_hours, energy_level, stress_level, time_of_day, previous_day_mood, face_emotion_hint, reflection_quality, emotional_state, intensity
Tasks
Predict:
emotional_state
Predict:
intensity
Explain whether you treat this as:
classification
regression
Design logic to decide:
Examples: box_breathing, ournaling. grounding, deep_work, yoga. sound therapy, light_planning, rest, movement, pause
Options: now, within_15_min, later_today, tonight, tomorrow_morning
Your system should use: predicted state, intensity, stress, energy, time of day
Provide:
confidence score
uncertain flag
Explain:
what features mattered most
text vs metadata importance
Compare:
text-only model
text + metadata model
Analyze at least 10 failure cases.
Explain:
what went wrong
why the model failed
how to improve
Focus on:
ambiguous text
conflicting signals
short inputs
noisy labels
Explain how your system would run:
on mobile
on-device
Discuss:
model size
latency
tradeoffs
Explain how your system handles:
very short text (“ok”, “fine”)
missing values
contradictory inputs
scikit-learn
XGBoost
PyTorch
TensorFlow
local lightweight models
OpenAI / Gemini / Claude APIs
any hosted LLM
* Your solution must run locally.
End-to-end pipeline
id
predicted_state
predicted_intensity
confidence
uncertain_flag
what_to_do
when_to_do
Include:
setup instructions
approach
feature engineering
model choice
how to run
Include:
10 failure cases
insights
Explain:
deployment approach
optimizations
ML + reasoning - 20%
Decision logic (what + when) - 20%
Uncertainty handling- 15%
Error analysis depth - 15%
Feature understanding- 10%
Code quality- 10%
Edge thinking- 10%
We are looking for:
real-world thinking
ability to handle messy data
reasoning under uncertainty
meaningful decision-making
product-oriented mindset
Not just accuracy.
supportive conversational message
small local API (Flask/FastAPI)
simple UI demo
lightweight conversational model (SLM)
label noise handling
During the interview, you will be asked to:
explain your model
justify decisions
walk through failure cases
AI should not just understand humans. It should help them move toward a better state.
Dream > Innovate > Create
— Team ArvyaX