Demandbase software engineer candidates report DSA and Java-focused technical rounds, plus system design and project discussions. Round counts and interviewer experience vary across the five reports.
$195K
Avg. Base Comp
$240K
Avg. Total Comp
2-5 rounds
Typical Rounds
Not reported
Process Length
Candidates describe a Demandbase software engineer loop built mostly around coding fundamentals and design discussion. The five reports cover roles from SDE to Staff, the format varies, and the reports don't agree on a single structure.
Data structures and algorithms come up most often. One candidate got two medium LeetCode problems in a dedicated algorithms round, another was asked to write an LRU cache on paper without an IDE, and a Staff candidate reported House Robber and a DFS graph question. Practice medium-level problems, caches included, and rehearse writing code by hand.
Java and SQL show up in several accounts. One senior candidate described a broad round covering Java Collections, multithreading, system design and SQL. A Java developer candidate reported a written test with twelve Java OOP questions, two coding problems and two SQL queries. Review core Java and basic SQL.
Design rounds range from high-level to low-level. Reports include a high-level Chess.com architecture exercise, a parking lot estimation problem, and low-level and high-level design at Staff level. Two candidates described a later techno-managerial round built around their past projects, so prepare concrete stories from your own work.
Experiences differed. One senior candidate found interviewers patient and helpful and received an offer. Others described disengaged or dismissive interviewers, and one Staff candidate reported unclear location details and poor recruiter follow-up. Confirm location and work mode early, and practice explaining your reasoning aloud.
Synthesized from 5 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Demandbase process.
I got contacted by a recruiter who pitched this as a remote role with plans to open an office in Bengaluru. That detail seemed secondary at the time, so I moved forward. The interview process itself was three rounds, all technical and pretty rigorous. The first round focused on leetcode-style problems — I got House Robber and a DFS graph question, both medium difficulty. We had about 15 days before hearing back on that one. The second round was low-level design, which felt solid; I thought I'd handled it well. Then came the third round, which was billed as a techno-managerial round covering high-level design, a project deep-dive from my resume, and some behavioral questions. Here's where things got weird: the HR kept telling me before this round that it would be "impossible to clear" and "very tough," yet they scheduled it anyway. I went in and felt like I answered everything well, but afterward HR said my candidature was on hold. What really bothered me was finding out after all three rounds that the role was actually based in Hyderabad, not Bengaluru — and the Bengaluru office they'd mentioned had no clear roadmap. When I followed up, the recruiter stopped responding. Later I discovered the role had been open for five months, which made the whole process feel like they were just cycling through candidates without a real hiring plan.
Prep tip from this candidate
Be upfront about role location and work mode before committing to interviews — this company's recruiter misrepresented both, and the process dragged across multiple rounds with communication breakdowns. The technical questions themselves (House Robber, DFS, LLD, HLD) were standard, but the organizational dysfunction and lack of clarity from HR suggests verifying location flexibility and actual hiring timelines early.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Demandbase
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Empty Neighborhoods | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Employee Salaries | |
| Monthly Customer Report | |
| Random SQL Sample | |
| Comments Histogram | |
| Top 3 Users | |
| String Shift | |
| Flight Records | |
| Rolling Bank Transactions | |
| Find the First Non-Repeating Character in a String | |
| Customer Orders | |
| Minimum Change | |
| Raining in Seattle | |
| Like Tracker | |
| Weighted Keys | |
| Find the Missing Number | |
| Recurring Character | |
| Scrambled Tickets | |
| First Touch Attribution | |
| Prime to N | |
| Job Recommendation | |
| Find Bigrams | |
| P-value to a Layman | |
| Largest Salary by Department | |
| Size of Joins |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an opening conversation about their background and the role. One senior candidate described an exploratory call, and another a project discussion. Expect to summarize your experience, and confirm location and work mode, since one Staff candidate reported confusion on this point.
Candidates report medium-level DSA problems, including two LeetCode-style problems and an LRU cache written on paper. A Java developer candidate described a written test with Java OOP, coding and SQL questions. Another reported Java fundamentals with unit testing. Content may vary by team and level.
Some candidates describe rounds where they explain their approach before or while coding. One reported discussing two problems in front of interviewers before writing code, and another a dedicated algorithms round with in-depth discussion. Practice narrating trade-offs and complexity, not only reaching a working answer.
Design questions reported include a high-level Chess.com architecture, a parking lot estimation problem, and low-level and high-level design for a Staff candidate. One senior candidate reported system design combined with Java Collections, multithreading and SQL. Prepare a structured approach and be ready to defend your choices.
Two candidates describe a final conversation about past projects. One senior candidate reported a brief system design discussion and learning about company direction. A Staff candidate reported high-level design plus a resume deep-dive and behavioral questions. Bring specific examples of decisions you made and their results.
