This role is for an engineer who likes hard problems: ambiguous requirements, architectural trade-offs, legacy constraints, new technology, and turning all of that into something simple and scalable.

Property Shell isn't a large engineering organisation where you'll own one small part of a system, receive finished requirements from a product team and spend weeks getting decisions through layers of people.

Our engineering team is small. The product is not. And our aspirations are bigger again.

We're building a sophisticated SaaS platform that sits at the centre of how property developers, project marketers and real estate sales teams manage leads, customer interactions, stock, sales, contracts, payments, reporting, integrations, automation and increasingly intelligent workflows.

That creates some genuinely interesting engineering problems.

• How do you take a complicated real-world process and make it feel simple to a user?
• How do you design something flexible enough to work across very different organisations without creating unnecessary complexity underneath?
• When should part of an established platform be modernised, and when is rewriting it simply engineering for engineering's sake?
• How should AI actually change a CRM beyond adding a chatbot to it?
• How do you keep a growing SaaS platform moving quickly while making technical decisions that will still make sense years from now?
• How do you take a platform built successfully for one market and evolve it into technology that can scale across countries, customers and increasingly different ways of doing business?

• These aren't theoretical exercises. They're the kinds of problems we're solving now.And because our engineering team is small, the people solving them have a meaningful influence over what the product becomes.

This role is for an engineer who likes hard problems: ambiguous requirements, architectural trade-offs, legacy constraints, new technology, and turning all of that into something simple and scalable.

Property Shell isn't a large engineering organisation where you'll own one small part of a system, receive finished requirements from a product team and spend weeks getting decisions through layers of people.

Our engineering team is small. The product is not. And our aspirations are bigger again.

We're building a sophisticated SaaS platform that sits at the centre of how property developers, project marketers and real estate sales teams manage leads, customer interactions, stock, sales, contracts, payments, reporting, integrations, automation and increasingly intelligent workflows.

That creates some genuinely interesting engineering problems.

• How do you take a complicated real-world process and make it feel simple to a user?
• How do you design something flexible enough to work across very different organisations without creating unnecessary complexity underneath?
• When should part of an established platform be modernised, and when is rewriting it simply engineering for engineering's sake?
• How should AI actually change a CRM beyond adding a chatbot to it?
• How do you keep a growing SaaS platform moving quickly while making technical decisions that will still make sense years from now?
• How do you take a platform built successfully for one market and evolve it into technology that can scale across countries, customers and increasingly different ways of doing business?

• These aren't theoretical exercises. They're the kinds of problems we're solving now.And because our engineering team is small, the people solving them have a meaningful influence over what the product becomes.