Your next React Engineer

A Cover-Letter Experience
by Sean DeRue

I want to be a part of Webstacks' next success stories. I made this site to prove it.

This site was made with love in just 23 days, using some of Webstack's favorite tools. Please enjoy using it as a tangible example of what I can bring to the table as your next Front End Engineer.


Est reading time: 4.8 mins

Press Laptop To Begin

Cover Letter Experience

This website is a tangible example of what I can bring to the table whilst showing my excitement for the Webstacks React Engineer role.

The experience was built in only 23 days with the tools & tech you love:

  • React for extensible components & state management

  • Next.js for static rendering & SEO friendliness

  • DatoCMS for headless content hydration

  • GraphQL for backend communication

  • Vercel for cloud-based hosting

  • React-Three/Fiber for unique 3D experience

  • Sass for CSS management

You're welcome to examine the codebase here, but I'd welcome the opportunity to discuss it over an interview 😉.

Content hydrated statically from DatoCMS's GraphQL endpoint
01

Plan

I'm an industrious organization nerd at heart and an out-of-the-box thinker.

Pair that with a T-shaped skillset, and you've got someone who's always prepared for meetings, ready to meet deadlines, and always thinking of new ways to equip the team and clients for success.

Crossfunctional collaboration

I know the team consists of...

  • UX designers

  • Backend Engineers

  • SEO Analysts

  • Marketing Technologists

Since I've dipped my toes in each of those roles, I'll be ready to support my team seamlessly.

From backlog grooming to product shipping, I'm eager to Sprint alongside some of the best talent in the tech space.

Prepared and communicative

Those who've worked with me in the past would agree--I love distilling complex concepts into understandable action plans with diagrams, loom videos, and presentations that include follow-up meeting notes to boot.

Content hydrated statically from DatoCMS's GraphQL endpoint
02

Design

I've always been a visual person. But, getting my Bachelor's in Marketing from Purdue University helped me understand how important it is to consider the user experience every step of the way.

UX-oriented thinker

I believe there's a canyon of difference between a product that works and a product that's enjoyable to use.

That's why I love to bring excellent Figma designs to life with attention to every detail.

Example:

When I was designing my budgeting app, I designed the fund's balance meter as an angular gradient within a circular progress meter...only to find out that was a lot more difficult to do in React Native than expected... especially when animating it.

Because I believe that design detail was an important one, I workshopped ways I could make it come to life. One option involved combining multiple primitive linear gradients into one, but animating those would be a challenge throughout the project. I ended up using a more extensible solution, through the use of shaders.

I love the way it came out and I'm glad I didn't cut corners where others may have compromised on the design.

Content hydrated statically from DatoCMS's GraphQL endpoint
03

Build

The technical requirements for this role match perfectly with my proficiencies.

Technical fit:

In my previous experience, I have built numerous projects using a variety of tools that Webstacks values. React, Typescript, AWS, Next.js, Headless CMS, GraphQL, Sass, and Node.js just to name a few.

I am quite familiar with Git and GitHub for version control in a team environment. While I worked in the Slipchenko Research Lab at Purdue, I gained experience working in a CI/CD team environment while we used Java to build a GUI for a chemical process visualizer.

Eager to learn more:

Even though I've racked up plenty of experience with the tools that this role calls for, I'd welcome any opportunity to develop with new tools and techniques at Webstacks.

Code organization habits

And rest assured that my organization-nerd habits carry over into my codebases. I prefer verbose naming habits, frequent comments, and clean file hierarchies to eliminate confusion about what that code does or how it fits into the project's overall architecture.

Content hydrated statically from DatoCMS's GraphQL endpoint
04

Optimize

I agree wholeheartedly with the sentiment that a website is never finished.

Well-optimized code & conversions are the lifeblood of a digital product. As a former copywriter, I know that even the smallest of changes to a site can make a massive conversion difference.

Data-driven growth

Data-validated tests are at the heart of every well-converting site, and I'd be very eager to join a company like Webstacks who knows this well enough to put it into their everyday workflow.

Eager to learn

This is the reason I approach code reviews with an open and constructive mentality. Ultimately, it's all about helping the team, client, & end-user reach their full potential. Being hungry & humble has given me the chance to grow so much as a developer since I started my programming journey in November of 2021.

That growth is reflected in my published projects and I'm proud of the velocity of my engineering growth. I have no plans of slowing that growth down.

In conclusion...

All-in-all, I'm confident that I'm a strong fit for this role.

