← WHOOP
First-time day at WHOOP

Fix how charging is read overnight without raising daytime false wear

You’re the ai / ml engineer. Your team is in the room. Printed Oct 17, 2026.

Overnight charging behavior is being mistaken for device removal.

Restoring sleep-window availability must not make daytime motion look like wear.

Who you’d be doing this for

“I woke up ready to train, then the app acted like I hadn’t worn it all night.”

Pia Andersen · Competitive recreational runner

She checks Sleep Performance and Recovery before deciding whether to run intervals or recover.

What is at stake

Overnight valid sleep windows fell to 94.1% after the device-state update. You have to weigh a fast threshold change against false wear classifications during normal daytime use.

Why it isn’t already fixed

Every obvious fix costs something else. That’s the part you’d have to decide.

  • overnight availability vs daytime precision
  • Python fidelity vs embedded limits
  • fast release vs regression evidence

Why WHOOP

Sleep Performance and Recovery depend on valid overnight physiological sensor data from the wearable device.

Written with these in mind

wearable ML engineersignal-processing engineerembedded AI engineer

Not your kind of problem? 40 more at WHOOP, or browse every organization.

This is the setup. The work is inside.

Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.