Question Details
Scaledgrid is a start-up providing mongodb as service on cloud. I had a skype interview and below are the questions.1) You have a single core cpu. Your applications does a...
Full Details
Scaledgrid is a start-up providing mongodb as service on cloud. I had a skype interview and below are the questions. 1) You have a single core cpu. Your applications does a lot of I/O operations. Can multi-threading used for making the application more efficient ? 2) A cluster consists of some finite number of server. A cluster is configured to use a DB(mongo db). Given that you have "n"(which can be large) clusters, give the design for a system for taking the periodic back-ups of these clusters. a) For each cluster, the cluster user would configure the start time to start taking the back-up and how frequently the back-up can be taken b) Assume you have backupservice.takebackup(Cluster cluster) throws BackUpFailedException method available c) Can multi-threading be used ? d) How is timer going to be implemented ? e) the takebackup() method can throw exception if backing up fails. How is this handled f) Define required classes with the data and methods 3) Write code for pattern matching of regular expression. Only . and * are the special characters in the pattern boolean isPatternMatched(String inputString, String pattern);
About This Question
This is a reported interview question from a scalegrid interview for a swe role reported in 2015.
It covers the following topics: Strings .
Topics
About Scalegrid Interview Reports
This question was reported by a candidate who interviewed at Scalegrid. 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 Scalegrid are the higher-signal extractions to take from this report.
For broader preparation context, the Scalegrid 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 Scalegrid reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Scalegrid 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 Scalegrid 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.