Uma candidatura completa num minuto
Currículo e carta de apresentação personalizados, prontos a enviar.
The Sales Centre seeks its first software engineer and technical lead to shape the architecture, data model and security of a new multi-tenant SaaS platform for property-investment businesses. You will own the data model, security, payments, background jobs, integrations and safe go-live decisions while guiding the founder’s briefs and ensuring data integrity during migration.
You will implement the test framework, establish production monitoring, and lead the two‑week parallel migration of 60
Salary: TBC
Our client is a UK B2B SaaS platform for property-investment businesses. Its customers source residential properties for investors, negotiate deals and earn a fee, and the platform helps them find opportunities, manage clients and deals, and market themselves. With around 60 paying customers on a white-labelled GoHighLevel setup, the team is now rebuilding the product from scratch as its own platform, with property search, deal management, portfolio tracking, financial calculators, Claude-powered AI features and Stripe billing.
You’ll be the company’s first engineer and technical lead. You’ll own how the platform is built: the data model, security, payments, background jobs, integrations, and what is safe to go live. Your first big milestone is launching the new platform and moving 60 customers off GoHighLevel without losing data. You’ll work alongside the product founder, who builds every day using Claude Code. Your job is to guide him, not replace him: shape his briefs, catch risks early, and make sure his work and yours don’t collide. A part‑time QA analyst tests every release.
No property knowledge or visual design skills needed. The domain will be taught, and the product founder owns design. You’ll thrive here if you are Happy being the only engineer and picking up work without being told. You can explain technical risk in plain English with options and a recommendation, you’ll say when something is a bad idea and then back the decision once it’s made, you ship small and often, and you speak up as soon as something goes wrong. This probably isn’t for you if you want a team around you or day‑to‑day management, you’d rather stop a non‑developer from building with AI than help him do it well, you’re mainly a front‑end specialist, or you’d hold up shipping for weeks over architecture debates.