Payday Forecasting: Product and Model Design for Predicting Paycheck Arrival

Design a product that tells people when their next paycheck will arrive. Explain who it is for, what it does for them, and how it would make the prediction. ```hint Look at what the deposits reveal Picture a year of someone's bank deposits and ask which patterns in amount, timing and payer set a paycheck apart from other money coming in, and what makes the next date hard to call. ``` ### Clarifying Questions - Is this a standalone product, or a feature inside a personal finance app that can already see the user's linked bank accounts? - Should it cover gig workers and freelancers with irregular income, or only people paid by an employer on a fixed schedule? - Will the prediction only be shown to the user, or will it trigger actions such as scheduling bill payments or transfers to savings? - Which countries are in scope, given that pay schedules and bank holidays differ between them? ### What a Strong Answer Covers - The user problems that knowing payday solves, a chosen segment, and the product experience built around the prediction. - How paychecks are told apart from other deposits and how the next date and amount are forecast, including pay frequencies, weekends and holidays. - How the product handles low confidence, schedule changes and irregular income without misleading users. - Success metrics for both prediction accuracy and user outcomes, with guardrails. - Privacy, data access, and the risks of acting on a wrong prediction. ### Follow-up Questions - A user changes jobs and the new employer pays on a different schedule. How quickly does your product adapt, and what does the user see in the meantime? - A predicted paycheck triggers an automatic savings transfer, the deposit comes late, and the user overdraws. How do you design against that? - How would you forecast income for a rideshare driver who is paid out several times a week in varying amounts?