The Interface Gardener

Weeds grow fast. Good interfaces grow slow. You are the person who trims the unnecessary, waters the intuitive, and repots confusing features into clearer soil. You don't just design screens — you cultivate habits. You'll work alongside our developers to ensure every dropdown, toggle, and hover state feels less like machinery and more like muscle memory. Your tools: empathy, a good eye for alignment, and the courage to delete what you once loved.

🎯 Requirements:

• ✓Has redesigned something small (a calculator, a to-do list, a coffee machine panel) just for the joy of it.
• ✓Can explain the difference between a primary and secondary button without using the word "affordance."
• ✓Has strong feelings about form labels and will defend them kindly.
• ✓Tests interfaces by closing their eyes and clicking — then fixes what broke.
• ✓Thinks "dark mode" is nice, but "calm mode" is better.

The Quiet Optimizer (Performance Gardener)

You hear a millisecond. You feel a memory leak before it shows up in the logs. Your job is not to add features — it's to subtract weight. You'll crawl through our codebase like a minimalist moving through an attic, asking: *Do we really need this? Can this run on a decade-old phone? What happens on 2G?* When our apps feel snappy on bad hardware, that's your victory. You celebrate in silence, with a single commit message: "lighter."

🎯 Requirements:

• ✓Has spent a full afternoon making a function 0.03 seconds faster and felt genuine joy.
• ✓Can read a flame graph without flinching.
• ✓Knows at least two ways to lazy-load something and will teach the team the simpler one.
• ✓Once chose plain text over JSON for a tiny project and was right.
• ✓Speaks C, Rust, or Zig — or is deeply curious about learning one without being dogmatic.

The Kindness Tester (QA with a Heart)

You break things gently. Unlike traditional QA, you don't just find bugs — you diagnose how they feel. Does this crash message blame the user? Does this loading spinner look anxious? You test our software on old laptops, cheap mice, and tired brains. You write bug reports that start with "I noticed something small…" and end with "but no rush at all." Your real job: making sure our tools fail gracefully, never rudely.

🎯 Requirements:

• ✓Has written a bug report that made a developer smile instead of sigh.
• ✓Enjoys clicking the same button 200 times to see if it gets lonely.
• ✓Can reproduce a bug without knowing how to code (and then learn just enough to explain it).
• ✓Believes "works on my machine" is not an answer — it's a beginning.
• ✓Keeps a notebook of tiny annoyances in other people's software. That notebook is your portfolio.