Frontend / Product Engineer

Why this role matters

You turn product decisions into interfaces people can use with confidence. Own a focused browser journey from first interaction to completion, including interruptions and recovery. Work closely with design and backend colleagues so that the experience is coherent beyond a successful demo.

A typical working day

• Translate a bounded brief into components, API questions and acceptance checks.
• Build responsive states with design, reproduce problems with QA and explain trade-offs.
• Review implementation, flag dependencies early and leave clear handover notes.

Your responsibilities

• Own responsive React and TypeScript journeys across agreed brands.
• Build reusable UI patterns and test loading, empty, error and permission states.
• Collaborate with design and QA on acceptance criteria and release evidence.
• Communicate progress and dependencies early; agree scope changes before taking on another workstream.

Ownership boundaries

Not the sole backend, infrastructure, product-management or graphic-design owner.

What you bring

• 2+ years of demonstrated frontend work; strong HTML, CSS, JavaScript and TypeScript.
• Accessibility, browser debugging, API contracts and component tests.
• Explain performance and security trade-offs in shipped work.

AI with judgment

Use coding assistants to accelerate implementation while independently reviewing correctness, accessibility and tests.

Evidence and assessment

Two relevant interfaces, your exact contribution, a code sample and one difficult trade-off.

A paid, bounded interface task with loading/error states and a short code walkthrough; no production credentials. Agree payment and a time cap before starting. Use fictional data, no live credentials and no free production work.

How we work

Remote-first with an agreed collaboration window with the Nigeria-based team. Physical sessions require an agreed location, notice and travel arrangements; weekly office attendance is not assumed. Eligibility, engagement type and availability are confirmed individually.

The work you can shape

Practical problems, visible ownership and collaboration across product, design and operations. Together we agree a focused scope and the evidence that will show it is working.

First 30 days

1. Days 1-5: reproduce one agreed journey and map its dependencies and acceptance checks.
2. Days 6-15: implement one bounded improvement with keyboard, loading and recovery tests.
3. Days 16-30: demonstrate the change in an approved test environment, resolve feedback and hand over evidence and remaining risks.