Frontend Engineer: Traduire Les Rêves Des Designers En Code

À Propos

On cherche un Frontend Engineer pour transformer nos designs en réalité.

On a des designers qui créent de beaux prototypes.

Tu vas les transformer en code qui fonctionne sur le vrai internet.

Responsabilités

• Implement UI from designs (Figma → React)
• Performance optimization (make it load fast)
• Cross-browser testing (it works on Chrome, what about Firefox?)
• Accessibility (make sure everyone can use it)
• Code quality (reviews, testing)
• Collaborate with design (discuss tradeoffs)

Profil Recherché

• 3-4 ans frontend experience
• Strong React/Vue/Angular (pick one, be good)
• CSS/HTML fundamentals (don't just use Tailwind)
• Performance mindset (care about load times)
• Design literacy (understand what designers are trying to do)

Ce Qu'On Veut

"We need someone who can bring our designs to life!"

Reality:
- Designs are often unrealistic for web
- You'll spend 40% of time explaining why the design isn't feasible
- 40% implementing the compromised version
- 20% actually enjoying the work

La Comp

Salaire: 47k€
Equity: 0.12%
Benefits: Standard + maybe a good monitor

Le Jour Typique

• 9h-10h: Check PR reviews (from yesterday)
• 10h-12h: Implement a new component
• 12h-13h: Lunch (debug a CSS issue while eating)
• 13h-15h: Meeting with designer (discuss implementation)
• 15h-17h: Fix bugs from yesterday's release
• 17h-18h: Write tests for the component

The Designer-Engineer Tension

Designer: "This animation should take 800ms and feel bouncy"

You: "That's nice. Here's the web version that's 200ms flat because browsers don't work that way"

Designer: "But the prototype..."

You: "Yeah, Figma isn't the web"

Common Frustrations

Frustration 1: The Design Spec Mismatch
- Design looks perfect in Figma
- Real web has constraints (screen sizes, performance, browser quirks)
- You implement, it's close but not exact
- Designer: "It's not pixel-perfect"
- You: "Welcome to web development"

Frustration 2: The Scope Creep
- Original spec: "Here's the button"
- Week 2: "Can we add animations?"
- Week 3: "Let's add a hover state"
- Week 4: "What if we made it interactive?"
- Button is now 3x the scope

Frustration 3: The Mobile Disaster
- Design: Looks great on desktop
- Mobile: It's a mess
- Designer doesn't use mobile view
- You have to make it work
- Takes twice as long

The Reality

Frontend is harder than it looks.

People think: "Just put it in React"

Reality: Browser inconsistencies, performance, accessibility, mobile, testing...

It's complex.

After 18 Months

Best Case:
- You've built a great design system
- Code is clean and performant
- Designer and you work seamlessly
- Team respects your technical input

Realistic Case:
- You've implemented most designs (with compromises)
- There's some technical debt
- Designer-engineer relationship is OK (but tense sometimes)
- You enjoy parts of the work

Worst Case:
- You're constantly frustrated
- Designer-engineer tensions are high
- Code quality suffers
- You burn out

The Skills Gap

Designers think in visual/UX.

Engineers think in code/architecture.

These don't always align.

Someone has to be the translator.

Usually that's you.

The Advice

If you like: Design, UX, implementing beautiful things:
Maybe yes.

If you want: To always follow the spec exactly:
No.

Frontend is about making the best possible web experience within constraints.

Not about pixel perfection.

That requires compromise.

And diplomacy.

Welcome to the job.