Senior Software Engineer

Landytech is building the intelligent operating platform for modern investment management. Our AI-powered platform, Sesame, brings together investment, corporate and accounting data across asset classes, custodians, currencies and legal entities, creating one secure, trusted source of truth from which our clients can understand their wealth and act with confidence.

Sesame is much more than a reporting tool. We build technology that helps asset owners, asset managers, private banks and trust and company service providers run their entire investment ecosystem: automating complex data and document ingestion, surfacing portfolio and risk insights, anticipating liquidity needs, supporting investment decisions and deal flow, streamlining collaboration and turning intelligence into action through AI.

From family offices managing multigenerational wealth to financial institutions serving clients at scale, Sesame replaces fragmented data and manual processes with clarity, control and smarter decisions.

Why this role exists

Our domain is a healthy challenge: multi-custodian, multi-currency, multi-entity financial data, modelled thoughtfully and available at scale. The platform is Kotlin and Spring microservices, with Python where it pays off: metrics, analytics and our AI work. Good features start well before any code gets written, with clear communication about the outcomes to be delivered, followed by planning, prototyping when it helps, and a design the team agrees on.

Inside an R&D team, you'll work closely with a Product Manager on initiatives, improvements and bugs: shaping the work, breaking it down with the team, and owning what you ship.

You go deep enough into the requirement to push back on it, ask the questions that need asking, and tell apart what the client needs from what the requirement says.

Then you work out how it fits. Usually the right answer is the simple one built on architecture we already have, and defending that is part of the job. Sometimes it isn't, and you're the one who flags that this is a truly new capability, writes the spec and plan, and takes it to our other architects to poke holes in before we commit.

You'll do all this in a team that uses coding agents every day, and you'll help shape how we do that well.

What you'll own

You're the engineer Product works with most closely. You sit with product and domain experts before the ticket exists, understand the business problem, push back on the requirement where it needs it, and come back with honest trade-offs on cost, risk and time. You help plan and size the work, and you keep it moving once it starts.

Security, scalability, availability and performance are design inputs on every initiative, not a hardening phase at the end. You cover tenant isolation, auth, data protection and auditability, because our clients' data is about as sensitive as it gets. You know how the system behaves under load and at month-end when everyone runs reports at once, you design to our SLOs and help set them, and you make sure we can see whether we're meeting them. When the team hits something genuinely hard, you're one of the people who goes in and solves it.

For every significant initiative you produce the design: what changes, in which services, what the contracts and data flows look like, what we reuse and what we leave alone. You write it down, take the challenge from our other architects, and improve it. When a requirement exposes a gap in the platform, you name it and propose what should exist.

You think about features end to end, from the React frontend through our Kotlin and Spring services, across data stores and events, down to Azure. You propose what goes where, and push hard for the simplest solution the existing architecture can carry.

You hold the line on coding standards, API design, testing, quality gates, and security and dependency hygiene, and you help shape them. That now covers how we work with coding agents: the rules they follow, the skills and MCP integrations we build over our own systems, and the review process that holds quality as more code gets generated. You're the one who challenges what an agent proposed, because plausible code that passes its tests can still be wrong about concurrency, a data model or a failure mode.

You model the financial domain: positions, transactions, instruments, valuations, entities and hierarchies, so it holds up as new asset classes, custodians and jurisdictions arrive. You build pipelines that stay correct when the source data is messy, late or wrong, and fast enough to run over long histories on demand.

You make the engineers around you better: mentoring, onboarding new joiners, code reviews people learn from, and a hand in our hiring. You bring back what's new and make sure it lands with the team rather than staying in your head.

You stay hands-on throughout — this is not a role whe