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.
Synthesized from 1 candidate report 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.
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 | |
| Closest SAT Scores | |
| Merge Sorted Lists | |
| Employee Salaries | |
| Prime to N | |
| Rolling Bank Transactions | |
| Largest Salary by Department | |
| Top 3 Users | |
| Raining in Seattle | |
| Bagging vs Boosting | |
| Find the Missing Number | |
| Retailer Data Warehouse | |
| P-value to a Layman | |
| Size of Joins | |
| Hurdles In Data Projects | |
| Maximum Profit | |
| Over-Budget Projects | |
| SELECTive Wine Connoisseur | |
| The Brackets Problem | |
| Find the First Non-Repeating Character in a String | |
| Get Top N Frequent Words | |
| Real-Time Transaction Streaming | |
| Google Maps Improvement | |
| Cyclic Detection | |
| Top 5 Turnover Risk | |
| Find Duplicate Numbers in a List | |
| Manager Team Sizes | |
| Sort Strings |
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.