The role

This is not generic frontend implementation. The expectation is that you can preserve rhythm, hierarchy, motion, and responsiveness while still building maintainable code.

You will work across marketing surfaces, admin experiences, and productized internal tools.

You should be comfortable moving from a highly art-directed landing page to a dense operational interface without losing clarity in either environment.

Responsibilities

• Implement polished, responsive interfaces in Next.js and TypeScript.
• Collaborate directly with design to keep visual decisions intact through build.
• Improve shared UI patterns without drifting into boilerplate.
• Contribute to admin and workflow surfaces that support the business behind the public experience.
• Spot weak interaction patterns and propose stronger implementations before they become defaults.
• Own frontend quality across layout, accessibility, responsiveness, and interaction behavior.

Requirements

• Strong frontend engineering fundamentals with a clear eye for design.
• Experience with React, Next.js, CSS architecture, and production delivery.
• Ability to debug layout, interaction, and rendering issues without guesswork.
• Comfort moving between marketing pages and application UI.
• Ability to work effectively with existing systems rather than rewriting by instinct.
• Strong communication about implementation tradeoffs and technical constraints.

Why Redstart

• Direct ownership of user-facing work.
• Close collaboration with design and strategy instead of ticket-only execution.
• Room to influence frontend standards, not just follow them.
• Broad exposure to both public-facing and internal product surfaces.

How to apply

Send examples that show both visual quality and implementation quality.

We care about how the interface behaves, not just how it screenshots.

A brief explanation of one difficult frontend tradeoff you handled well will help.