Ramp Software Engineer Platform SWE Online Test Experience
Question Details
This post was last edited by Anonymous on 2025-09-29 11:07. This is my third sharing this week. I'm asking for points to see my interview experience! This time, I applied for a Software Engineer/Platf
Full Details
This post was last edited by Anonymous on 2025-09-29 11:07. This is my third sharing this week. I'm asking for points to see my interview experience! This time, I applied for a Software Engineer/Platform position at the end of August and received an online assessment (OA) in mid-September. It was done on Coderbyte, with no time limit, a total of 30 minutes. The content included: 1 DSA coding question, 1 Git scripting question, and 3 multiple-choice questions (basic concepts). --- Q1. Coding Given a 2D 0/1 matrix (input as a string array), find the number of holes, i.e., connected 0 regions (connected in all four directions).
Example:
Input: ["10111", "10101", "11101", "11111"] Matrix: 1 0 1 1 1 1 0 1 0 1 1 1 1 0 1 1 1 1 1 1 Output: 2. Use DFS/BFS to flood fill and count all zero regions. Refer to LC200. --- Q2. Git Script Write a simple bash script with the following requirements: clone repo -> create a new branch -> create a file in the branch -> finally print git status. Basically, just be familiar with Git commands: git clone, git checkout -b, echo ... > file, git status --- Q3. Multiple Choice (Three Concepts) What are the differences between DFS and BFS? What is the definition of a Git merge conflict? What is the function of git diff-tree -r {commit hash}? --- The overall difficulty is not high; 30 minutes is more than enough. However, I
passed all of them but didn't follow up. Additional content (2025-09-30 06:46 +08:00): I just realized that I accidentally tagged the wrong company when sharing the results of the ramp OA on the same day. Sorry QQ
About This Question
This is a reported interview question from a ramp interview for a swe role during the oa round reported in 2025.
It covers the following topics: Array, Strings, Bfs, Tree, Dfs, Graph, Arrays, Matrix .
Difficulty rating: Easy
More Ramp Interview Questions
About Ramp Interview Reports
This question was reported by a candidate who interviewed at Ramp. 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 Ramp are the higher-signal extractions to take from this report.
For broader preparation context, the Ramp 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 Ramp reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Ramp 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 Ramp 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.