Why are you interested in working at Giving What We Can?

I'm interested in working for GWWC for three reasons:

First, the older I get and the more I travel, the more I realize just how lucky we are in WEIRD (Western, Educated, Industrialized, Rich, and Democratic) countries. Most of us live in an abundance of goods and money, yet it's clear that these do not necessarily make us happier. Meanwhile, there are many important causes and people are born into very different circumstances, creating a significant imbalance and untapped potential for doing good. Hence, the idea behind GWWC resonates with me deeply.
Secondly, I'm not the most scientifically inclined person. I prefer hands-on work and have a passion for simple, effective design and communication. At times, this has frustrated me within the EA community because much of the communication, design (if done at all), and marketing is, in my eyes, overly complicated, technical, and not accessible to everyday people. However, GWWC has always stood out to me as an EA meta-organization that understands this. For me, that's the ideal EA organization—one that combines rigorous, rational research with engaging and approachable communication to maximize the impact it can have.
Third, I see very good fit with my skillset and experience.

Why would you be a good fit for this Web Design role at Giving What We Can?

Marieke from EA Netherlands sent me this job application, and I couldn't help but think, "This fits me like a glove!"

I'm primarly a UI/UX designer, but I love to code. I picked up coding years ago to bridge the gap between design and the actual implementation of websites and projects.
React and NextJS—which I noticed you use as well—are exactly the stack that I use for my own work. I love a good design system and reusable components, and TailwindCSS is a fantastic choice for building these.
I'm comfortable taking responsibility and leading the design process from start to finish.
Some additional skills and experience that might be releavnt: I'm a good facilitator, I have a good grasp of SEO and copywriting, and have hands-on experience with user interviews, A/B testing, and other user research techniques
I have shipped many websites. My largest project being the Facilitator School. I build the brand, website and all the resources libraries from scratch. Now, the website is well-known in the facilitation community with around 200,000 annual visitors.
I'm a big fan of Basecamp and have myself implemented a 6-week working cycle in my last two companies. (Not exactly Shape Up, but quite similiar!)
I've been part of the EA community for five years. I helped launch EA Utrecht and the EA Netherlands online community, and I currently work with EA Netherlands one day a week to rebuild their website (early WIP here), also using Next.js and React.

My core belief is that good design comes from continuous learning and iteration.
It's difficult to create the perfect design right away, because in the end the user is the judge. Often, users don't even know what they want themselves.
Therefore, my design process is very hands-on, practical, and user-centric.
I'm not a fan of building large Figma boards in the dark for weeks or months at a time.
For small, non-critical projects, I value getting the design into users' hands quickly.
I then iterate on the design over time with real user data and feedback, while documenting learnings for future projects.
Example: At Facilitator School, I built a Team Plan calculator for our Team Plan page. I designed and developed the first version in half a day, and then continuously improved it after reviewing user recordings.
For larger projects, it's important to understand the problem space, the user's perspective, and the design scope before designing.
The risk is too large to take the wrong path and build something that misses the point.
To tackle large projects, I'm a fan of using a structured approach like working in cycles (à la Shape Up) or running workshops to create meaningful time for making real progress.
Example: Before COVID, I worked with Mr. Spex, a German online optician, to validate an Augmented Reality try-on feature for their online shop. I facilitated a one-week Design Sprint workshop, designed a prototype, and ran tests with users.

Because of the peak-end rule, I see the "Thank You" page as a key moment for users
Before meeting with the engineer, I would gather insights from pledger surveys, our web analytic tools, and by speaking with recent pledgers about their experience, if possible.
I would collect all findings in a visual tool like Miro and invite others on the team to contribute their thoughts and feedback
Together with the software engineer, I would discuss the current implementation, explore the constraints, and look for opportunities to combine design and development in a unique way.
Example of a unique idea: What if we show the user an interactive timelapse of their estimated impact with various charities over the next 5, 10, 20, and 40 years of their pledge? Would this reinforce their decision? Would they want to share this as well on social media?
Combining everything I've learned, I would create prototypes and designs for internal feedback and, potentially, to test with users.
Key aspects I would incorporate are: Personalization, delightful interaction, and strong copywriting.
Once the direction is clear, I would circle back with the software engineer to discuss the implementation.
In the implementation, I could take up the task of building the reusable visual components in TailwindCSS (aligned with our design system) and hand them over to the software engineer to tie the componant logic together.