EQWIN

A horse-racing betting application operating in France, originally built by an external vendor. I joined as the first in-house engineer to lead its transition onto an internal team — inheriting the codebase, working alongside the vendor, and standing up the web and mobile streams that would take the product in-house and reduce the business's reliance on (and spend with) the vendor.

Company

EQWIN

Senior Frontend Engineer

Paris (Remote)

Team

  • Mobile (Internal)1
  • Mobile (Vendor)5
  • Backend (Vendor)1
  • Architect1
  • DevOps1
  • Stakeholders & Management3

Technologies

  • React Native
  • TypeScript
  • Expo
  • Firebase
  • REST
  • GraphQL
  • Next.js

Responsibilities

  • Came in as the first internal engineer on the product: inherited the vendor-built codebase solo, worked alongside the existing vendor team, and prepared the ground for an in-house team to take ownership.
  • Owned architectural decisions across web and mobile as the internal side was built out.
  • Redesigned 80+ screens of the mobile application — bringing the bulk of the redesign in-house rather than contracting it back to the vendor.
  • Built the marketing landing page in Next.js as the internal team's first delivered feature, giving the business an analytics-instrumented page it needed for marketing.
  • Interviewed candidates for the internal web and mobile roles, helping assemble strong teams on both streams from a standing start.
  • Partnered with the incoming frontend lead to audit the codebase and produce a refactor and guidelines plan: consolidated four competing state managers into a single approach, cut redundant network requests, and addressed memory usage — establishing the development standards the vendor-only phase had lacked.
  • Stepped into day-to-day frontend-lead responsibilities while that lead onboards — delegating and reviewing work and onboarding new engineers to keep delivery moving.