The Role
You’ll be building across the full product surface — frontend architecture, backend services, data layer, and AI integrations — with ownership over technical design decisions, not just implementation. The expectation is that you ship production-ready code and have opinions about how systems should be built. Six years of experience means you’ve seen what breaks at scale and you design accordingly.
About the Product
The product is an email security platform focused on detecting and neutralising phishing and email-based threats in real time. The product sits in the inbox — processing, classifying, and responding to threats at scale using a combination of AI models and human analyst signals. The backend handles complex data workflows across relational and in-memory stores; the frontend is a rich, engineered interface, not a thin client. AI models and agentic patterns are embedded in the product, not prototyped on a side branch.
Technology Stack: React on the frontend, Python on the backend, PostgreSQL and Redis for data. The team works with AI models and agentic tooling as core product components, not experiments. Django, Flask, and FastAPI are in the advantage column — the Python backend is established, not greenfield. Event-driven architecture with Kafka or RabbitMQ is in scope for candidates who’ve worked in that space.
What You’ll Be Doing
- Design and implement full-stack features end-to-end — from frontend components through API contracts to data models
- Own frontend architecture decisions: how the UI is structured, how state is managed, how it scales as the product grows
- Drive technical design for backend systems with scalability and reliability as hard constraints
- Build and maintain data solutions on PostgreSQL and Redis — schema design, query optimisation, caching strategy
- Integrate and work with production AI models and agentic workflows as first-class product components
- Write code that’s tested, observable, and maintainable — not code that ships and gets forgotten
- Contribute to service architecture decisions: how components communicate, how they fail gracefully
What We Expect
Must-have
- 6+ years of full-stack development experience with React and Python
- Strong command of HTML, CSS, JavaScript, and DOM fundamentals — not framework-dependent, genuinely understands the platform
- RESTful API design and implementation, both building and consuming
- Hands-on production experience with PostgreSQL and Redis
- Experience designing frontend software architecture — not just building components inside someone else’s structure
- Track record of driving technical design for scalable systems
- Hands-on experience working with AI models and agentic development patterns in production
Nice to have
- Django, Flask, or FastAPI
- AWS or equivalent cloud platform experience
- Microservices and event-driven architecture
- Message brokers: Kafka or RabbitMQ
Why This Role Is Worth Your Time
- Full-stack ownership here is genuine — you’re making frontend architecture decisions and backend design calls on the same product, not switching contexts between two separate teams
- AI and agentic development are already in production, which means you’re working with these systems at real constraints, not building demo integrations
- The problem space involves scale and data complexity that makes the engineering non-trivial — PostgreSQL and Redis at volume, systems designed to not break
- Technical design authority is part of the role from day one — the expectation is that you shape how things are built, not just execute what’s been decided
