Take-home assessment 2026

Cortile builds software for residential buildings: for the managers who run them, the front-desk teams who keep them going day to day, and the people who live in them.

For this exercise we've put together three months of data from three communities. It covers parcels, repairs, visitors, amenity bookings, noticeboard posts and resident feedback. Everything is fictional. The data is a snapshot taken on the morning of 30 September 2026.

The task

Pick one of the people below. Spend some time with the data, find something that makes their week harder than it should be, and build something that helps them.

There's no single right answer and no hidden list of features we expect. We're interested in the problem you chose, why you chose it, and the decisions you made along the way.

Priya

Building manager, Riverside Quarter, Manchester

Looks after repairs, contractors and resident satisfaction for 192 homes across three blocks. Starts every Monday catching up on what happened over the weekend.

Dan

Front-desk concierge, Canal Wharf, Birmingham

Handles parcels, visitors and contractors for 140 homes. Usually the first person residents come to when something goes wrong.

Amara

Resident, Elm Court, Leeds

Works from home, uses the gym and the guest suite, and wants to know what's going on in her building.

Tom

Regional manager, all three communities

Reports to the building owners every month. Needs to know which community needs his attention, and why.

Guidelines

Spend around three hours. Depth beats breadth: a small thing done well is better than a big thing done thinly.
Any user interface should use React and TypeScript. Everything else is up to you. It doesn't have to be a dashboard, and you can add your own backend if you need one.
Use the tools you'd normally use, including AI assistants. Tell us in your README how you used them.
The API is read-only. Like most real APIs, it sometimes fails or responds slowly, and the data isn't perfectly clean.

What to send us

A private GitHub repository shared with @sheamcdevitt and @jakehiggi.
A README that covers:
- who you built for, and the problem you picked
- what you built, and how to run it
- what you chose not to do, and why
- what you'd do next with more time
- how you used AI tools
If you like, a deployed link or a short screen recording.

The API

The base URL is https://takehome.cortile.com/api/v1. There's no authentication. Start with the API reference, or load the OpenAPI spec into your tool of choice.

Questions? Email shea@projectark.co.uk with “Cortile take-home” in the subject.