The R1 interview questions cover a range of topics. For layout and rendering, you'll be asked how to dynamically display tasks in a board layout based on JSON data with different statuses (To-do, In Progress, Done) and how to loop through and display task cards accordingly. In dynamic interaction, you'll need to create a form for adding new tasks, ensuring the new tasks are initially placed in the 'TO_DO' column, and handle form submission to dynamically update the board. For API consumption, you'll be required to use an API to fetch tasks, display them on the board, and fetch additional user data from a separate endpoint to display in each task card. You’ll also need to manage asynchronous API calls and ensure UI updates correctly. For task management, you'll need to ensure new tasks are added to the right column, handle updates, and optimize performance when dealing with large sets of task data. In front-end security, you'll be asked why you'd use WebSockets, security best practices, and your approach to test-driven development (TDD) and maintaining code quality. The OOP task asks you to write a Circle class to calculate the area from the topmost and center points, and to write client code to use this class to calculate the radius and area.

Round 2 interview questions focus on admin dashboard design and user management. You'll be asked about the roles that should exist in an admin dashboard for managing users and the UI design for the dashboard. The interviewer will ask you to describe how you would display a list of users and handle searching for users, particularly when dealing with a large number of users. You'll need to explain how you would display large sets of data, like 10,000 or 20,000 users, efficiently. When discussing adding a new user, you should outline the flow for adding a user in the system. The high-level architecture of an admin dashboard for user management should also be described, focusing on its components and structure. You'll also need to address security and scalability—how the system scales with growing data and maintains security. Role-based access and user management will come into play, where you'll discuss the roles required to manage users. The UI components for user management (like forms for adding users) should be outlined. Finally, you'll need to discuss how to implement searching and pagination for users, especially when dealing with large amounts of data.

In Round 3, questions focus on task management, API handling, and front-end best practices. You’ll need to display tasks dynamically in a board layout based on statuses (To-do, In Progress, Done) by looping through JSON data and rendering cards accordingly. For dynamic interaction, you'll create a form to add tasks, with default placement in the "To-do" column, and update the board via state. When consuming APIs, you'll fetch task data and assigned user names, managing asynchronous calls with React hooks. For task updates, logic ensures new tasks are placed in the correct column. To optimize performance with large datasets, implement pagination or lazy loading. Front-end security practices include input validation, preventing XSS, and using HTTPS, while TDD ensures tests are written before the code. In Object-Oriented Programming (OOP), you'll write a Circle class to calculate areas based on center and topmost points. For the admin dashboard role, key tasks involve defining roles like Admin and User, designing a UI with tables and search functionality, and handling large data with pagination. Lastly, the architecture should be modular, secure, and scalable with efficient data handling techniques.