Rippling Mobile Engineer System Design Questions

Rippling needs an efficient system that can schedule and execute background tasks, such as fetching updates or syncing data, without impacting user experience or device resources.
Design a class TaskScheduler with the following methods:
- void scheduleTask(Task task) to schedule a new background task.
- void executeTasks() to run any scheduled tasks while ensuring they do not exceed resource limits.
- List<Task> getPendingTasks() to retrieve tasks waiting for execution.Example 1:
Input: Task task = new Task(); taskScheduler.scheduleTask(task);
Output: task will be executed based on system resource availability Example 2:
Input: List<Task> pendingTasks = taskScheduler.getPendingTasks();
Output: List of all tasks not yet executed Constraints:
- `Tasks may vary in size and complexity and must each include metadata for execution priority and resource requirements.

Rippling demands a robust system that allows mobile users to work offline and sync their actions with the server when they regain connectivity, ensuring data integrity and a seamless user experience.
Design a class SyncEngine with the following methods:
- void sync(Data data) to upload changes from the device to the server.
- Data fetch() to download data from the server when online.
- void saveLocally(Data data) to save data changes locally when offline.Example 1:
Input: Data data = new Data(); syncEngine.sync(data);
Output: data will be uploaded when the device is back online Example 2:
Input: Data data = syncEngine.fetch();
Output: fetch returns the latest data from the server Constraints:
- Data can represent various user actions and changes due to network unavailability.