If you were to hire me, I will be the type of employee who will embrace change positively, be a great role model for the company, and take ownership of my development.

I sincerely thank you for taking the time to consider my application.

Content hydrated statically from DatoCMS's GraphQL endpoint

Cover Letter Experience

This website is a tangible example of what I can bring to the table whilst showing my excitement for the Webstacks React Engineer role.

The experience was built in only 23 days with the tools & tech you love:

  • React for extensible components & state management

  • Next.js for static rendering & SEO friendliness

  • DatoCMS for headless content hydration

  • GraphQL for backend communication

  • Vercel for cloud-based hosting

  • React-Three/Fiber for unique 3D experience

  • Sass for CSS management

You're welcome to examine the codebase here, but I'd welcome the opportunity to discuss it over an interview 😉.

02

Design

I've always been a visual person. But, getting my Bachelor's in Marketing from Purdue University helped me understand how important it is to consider the user experience every step of the way.

UX-oriented thinker

I believe there's a canyon of difference between a product that works and a product that's enjoyable to use.

That's why I love to bring excellent Figma designs to life with attention to every detail.

Example:

When I was designing my budgeting app, I designed the fund's balance meter as an angular gradient within a circular progress meter...only to find out that was a lot more difficult to do in React Native than expected... especially when animating it.

Because I believe that design detail was an important one, I workshopped ways I could make it come to life. One option involved combining multiple primitive linear gradients into one, but animating those would be a challenge throughout the project. I ended up using a more extensible solution, through the use of shaders.

I love the way it came out and I'm glad I didn't cut corners where others may have compromised on the design.

Content hydrated statically from DatoCMS's GraphQL endpoint
04

Optimize

I agree wholeheartedly with the sentiment that a website is never finished.

Well-optimized code & conversions are the lifeblood of a digital product. As a former copywriter, I know that even the smallest of changes to a site can make a massive conversion difference.

Data-driven growth

Data-validated tests are at the heart of every well-converting site, and I'd be very eager to join a company like Webstacks who knows this well enough to put it into their everyday workflow.

Eager to learn

This is the reason I approach code reviews with an open and constructive mentality. Ultimately, it's all about helping the team, client, & end-user reach their full potential. Being hungry & humble has given me the chance to grow so much as a developer since I started my programming journey in November of 2021.

That growth is reflected in my published projects and I'm proud of the velocity of my engineering growth. I have no plans of slowing that growth down.

In conclusion...

All-in-all, I'm confident that I'm a strong fit for this role.

If you were to hire me, I will be the type of employee who will embrace change positively, be a great role model for the company, and take ownership of my development.

I sincerely thank you for taking the time to consider my application.

Content hydrated statically from DatoCMS's GraphQL endpoint
01

Plan

I'm an industrious organization nerd at heart and an out-of-the-box thinker.

Pair that with a T-shaped skillset, and you've got someone who's always prepared for meetings, ready to meet deadlines, and always thinking of new ways to equip the team and clients for success.

Crossfunctional collaboration

I know the team consists of...

  • UX designers

  • Backend Engineers

  • SEO Analysts

  • Marketing Technologists

Since I've dipped my toes in each of those roles, I'll be ready to support my team seamlessly.

From backlog grooming to product shipping, I'm eager to Sprint alongside some of the best talent in the tech space.

Prepared and communicative

Those who've worked with me in the past would agree--I love distilling complex concepts into understandable action plans with diagrams, loom videos, and presentations that include follow-up meeting notes to boot.

Content hydrated statically from DatoCMS's GraphQL endpoint
03

Build

The technical requirements for this role match perfectly with my proficiencies.

Technical fit:

In my previous experience, I have built numerous projects using a variety of tools that Webstacks values. React, Typescript, AWS, Next.js, Headless CMS, GraphQL, Sass, and Node.js just to name a few.

I am quite familiar with Git and GitHub for version control in a team environment. While I worked in the Slipchenko Research Lab at Purdue, I gained experience working in a CI/CD team environment while we used Java to build a GUI for a chemical process visualizer.

Eager to learn more:

Even though I've racked up plenty of experience with the tools that this role calls for, I'd welcome any opportunity to develop with new tools and techniques at Webstacks.

Code organization habits

And rest assured that my organization-nerd habits carry over into my codebases. I prefer verbose naming habits, frequent comments, and clean file hierarchies to eliminate confusion about what that code does or how it fits into the project's overall architecture.

Content hydrated statically from DatoCMS's GraphQL endpoint