Rippling Software Engineer interview experience

I was given a task list with task durations and a dependency list expressed as pairs of tasks, where one had to be finished before another could begin. The core of the work was figuring out the right way to process dependencies and make sense of the ordering.

After that, I moved to a low-level design interview. The format still leaned on reasoning through a structured problem using the kind of relationships implied by those dependency inputs, and I had to lay out an approach clearly rather than just jump into code. The whole thing felt fairly direct technically: DS&A first, then LLD as the