Skip to main content
Logo
Overview

JLL Frontend Developer Interview Experience (React, API, Pagination, Filters)

April 7, 2026
3 min read

Interview Experience: Front End Developer @ JLL (Chhatrapati Sambhajinagar)

I recently went through the interview process for a Front End Developer role at JLL. This was a hands-on, React-focused interview with real-world tasks like API integration, pagination, and building filterable tables. Sharing my experience in case it helps others preparing for frontend interviews.

Getting Started

I got a referral for the position and was contacted by HR shortly after. As part of the preparation, I was asked to set up a local React environment before the interview. This made it clear from the beginning that the process would be practical and coding-heavy rather than purely theoretical.

Round 1: API Integration and Pagination

In the first round, I was given an API and asked to:

  • Fetch data from the API
  • Display it in the UI
  • Implement pagination

I completed the task end-to-end, including data fetching and pagination logic. The UI was functioning as expected, but there was a small intermittent issue where pagination was not syncing properly.

Instead of ignoring it, I clearly explained:

  • What the issue was
  • Possible causes of the bug
  • How I would debug and fix it

I walked the interviewer through my code and reasoning, which helped demonstrate my thought process.

Result: Selected for the next round.

Round 2: Table with Filters

The second round had two panelists and was more focused on UI building and state management.

I was given a hardcoded dataset and asked to:

  • Build a data table using any library of my choice

  • Add filters for multiple columns using:

    • Text input
    • Date input
    • Dropdown select

I approached this by first building the UI structure and then integrating the data.

What I implemented:

  • Table UI with structured data rendering
  • Integration of mock dataset
  • Filter components for different input types
  • State management for applying filters

I was able to complete around 90% of the implementation. The remaining 10% involved finalizing filter logic and edge cases, but I ran out of time.

After the coding part, the discussion shifted to theory:

  • How I would complete the remaining logic
  • Questions on React fundamentals
  • Performance optimizations and best practices

Result: Selected again.

Final Stage

After clearing both technical rounds, HR informed me about a final in-person techno-managerial round. However, there was a delay due to internal townhall meetings.

  • I was asked to wait for further updates
  • A week passed without communication
  • Follow-ups initially didn’t receive a response

Eventually, through my reference, I found out that the position had been closed because they needed someone who could join immediately and had moved forward with another candidate.

Takeaways

  • Explaining your thought process clearly can matter more than writing perfect code
  • Real-world tasks like API handling, pagination, and filters are common in frontend interviews
  • Time management is critical, especially when tasks are UI-heavy
  • Hiring decisions can depend on urgency and availability, not just interview performance

Final Thoughts

Even though I didn’t get the offer, the experience was valuable and closely reflected real-world frontend work. It reinforced the importance of communication, structured thinking, and handling practical problems under time constraints.

If you’re preparing for frontend interviews, especially in React, focus on:

  • API integration and loading/error states
  • Pagination and data handling
  • Building reusable UI components
  • Implementing filters and managing state effectively
  • Debugging real-world UI issues

Practicing projects like tables, dashboards, and filterable lists can significantly improve your readiness for such interviews.


If you’ve had a similar frontend interview experience, feel free to share your approach and the kind of problems you encountered.