CBRE Software Engineer reports describe project-focused technical conversations, AWS and infrastructure discussion, a coding component, behavioral questions, and a planned whiteboard interview.
$126K
Avg. Base Comp
$144K
Avg. Total Comp
2 rounds
Typical Rounds
1-2 weeks
Process Length
The available CBRE Software Engineer reports point to technical conversations rooted in your own work. One candidate described a brief introduction before discussion moved into their resume, technical background, project decisions, and AI-related functionality. That interview included a simple coding portion and questions on HTTP methods, including the distinctions among GET, PUT, and POST. Behavioral questions followed the technical discussion in that account.
A separate report described a hiring-manager conversation focused on projects, background, AWS experience, and infrastructure. The candidate reported prompts about choosing among Lambda, ECS/Fargate, and EMR for large-scale data workloads, plus diagnosing an S3 data-pipeline performance issue involving 503 Slow Down throttling. That candidate was scheduled for a 90-minute face-to-face whiteboard interview but withdrew before taking it.
Prepare a clear account of your direct contribution to each project, including constraints and tradeoffs. Review practical API fundamentals, and be ready to explain how workload characteristics influence AWS service selection. For an architecture scenario, practice walking through diagnosis before proposing changes: identify likely bottlenecks, define what you would inspect, and explain how an improvement addresses the observed behavior.
Synthesized from 2 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 Cbre process.
There are 2 rounds - one hiring manager(MD or higher) will check if you are suitable for his team. Next face to face white board interview 90 minutes.
The hiring manager was busy all the time and kept postponing the meeting. He did that thrice and when he showed up , he left the camera on and went for a break leaving me and his camera alone. He came back after 5 to 7 minutes and asked me about my projects and background. He wanted to know about my AWS experience and infrastructure. 1.The Multi-Service Architecture Question Question: How do you choose between AWS Lambda, Amazon ECS (Fargate), and Amazon EMR for processing large-scale data workloads? What are the key constraints of each? 2. The Data Pipeline & Performance Question Question: A data pipeline reading from an Amazon S3 bucket is experiencing performance bottlenecks and 503 Slow Down throttling errors. How would you diagnose and optimize this architecture? While i was explaining the concepts he got another call and had to drop . It was very unprofessional so i sent an email that i would no longer attend any interviews with this company.
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 | |
| Closest SAT Scores | |
| Employee Salaries | |
| Top 3 Users | |
| Rolling Bank Transactions | |
| Largest Salary by Department | |
| Top 5 Turnover Risk | |
| Prime to N | |
| Bagging vs Boosting | |
| Raining in Seattle | |
| Find the Missing Number | |
| Retailer Data Warehouse | |
| Over-Budget Projects | |
| Size of Joins | |
| P-value to a Layman | |
| Maximum Profit | |
| The Brackets Problem | |
| Hurdles In Data Projects | |
| Find the First Non-Repeating Character in a String | |
| Minimum Change | |
| Real-Time Transaction Streaming | |
| Get Top N Frequent Words | |
| Google Maps Improvement | |
| SELECTive Wine Connoisseur | |
| Find Duplicate Numbers in a List | |
| Cyclic Detection | |
| Normalize Grades |
Synthesized from candidate reports. Individual experiences may vary.
Reported conversations examined candidates’ projects, technical backgrounds, AWS experience, and infrastructure knowledge. Prepare concise explanations of work you personally delivered, the decisions you made, and the constraints that shaped those decisions.
One report described a simple coding component alongside deeper questions about the candidate’s resume, AI-related project functionality, and HTTP methods such as GET, PUT, and POST. Behavioral questions followed the technical portion in that interview.
One candidate was scheduled for a 90-minute face-to-face whiteboard interview but withdrew before completing it. Reported architecture prompts covered selecting Lambda, ECS/Fargate, or EMR for data workloads and diagnosing S3 pipeline performance and throttling issues.
