Smartsheet Senior Software Engineer Interview Experience
Interview Experience
Role: Senior Software Engineer HR Screening (15 mins) Initially received a call from HR through a referral. The discussion was around: Current project and responsibilities Tech stack being used How I
Full Details
Role: Senior Software Engineer HR Screening (15 mins) Initially received a call from HR through a referral. The discussion was around: Current project and responsibilities Tech stack being used How I handle scale and high-traffic scenarios It was a brief and smooth conversation.
Round 1 DSA Round Question 1: Given a set of numbers and a target value,
return all possible ways to construct a set whose sum equals the target. The same number can be used multiple times. (This is similar to a backtracking / combination sum problem.)
Follow-up Question: Modify the solution such that: A number can be used only as many times as it appears in the input set. Also generate set of number used. Focus was on: Correct approach Handling edge cases Time and space complexity
Round 2 System Design (Live Chat Application) The round started with discussion about: Past projects Overall experience Then I was asked to design a chat application for users watching a live event. Key discussion points: Functional requirements (real-time messages, ordering, scalability) Handling large number of concurrent users How to fetch old message High-level architecture and data flow
Round 3 System Design (Playo-like Application) Asked to design an application similar to Playo. Requirements included: Users should be able to view free playground Users should be able to make and modify booking Admin should be able to revise bookings and manage data Discussion focused on: Entity design API design Handling conflicts in bookings(most imp) Scalability considerations
Round 4 Hiring Manager Round This round was a deep dive into: Projects I have worked on Technical challenges faced and how I solved them Key learnings from past experience Also included leadership and behavioral questions such as: How I resolve conflicts within a team Decision-making in difficult situations Final Step: Aptitude Test There was a short aptitude test at the end, mainly to assess logical and analytical thinking.
Verdict waiting
About This Question
This is a candidate experience report from a smartsheet interview for a swe role (senior level) during the behavioral round reported in 2026.
It covers the following topics: System Design, Backtracking, Behavioral, Recursion, Stack .
Difficulty rating: Hard
About Smartsheet Interview Reports
This question was reported by a candidate who interviewed at Smartsheet. 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 Smartsheet are the higher-signal extractions to take from this report.
For broader preparation context, the Smartsheet 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 Smartsheet reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Smartsheet 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 Smartsheet 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.