Frontend Engineer

Context & Vision

In 2026, writing code is no longer the primary bottleneck; managing its complexity and ensuring its reliability is. We are building a highly resilient advertising platform with a very lean, senior internal team, and we intend to keep it that way.

To achieve scale without the overhead of a large engineering department, we rely on an AI-first development paradigm and a philosophy borrowed from the best large-scale open-source projects. Our code is not public, but our governance is theirs: asynchronous communication, exhaustive written documentation, explicit rules, and uncompromising quality gates. It is the only way a small team of humans and AI agents ships serious systems without accumulating technical debt.

This role owns the entire product surface: the console through which advertisers and agencies run their campaigns.

The Role

You will own the frontend of the platform end to end — the advertiser and agency console where campaigns, audiences, creatives and reports come to life. This is the most visible part of the build and, today, the least finished; you will have real ownership and a large surface to shape.

1. The Advertiser & Agency Console.** Build and own the product UI: campaign and line-item management, inventory, creative assets, reporting dashboards, account and admin modules, and the conversational agent interface. You are responsible for how the product feels to use.

2. A Typed, Contract-First Client.** Our frontend consumes the backend through a typed, contract-first client. You keep the contract tight: no drift between what the backend promises and what the UI assumes.

3. A Real Design System.** The product is standardising on a proper design system. You will own its implementation, keep components consistent, accessible and internationalised (FR / EN / AR), and work with the studio on the visual direction rather than reinventing it per screen.

4. AI-First Delivery & Governance.** We expect AI to write most of the code; you are the editor, not the typist. You specify work as explicit, self-sufficient issues, direct agentic tooling to implement, and gatekeep every diff. Components, patterns and decisions are documented. If it is not written down, it does not exist.

The Tech Stack

• Core: modern React, TypeScript.
• UI:a component library and a shared design system; data visualisation. -State & Data: server-state and client-state tooling, typed API clients.
• Testing: end-to-end and unit testing.
• i18n: multi-language (FR / EN / AR).
• Cloud: Google Cloud Platform.

Profile & Requirements

We are looking for a senior frontend engineer who owns a product surface with taste and rigour, and who is comfortable in a lean, high-quality, AI-first environment. This role is not suited to someone who wants a narrow slice of screens inside a large team.

• 4+ years building and shipping production React applications, with real ownership of a non-trivial product surface.
• Deep TypeScript, modern React, and a component-library-based UI used at scale.
• Experience with server-state tooling and typed API consumption.
• A real testing habit (end-to-end and unit) and attention to accessibility and internationalisation.

Core Competencies & Mindset

-AI Development Lifecycle: genuine proficiency editing and validating AI-produced code, and turning ambiguous product goals into specifications an agent can execute.

• Product Sense & Craft: you care how it feels, not only that it renders. Hierarchy, states, and consistency are not afterthoughts.
• Uncompromising Quality: a focus on performance, correctness and maintainability across a large surface, not just the happy path.
• Written & Asynchronous: exceptional written communication; effective in a distributed, async environment (Paris timezone +/- 3h). You document your components and decisions and do not wait to be asked.