Need help? Reach out to us
Back to library

Proptech and construction tech

Roofandfloor Full Stack Developer Interview: Rounds, Questions and Preparation

For Full Stack Developer roles at companies like Roofandfloor

Share with friends

Preparing together? Send them this role's questions.

https://www.cynchrony.in/library/roofandfloor-full-stack-developer

What the job involves

A Full Stack Developer in proptech and construction tech builds and maintains web applications that connect property buyers, sellers, agents, and construction professionals. Day to day, you work on both front-end interfaces (like property listing pages, search filters, and dashboards) and back-end services (APIs, databases, and integrations with maps or CRM systems). You also collaborate with product and design teams to ship features quickly in a fast-growing environment.

Role and technical knowledge

  1. 1

    How would you design a database schema for a property listing platform that includes properties, owners, and enquiries?

    A strong answer covers tables or collections for properties (with fields like location, price, type), owners (linked by ID), and enquiries (with timestamps and status). Mention indexing on location and price for fast search.

  2. 2

    Explain how you would implement a search filter that lets users find properties by city, price range, and number of bedrooms.

    Cover both front-end state management (e.g., React state or query params) and back-end query building (e.g., MongoDB $and or SQL WHERE clauses). Mention debouncing and pagination for performance.

  3. 3

    What are the key differences between SQL and NoSQL databases, and which would you choose for a construction project management tool?

    Discuss structured vs flexible schema, scalability, and use cases. For construction projects with changing requirements, NoSQL (like MongoDB) can be good, but SQL works well for transactional data. Justify your choice.

  4. 4

    How do you ensure a property listing page loads quickly even with many images and map integrations?

    Mention lazy loading, image compression, CDN usage, code splitting, and caching. Also talk about limiting map API calls and using placeholders.

Practical scenarios

  1. 5

    A user reports that the enquiry form on a property page is not submitting. How would you debug this?

    Walk through checking browser console for errors, network tab for failed requests, validating front-end form data, and testing the API endpoint separately. Mention logging and reproducing the issue.

  2. 6

    You need to add a feature that shows nearby schools and hospitals for a property. How would you approach it?

    Discuss using a maps API (like Google Places), storing coordinates, making asynchronous calls, and caching results. Also consider fallback if API fails and display on front-end.

  3. 7

    Your team wants to integrate a third-party CRM for lead management. What steps would you take?

    Cover understanding the CRM API, authentication (API keys or OAuth), mapping data fields, handling errors and retries, and testing with sandbox credentials. Mention security of API keys.

  4. 8

    How would you handle a situation where the front-end and back-end teams have different assumptions about an API response format?

    Suggest documenting the API contract early, using tools like Swagger or Postman, and having a quick sync. Mention writing mock responses and unit tests to catch mismatches.

Behavioural and teamwork

  1. 9

    Tell me about a time you had to learn a new technology quickly for a project.

    Use a specific example from college or internship. Highlight how you found resources, built a small prototype, and applied it. Show willingness to learn.

  2. 10

    Describe a situation where you disagreed with a teammate on a technical approach. How did you resolve it?

    Focus on listening, presenting data or pros and cons, and reaching a consensus. Avoid blaming; show you value team success over being right.

  3. 11

    How do you prioritise tasks when you have multiple deadlines in a fast-growing startup?

    Mention using a simple framework like impact vs effort, communicating with your manager, and breaking work into smaller chunks. Show flexibility and transparency.

  4. 12

    Why are you interested in working in proptech or construction tech rather than a general tech company?

    Connect personal interest in real estate, construction, or solving India-specific problems like finding verified listings. Show you understand the sector's challenges and opportunities.

HR and company fit

  1. 13

    What do you know about our company and what we do in the proptech space?

    Research the company's product, target users, and recent news. Mention specific features like verified listings, construction updates, or agent tools. Show genuine curiosity.

  2. 14

    Where do you see yourself in three years as a full stack developer?

    Align your growth with the company's needs: deepening technical skills, taking ownership of modules, and contributing to architecture. Avoid saying you want to start your own company soon.

  3. 15

    How do you handle feedback, especially when it is critical of your code?

    Show openness, ask clarifying questions, and treat feedback as a chance to improve. Give an example of implementing feedback from a mentor or peer.

  4. 16

    Are you comfortable working in a hybrid or remote setup with a distributed team?

    Be honest about your preferences but emphasise adaptability, clear communication via tools like Slack or Zoom, and ability to manage time independently.

Coding round

Full Stack Developer interviews usually include a coding round. Practise planning the solution out loud, then review code the AI writes from your plan, in Python, Java, C++, C or JavaScript.

Ready to try it for real?

Take a timed test or talk through a mock interview for this role, then see your scores.

This is practice material for Full Stack Developer roles, written with AI. It is not a list of questions Roofandfloor or any other company has asked.