Senior Backend Engineer Remote (EU)

Weve Security Limited; Ireland; Remote; EUR 85,000 - 110,000; Full time

Job summary

Weve is building workplace security for a world where people and AI agents work across dozens of systems. You’ll own backend work from data modelling through production behaviour, our stack includes TypeScript, PostgreSQL, ClickHouse and Temporal.

The interesting work is deciding where state belongs, how work recovers from failure and how the system stays understandable as sources and customers grow. You’ll design durable workflows, model identities and resources, and craft APIs and queries that

Qualifications

• Own production backend systems beyond initial release.
• Strong TypeScript or comparable backend language experience.
• Relational data modelling and practical SQL performance skills.
• Understanding of asynchronous execution, concurrency and idempotency.
• Care with access control and tenant isolation to protect data.

Responsibilities

• Build ingestion and processing paths for duplicates, retries and changing schemas.
• Model identities, resources, activity and relationships with provenance and tenant boundaries.
• Design APIs and queries for investigations and person profiles with controlled data access.
• Develop durable workflows for acquisition, enrichment and investigation, including cancellation and recovery.
• Instrument systems to diagnose failures and optimize latency, capacity and cost.
• Collaborate with research, field engineering and product to turn complex cases into maintainable backend capabilities.

Skills

Backend ownership

TypeScript

SQL performance

Data modelling

Concurrency

Security awareness

Tools

PostgreSQL

ClickHouse

Temporal

Job description

Weve is building workplace security for a world where people and AI agents work across dozens of systems. We connect activity, identity and business context so security teams can investigate risks that no single tool can explain on its own.

One person can appear under different identities across an identity provider, a cloud account and an AI application. Events arrive late, repeat themselves and disagree. We need to preserve the evidence while turning those records into something an investigation can reliably use.

You’ll own backend work from data modelling through production behaviour. Our stack includes TypeScript, PostgreSQL, ClickHouse and Temporal. The interesting work is deciding where state belongs, how work recovers from failure and how the system stays understandable as sources and customers grow.

What you’ll own

• Build ingestion and processing paths that handle duplicates, retries, partial failures and changing vendor schemas without silently losing evidence.
• Model identities, resources, activity and relationships with clear provenance and tenant boundaries.
• Design APIs and queries that make investigations and person profiles responsive without expensive, unbounded data access.
• Develop durable workflows for acquisition, enrichment and investigation, including cancellation, recovery and safe deployment changes.
• Instrument the systems you own so failures can be diagnosed. Improve latency, capacity and cost using observed workloads.
• Work with research, field engineering and product to turn difficult customer cases into maintainable backend capabilities.

What you’ll bring

• Experience owning production backend systems beyond the initial release, including the failures and operational trade-offs that followed.
• Strong TypeScript or comparable backend language experience, relational data modelling and practical SQL performance skills.
• A sound understanding of asynchronous execution, concurrency, idempotency and consistency across service boundaries.
• Care with access control, tenant isolation and sensitive data. Security boundaries should be explicit in your designs.
• The ability to simplify a system, explain your choices and leave another engineer able to operate and change it.

Useful, but not required

ClickHouse, Temporal, high-volume event processing, security data or entity resolution. Experience with every tool in our stack is not required.

What good looks like

• Data is recoverable and traceable when a source or processing step fails.
• Queries and workflows remain predictable as real customer workloads grow.
• New integrations and investigation features need fewer special cases because the underlying model is clearer.

Working here

You’ll work directly with the people building and selling Weve. We expect you to question the brief, make decisions within your area and follow through after something ships. Customer evidence matters more than how convincing an idea sounds in a meeting.

We work remotely and write down our decisions so people can make progress without waiting for everyone to be online. Read more about the team and why we’re building Weve .