Rubrik | SSE | NOV 2024
Question Details
System Design 1 You need to build scp from machine 1 to machine 2 -> For huge File like of 1TB size. System Design 2 Design a scalable and fault-tolerant data collection...
Full Details
System Design 1
You need to build scp from machine 1 to machine 2 -> For huge File like of 1TB size.
System Design 2
Design a scalable and fault-tolerant data collection system that can collect logs and data from various sources (eg, application servers, tailing a file etc.) and route them to different destinations (e.g., Elasticsearch, Kafka, S3) for further processing and analysis.
R3: Code Design:
Build a Pipeline Manager where many job can be submitted and many jobs will have dependency on previous jobs one or more.
A --> B --> C ------
| |
| --> G
---> E --> F-------------^
K--> L --> M
Now What we are given:
Job { // here A,B ,C are each a job
jobId
doWork() throws EnvironmentError
}
execute() -> need to implement this function in the class which I will create.
Now the pipeline can end under 2 conditions:
1. Success -> when all jobs have executed.
2. Failure --> If atleast one job fails, then it fails. No job is in a running state.
R4: Code Design 2
Given:
// open a file descriptor for a named file
open(name string) (fd int, err error)
// pread will read len(buf) bytes, returning the number of bytes read
// if a read would exceed the end of a file, pread will return EOF
pread(int fd, buf []byte, offset int64) (int, error) //int -> how many actual bytes were read.
\t// any error occured.
\t//in our case -> only int works (-ve -> error)
// pwrite will write len(buf) bytes to a file, returning an error if not all
// bytes could be successfully written
pwrite(int fd, buf []byte, offset int64) error // filled buffer of data
// close a file, flushing any outstanding writes
close(fd int) error
Please Implement:
// copy the contents of file src to file dst.
copy(dst string, src string) error
R5: Director Round - past-experience Behviour Round
R6: Technical Deep Dive - discussion about past project by principle engineer
In case you are planning to join Rubrik, please do gothrough Blind (App) reviews and also do connect with current employees of Rubrik. WLB is a mess there, need to work 13-14 hours is what I have heard but they do pay well
About This Question
This is a reported interview question from a elastic interview for a data eng role (director level) during the system design round reported in 2024.
It covers the following topics: Sql, Strings, System Design .
Topics
About Elastic Interview Reports
This question was reported by a candidate who interviewed at Elastic. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Elastic are the higher-signal extractions to take from this report.
For broader preparation context, the Elastic interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Elastic reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Elastic Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Elastic reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.