Two campus-hiring candidates describe JLL's Software Engineer process as an aptitude test, a group discussion, and a technical interview on projects, SQL, C or Python, with one also reaching an HR round. A third describes a recruiter and hiring manager route.
$102K
Avg. Base Comp
$133K
Avg. Total Comp
3-4 rounds
Typical Rounds
Not reported
Process Length
The clearest picture of JLL's Software Engineer interview comes from two campus-hiring candidates. Both describe an online aptitude test, then a group discussion on whether extracurricular activities should be compulsory in schools. A technical interview followed. One of them also describes an HR round.
The technical round leans on your own projects and fundamentals more than on hard algorithm puzzles. One candidate says the interviewers spent most of the time on why they chose specific technologies. They then asked for a simple C program, a numerical puzzle, and a SQL query to find employees who joined in the last six months from a DATE field. The other candidate, interviewing for an internship with a pre-placement offer, was asked about Python libraries, SQL commands, some data structures, OOP, and how to store interconnected tables in Python data structures.
The internship candidate reached HR, where scenario questions tested flexibility. Hesitating about working outside their core area may have hurt them. Both of these candidates ended without an offer.
A separate candidate in a general tech role applied through the website. They describe a recruiter screen and a hiring manager conversation, both positive, followed by months of silence. Applicants outside campus drives may want to follow up in writing.
Prepare by rehearsing a plain explanation of the technology choices in each project. Practice date-filtering SQL and basic C syntax. Be ready to say honestly where you would be willing to work.
Synthesized from 4 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 Jll process.
I interviewed at JLL for a Software Engineer role during their campus placement drive in late 2024. The process had multiple stages, starting with an online aptitude test covering CSE fundamentals and general reasoning. I cleared that and moved into a group discussion with about ten other candidates. The topic was whether extra co-curricular activities should be compulsory in school — it was a standard behavioral round to see how you communicate and collaborate under pressure.
For the technical interview, they started by asking me to introduce myself and walk through my past projects. They spent most of the time drilling into my tech stack choices, which was their real focus. I wasn't asked to design something from scratch; instead, they wanted to understand why I'd made specific technology decisions and how deep my knowledge went. Then they moved into coding. They gave me a simple C program to write — nothing complex algorithmically, but it tested basic syntax and logic. After that came a numerical puzzle, which felt more like a puzzle-solving exercise than a pure coding problem.
The last part was SQL. They asked me to write a query to find all employees who joined in the last six months using a DATE field in a company DBMS. It required understanding date arithmetic and filtering, so I had to think through the logic carefully. The whole technical round was moderate in difficulty — they weren't looking for LeetCode-hard problems, but they did expect you to think clearly and code cleanly.
I didn't receive an offer. The process was fairly structured for a campus placement, and while I got through the early rounds, the technical bar was still there.
Prep tip from this candidate
Focus heavily on articulating why you chose specific technologies in your projects — JLL spends significant time on that. Also brush up on date-based SQL queries and basic C syntax, as those are concrete skill areas they test.
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 Jll
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Top Three Salaries | |
| Merge Sorted Lists | |
| Closest SAT Scores | |
| Employee Salaries | |
| Prime to N | |
| Largest Salary by Department | |
| Top 3 Users | |
| Top 5 Turnover Risk | |
| Raining in Seattle | |
| Find the Missing Number | |
| Rolling Bank Transactions | |
| Bagging vs Boosting | |
| Size of Joins | |
| Retailer Data Warehouse | |
| Maximum Profit | |
| Find the First Non-Repeating Character in a String | |
| Over-Budget Projects | |
| P-value to a Layman | |
| Hurdles In Data Projects | |
| Real-Time Transaction Streaming | |
| The Brackets Problem | |
| Employee Project Budgets | |
| Repeated Category Purchase | |
| SELECTive Wine Connoisseur | |
| Google Maps Improvement | |
| Cyclic Detection | |
| Get Top N Frequent Words | |
| Find Duplicate Numbers in a List | |
| Resumable Fact Table Load |
Synthesized from candidate reports. Individual experiences may vary.
Candidates in campus drives report starting with an online aptitude test. One describes CSE fundamentals and general reasoning. Another describes math, SQL and Python multiple-choice questions, proctored by campus staff. Solid fundamentals are likely the main requirement.
Both campus candidates report a group discussion on whether extracurricular activities should be compulsory in schools. One mentions about ten participants. It appears to assess communication and how you hold your own in a group, so practice structured, concise points.
Candidates report questions on past projects, with heavy focus on why they chose their technologies. Other reported topics include a simple C program, a numerical puzzle, and a SQL query on a DATE field. Others include Python libraries, OOP, data structures, and storing interconnected tables. Difficulty was described as moderate.
The internship candidate reports a final HR round of scenario-based questions. They were asked whether they would work outside their core area, and they believe their hesitation may have cost them. This was one candidate's experience, so be ready to discuss flexibility on role placement.
One candidate in a general tech role, who applied through the website, reports a recruiter screen followed by a hiring manager interview, both positive. They then heard nothing for months and the application later showed as completed. Keep written follow-ups if you apply this way.
