À Propos

On cherche un QA Engineer pour tester notre produit avant qu'on le livre aux clients.

Tu vas: Tester, find bugs, report issues.

C'est pas glamorous. Mais c'est critique.

Responsabilités

Manual testing (click through the app, find issues)
Test automation (write scripts to test automatically)
Bug reporting (clear, detailed reports)
Regression testing (make sure we didn't break anything)
Performance testing (how fast does it load?)
User experience testing (does it feel good to use?)

Profil Recherché

2-3 ans QA experience
Strong attention to detail
Testing mindset (you think like a user, not a dev)
Tech skills (basic scripting, SQL, understanding of architecture)
Communication (explain issues clearly)

Ce Qu'On Veut

"We need quality!"

Reality:
- We need quality, but not at the cost of speed
- You'll be pressured to test faster
- You'll miss bugs
- Bugs will reach customers
- You'll get blamed

La Comp

Salaire: 40k€
Equity: 0.08%
Benefits: Standard

Le Jour Typique

9h-10h: Review test cases from yesterday
10h-12h: Manual testing (go through the new feature, find issues)
12h-13h: Lunch while documenting bugs
13h-15h: Test automation (write or update test scripts)
15h-17h: Regression testing (make sure old stuff still works)
17h-18h: Report on what broke

The Frustration

You find: "When you click this button, it shows an error"

Dev says: "That's not a real use case"

You: "But a user can do this"

Dev: "Yeah but they shouldn't"

You: "But they CAN"

Dev: "Not my problem"

The Numbers

You test for 2 weeks.

Find: 45 bugs

Dev team fixes: 30 bugs

Marked as "won't fix": 10 bugs

Still broken at launch: 5 bugs

Users discover: 3 bugs not in your report (oops)

The Time Pressure

Release date: Friday

Today: Thursday

You just found: Major bug

Dev: "We don't have time to fix it"

You: "But it's a blocker!"

Dev: "Ship it. We'll fix it in the next release"

(They won't. Users will complain. Your report wasn't wrong.)

The Relationship

Devs view QA as: The bottleneck

You view QA as: The quality gate

Often, you don't get along.

Devs want to ship. You want to find bugs.

These are sometimes opposing goals.

Common Bugs You'll Find

"When I do X then Y then Z, it crashes"
"On mobile, this button is hidden"
"The payment form doesn't work with a hyphen in the address"
"After 100 clicks, the performance degrades"

None of these are obvious in normal testing.

But they matter to users.

After 18 Months

Best Case:
- You've built a solid test suite
- Quality has improved
- Bugs are caught early
- Dev team respects your input

Realistic Case:
- You've done manual and some automation
- Some bugs slip through
- Quality is "OK"
- Dev team respects you (sometimes)

Worst Case:
- You're constantly understaffed
- Bugs slip through constantly
- You get blamed
- Devs ignore your reports
- You're frustrated

Why It's Hard

QA is about preventing problems.

But in a fast-moving startup, prevention is secondary to speed.

So you're often overridden.

But when something breaks with customers... you get blamed.

It's a tough position.

The Advice

If you like: Detail work, user empathy, process:
Maybe yes.

If you want: Respect from the team:
No.

QA is often undervalued.

You're the person who finds problems.

People don't love that.

But every shipped bug could have been caught.

So... someone's gotta do it.

QA Engineer: Trouver Les Bugs Que Les Devs Ont Laissés