Add Future-Dated and Backdated Employee Changes to an HR Records App

Quick Overview

Extend a full-stack employee records app so salary, title and other changes can be scheduled to take effect on a future date, then handle a change entered after its effective date has passed. Tests effective-dated data modeling, as-of queries, API and UI design, audit history and downstream corrections.

Add Future-Dated and Backdated Employee Changes to an HR Records App

Company: Rippling

Role: Software Engineer

Category: Software Engineering Fundamentals

Difficulty: medium

Interview Round: Onsite

You are working on a small full-stack application for employee records: a backend API over a relational database, and a web UI where an admin views an employee and edits fields such as salary and title. In the starting version each employee has one record, and saving an edit overwrites it immediately. The change to build: the app must support personnel changes that take effect in the future. An admin should be able to enter, for example, a new title and salary effective on a future date. Until that date the app keeps showing the current values; from that date on it shows the new ones, without anyone editing the record again. As a follow-up, the interviewer asks how to handle adding an event that has already taken effect, that is, one dated in the past. The report does not describe the starting app's stack or schema, so state the minimal version you assume and build the change on top of it. ### Clarifying Questions - Which fields can be scheduled (salary and title, and others such as department or manager), and is a change made per field or as a whole-record snapshot? - Is an effective date a calendar date or a timestamp, and in which time zone does a new day start? - If two changes to the same field have the same effective date, which one wins? - Can a scheduled change be edited or cancelled before it takes effect? - Do other systems need to be told when a change takes effect? ### Part 1 — Support changes that take effect in the future Change the data model, the API and the UI so that an admin can schedule a change for a future date, every screen shows the values in force today, and the admin can see what is scheduled. Decide whether today's values are computed when they are read or written into the record when the date arrives, and justify the choice. Show the core code and how you test it. ```hint Keep the history Ask what the app loses when a scheduled change is written straight into the employee's record, and what single query would answer "what was this employee's title on date D?" ``` ```hint Does midnight need a job? Think about what must happen at the start of the effective date in your design, and what goes wrong if that step runs late, twice or not at all. ``` #### What This Part Should Cover - An effective-dated model and the as-of read that resolves the values in force on a given date - API and UI changes for scheduling a change, viewing upcoming changes, and editing or cancelling one - Resolving values at read time versus a job that applies due changes, with the failure modes of each - The tie rule, the time zone of the effective date, and tests that fix the clock ### Part 2 — Add an event that already happened An admin must now record a change whose effective date is in the past, for example a title change that should have applied two months ago, possibly earlier than changes already on file. How does your design handle it, and what else in the system has to react? ```hint Two different times Separate the date a change took effect from the moment the system learned about it, and ask which questions need each one. ``` #### Clarifying Questions for this Part - Is the backdated event a correction of a mistake, or a real change that was reported late? - Must the app still be able to show what it displayed before the backdated event was entered? #### What This Part Should Cover - Inserting into the middle of a timeline, and how later changes to the same field interact with it - Recording both the effective date and the entry time, so earlier views can be reproduced and audited - Anything already computed from the old values, such as reports or pay, and how it is flagged or corrected - Validation and permissions for retroactive changes ### What a Strong Answer Covers - A per-employee timeline of changes with an as-of read, instead of a single overwritten row - Explicit rules for ordering, ties, edits and cancellations - Correct handling of the effective day boundary and time zones - Backdated inserts with an audit history and downstream recalculation - A working change across database, API and UI, covered by tests that pin the clock ### Follow-up Questions - Two admins schedule different salaries for the same employee on the same date. What does the app do? - A termination is scheduled for a date before a raise that is already scheduled. How do you catch it? - How would you show the whole organization as of a past or future date efficiently? - How do you notify downstream systems exactly once when a scheduled change takes effect?

Overview: Extend a full-stack employee records app so salary, title and other changes can be scheduled to take effect on a future date, then handle a change entered after its effective date has passed. Tests effective-dated data modeling, as-of queries, API and UI design, audit history and downstream corrections.

Rippling logo
Rippling
Oct 23, 2026
mediumSoftware EngineerOnsiteSoftware Engineering Fundamentals
1
0

You are working on a small full-stack application for employee records: a backend API over a relational database, and a web UI where an admin views an employee and edits fields such as salary and title. In the starting version each employee has one record, and saving an edit overwrites it immediately.

The change to build: the app must support personnel changes that take effect in the future. An admin should be able to enter, for example, a new title and salary effective on a future date. Until that date the app keeps showing the current values; from that date on it shows the new ones, without anyone editing the record again. As a follow-up, the interviewer asks how to handle adding an event that has already taken effect, that is, one dated in the past.

The report does not describe the starting app's stack or schema, so state the minimal version you assume and build the change on top of it.

Clarifying Questions Guidance

  • Which fields can be scheduled (salary and title, and others such as department or manager), and is a change made per field or as a whole-record snapshot?
  • Is an effective date a calendar date or a timestamp, and in which time zone does a new day start?
  • If two changes to the same field have the same effective date, which one wins?
  • Can a scheduled change be edited or cancelled before it takes effect?
  • Do other systems need to be told when a change takes effect?

Part 1 — Support changes that take effect in the future

Change the data model, the API and the UI so that an admin can schedule a change for a future date, every screen shows the values in force today, and the admin can see what is scheduled. Decide whether today's values are computed when they are read or written into the record when the date arrives, and justify the choice. Show the core code and how you test it.

What This Part Should Cover Guidance

  • An effective-dated model and the as-of read that resolves the values in force on a given date
  • API and UI changes for scheduling a change, viewing upcoming changes, and editing or cancelling one
  • Resolving values at read time versus a job that applies due changes, with the failure modes of each
  • The tie rule, the time zone of the effective date, and tests that fix the clock

Part 2 — Add an event that already happened

An admin must now record a change whose effective date is in the past, for example a title change that should have applied two months ago, possibly earlier than changes already on file. How does your design handle it, and what else in the system has to react?

Clarifying Questions for this Part Guidance

  • Is the backdated event a correction of a mistake, or a real change that was reported late?
  • Must the app still be able to show what it displayed before the backdated event was entered?

What This Part Should Cover Guidance

  • Inserting into the middle of a timeline, and how later changes to the same field interact with it
  • Recording both the effective date and the entry time, so earlier views can be reproduced and audited
  • Anything already computed from the old values, such as reports or pay, and how it is flagged or corrected
  • Validation and permissions for retroactive changes

What a Strong Answer Covers Guidance

  • A per-employee timeline of changes with an as-of read, instead of a single overwritten row
  • Explicit rules for ordering, ties, edits and cancellations
  • Correct handling of the effective day boundary and time zones
  • Backdated inserts with an audit history and downstream recalculation
  • A working change across database, API and UI, covered by tests that pin the clock

Follow-up Questions Guidance

  • Two admins schedule different salaries for the same employee on the same date. What does the app do?
  • A termination is scheduled for a date before a raise that is already scheduled. How do you catch it?
  • How would you show the whole organization as of a past or future date efficiently?
  • How do you notify downstream systems exactly once when a scheduled change takes effect?