Senior Full Stack Product Engineer, Litta

• 7 or more years building production web applications
• Strong TypeScript/JavaScript across frontend and backend
• Experience with Vue or similar frameworks, Node.js, and cloud or serverless systems
• Experience integrating third-party APIs and working with webhooks
• Comfortable owning systems end-to-end
• Familiar with modern AI tooling in a development workflow

Desirable

• Job title: Full Stack Product Engineer (Mid-Senior)
• Reporting to: Engineering Manager
• Working hours: 40 hours per week (Monday- Friday) 08:00 - 17:00
• Litta is building operational infrastructure for waste collection at scale
• This is not a conventional feature-delivery role
• A large part of the work is improving the systems behind operations
• The focus is on systems that reduce operational overhead, improve reliability, and make the business easier to run as volume grows
• We are hiring a Senior Full Stack `Product` Engineer who is comfortable operating across product, engineering, internal tooling, and automation
• You will be expected to ship end-to-end features, integrate external systems, and use AI-assisted tooling to accelerate delivery and reduce manual work
• We are a small, fast-moving team. Processes are lightweight and not everything will be fully defined or documented
• You need to be comfortable operating in that environment
• You are product-minded and able to make sensible decisions without heavy oversight
• There is no dedicated design function and few layers of management, so you will be expected to translate rough ideas into working solutions
• You take ownership, get up to speed quickly across multiple codebases, and are willing to work across whatever is needed to move things forward
• Build and maintain frontend applications using Vue, React, and TypeScript. Develop and deploy backend services using Node.js, Firebase, and Google Cloud. Design and evolve APIs, data models, and system boundaries
• Integrate third-party systems such as Stripe, HubSpot, Airtable, and Slack. Build and maintain workflow automations using n8n and custom scripts. Work with webhooks, queues, and asynchronous workflows as core primitives
• Replace manual operational processes with reliable, observable systems. Own features end-to-end, from schema and integrations through to UI and deployment
• AI-Augmented Engineering:
• We use LLMs and modern AI tooling to accelerate development, automate workflows, and enhance product capabilities. We identify areas where AI meaningfully reduces cost or improves user experience and implement solutions
• AI is expected to be used deliberately and appropriately. You should understand the code you write, apply sound engineering practices, and not rely on AI as a substitute for technical judgement
• All code, including generated output, is subject to full code review, and we are actively working towards increasing automated test coverage across the codebase
• You will have access to shared team AI tooling, including a Claude Team subscription, and are expected to incorporate these tools effectively into your workflow
• Engineering Quality and Delivery:
• This is not a ticket-driven role. You are expected to take ownership of problems end-to-end rather than just implementing predefined tasks
• Write maintainable, production-grade TypeScript across the stack. Ship continuously via CI/CD using tools such as GitHub Actions
• Monitor, debug, and improve system performance and reliability

• Step 1: Intro Call (45 mins)
• High-level discussion on experience, expectations, and context
• Step 2: Take-home exercise (2 to 3 hours)
• A realistic problem aligned with our stack to evaluate how you structure and ship work
• Step 3: Second stage call & more technical questions (60 mins)
• Delve a bit deeper into who you are, generally go in to more detail plus any high level technical questions and discuss any systems you have built, focusing on decisions, trade-offs, and ownership
• You might be asked how you approach real-world problems such as structuring applications, modelling data, designing APIs, and handling failure modes and edge cases, rather than focusing on recalling syntax or writing code from memory
• Step 4: Offer
• Assuming the earlier stages go well. We’ll reach out over email to discuss alignment, answer any remaining questions, and progress offer discussions