Modo Energy - Frontend Engineer (AI/Platform)

Remote - London3w ago

Remote Mid EMEA Frontend Engineer Jest Git Yarn Cypress Playwright

Requirements

• The Essentials • 3+ years of professional frontend development experience, with excellent TypeScript, React, and Next.js. • Experience with MUI or a similar component library. • Solid testing practice with frameworks like Jest and Cypress or Playwright. • Proficient with Git, Docker, and CI/CD workflows, and familiar with monorepo structures and tools (Turborepo, Yarn Workspaces, or similar). • Fluent with AI-assisted development tools (Cursor, Claude Code, GitHub Copilot, or similar). We write a lot of code this way. • An eye for design (UI/UX): you can build polished, aesthetically pleasing interfaces, not just functional ones. • A fast learner with good judgement, comfortable making calls on component design and what's good enough to ship, and genuinely energized by picking up unfamiliar tools, stacks, or problem areas rather than staying in one lane. • Comfortable in a small, fast-moving team where you're expected to figure things out, make trade-offs, and ship, with real autonomy over how. • Start-up or scale-up experience. • Familiarity with Python. • Experience with energy markets. • Equal Opportunity • Equal Opportunity

Responsibilities

• Help shape the technical direction of our frontend monorepo so it scales with the team and the product. • Design and build components in our internal UI library, built on MUI, that the rest of the team can build on. • Build and improve high-performance, low-latency interfaces that hold up under real, live market data. • Write well-tested code (Jest, Cypress, or Playwright) and contribute to how the team reviews and documents its work. • Split your time between shipping new features and keeping things healthy: maintenance, performance, and production issues are a normal, expected part of the job, not an interruption to it. • Work directly with design and with the people who understand the domain (energy analysts, data scientists) to bridge the gap between design and engineering. • Cross into the backend and infrastructure basics behind your own features when the team needs it: an API change, a deployment fix, a bit of the pipeline behind the data you're rendering.