CBRE Software Engineer interview typically runs 1 round: coding plus technical. The process is usually quick, direct, and resume-driven, with little small talk.
$107K
Avg. Base Comp
$166K
Avg. Total Comp
3 rounds
Typical Rounds
1-2 weeks
Process Length
Our candidates report that CBRE’s software engineering interviews are less about flashy puzzles and more about whether you can defend the technical choices on your own resume. Even when the coding itself is simple, the conversation quickly shifts into project depth: why you built something a certain way, what tradeoffs you made, and whether you actually understand the systems you’ve touched. That makes the interview feel direct and efficient, but also unforgiving if your experience is only surface-level.
A recurring theme is the company’s interest in practical AI fluency. One candidate noted that the interviewer kept circling back to AI-related functionality and wanted more than buzzwords — they were probing for real understanding. We’ve also seen basic web fundamentals used as a filter inside a broader technical discussion, like the GET/PUT/POST distinction, which suggests CBRE is checking whether candidates can explain core API behavior cleanly under pressure. The behavioral portion appears to come late and briefly, so the real signal is how confidently you can walk through your background without hand-waving.
Synthetized from 1 candidates 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 Cbre process.
The interview was pretty straightforward, but it was much more technical than I expected from the start. After a quick 5–7 minute introduction, they went straight into my resume and technical background, and most of the conversation stayed there. I had one coding plus technical round overall. The coding portion itself was simple, but they spent a lot of time digging into my projects, background, and whether I actually understood the technical choices I’d made. They seemed especially interested in AI-related functionality and wanted to see if I had a solid grasp of that area, not just surface-level familiarity.
One of the more basic questions they asked was to differentiate between GET, PUT, and POST, but even that was part of a broader technical grilling rather than a standalone trivia question. After about 15 minutes of technical questions, they wrapped up with behavioral questions. The process felt direct and efficient, with very little small talk. I didn’t feel like they were trying to trick me, but they definitely expected me to be comfortable explaining my own experience in detail and defending the technical decisions behind my work. In my case, I didn’t get an offer, so I’d say the main takeaway is to be ready for a resume-driven interview where they can pivot quickly from simple coding into deeper technical discussion, especially around AI concepts and core web/API basics.
Prep tip from this candidate
Be ready to walk through your own projects in detail, especially any AI-related work, because they spent a lot of time probing technical depth from the resume. Also review basic HTTP methods like GET, PUT, and POST so you can explain the differences clearly under pressure.
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 Cbre
What do you tell an interviewer when they ask you what your strengths and weaknesses are?
| Question | |
|---|---|
| 2nd Highest Salary | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Largest Salary by Department | |
| Employee Salaries | |
| Prime to N | |
| Raining in Seattle | |
| Closest SAT Scores | |
| Find the Missing Number | |
| Size of Joins | |
| First Touch Attribution | |
| Hurdles In Data Projects | |
| P-value to a Layman | |
| Rectangle Overlap | |
| Employee Project Budgets | |
| Find the First Non-Repeating Character in a String | |
| Top 5 Turnover Risk | |
| Find Duplicate Numbers in a List | |
| The Brackets Problem | |
| Manager Team Sizes | |
| Sort Strings | |
| Cyclic Detection | |
| Target Indices | |
| Get Top N Frequent Words | |
| New Resumes | |
| Minimum Absolute Distance | |
| Google Maps Improvement | |
| Nearest Common Ancestor | |
| String Mapping |
Synthesized from candidate reports. Individual experiences may vary.
The interview starts with a brief 5–7 minute introduction, then quickly moves into a resume and technical background review. Expect the interviewer to spend most of the time digging into your past projects, technical decisions, and whether you truly understand the work you list on your resume.
There is one combined coding and technical round overall. The coding portion is described as simple, but the discussion goes deeper into core technical concepts such as GET vs. PUT vs. POST, web/API basics, and AI-related functionality tied to your experience.
The final portion of the interview shifts into behavioral questions. This stage is relatively short and direct, with little small talk, and is used to assess communication, ownership, and how you explain your work under scrutiny.