I'd like to report a bug: Bug: Date-range picker selects the wrong day (off-by-one) for users in negative-UTC timezones Summary: In the job search Posted date range picker, clicking a date selects the previous day. It's a timezone bug, not a locale/format one. Environment: • Chrome (also reproduced in an Incognito window, so not an extension) • macOS, system timezone America/New_York (UTC−4) • Web app (app.theirstack.com), job search filters Steps to reproduce: 1. Set your machine's timezone to a negative UTC offset (e.g. US Eastern). 2. Open the Posted date filter → calendar range picker. 3. Click June 1. Expected: the selection registers June 1. Actual: it registers May 31 — every clicked date lands one day earlier. Selecting a range (e.g. intended May 27–June 1) shows as May 26–May 31 in the header chip, with the highlighted cells shifted a day back. Root-cause hypothesis: the picker appears to treat the clicked day as UTC midnight and then render/store it in local time, which rolls it back a day for any negative-UTC-offset user. Classic

new Date(...).toISOString()

vs local-date mismatch. Users at UTC+0 or positive offsets don't see it. Workaround (for other users hitting this): set the OS timezone to Reykjavik (UTC+0, no DST) or UTC and restart the browser — then clicks land correctly. Or click one day later than intended on both ends. Suggested fix: handle picker values as timezone-agnostic date-only (e.g. format as

YYYY-MM-DD

from the local calendar day, or use a date-only type) instead of converting through UTC instants. Note: there's no manual date-entry field, so the calendar is the only way in — which makes the off-by-one the only path to a wrong range.

Thanks for the detailed report, I reproduced it and already working on a fix for the timezone off-by-one in the posted date picker.

Thank you!