THREE Things You Can Do Today to Become the Highest Paying Front-end Dev

Considering that this year officially marks 20 years that I've been in the industry, I want to take the year to reflect, look back on my experiences while also sharing the lessons and insights that I've gained/earned along the way.

While some folks that are at the top of their game might feel compelled to withold certain information (usually worried that others might take it and end up doing better), I've come to learn that it is my passion for sharing, observing and listening to other devs that has helped me to continue growing and becoming better along the way. It's just more fulfilling and fun to grow alongside others than to be alone in my own journey.

In a recent article that I've published on LinkedIn, I shared about my most recent observations and how the industry has been shifting it's perspective on hiring top talents across multiple fields. Unlike 20 years ago when I first started my career, today, the pay gap has finally widen up enough to help differentiate between the acceptable hires and the creme de la creme (usually the top 10%).

So, I imagine your very first question might sound something like, "Is it possible for me to be among that top 10% in my field/role?". And your follow-up question might sound something like, "What can I do to get myself there?"

The answer to your first question is actually a simple, "Yes."

In fact, looking back now, taking into consideration both my own journey as well as the journey of others that I've helped along the way, it is clear to me that anybody can be among that top 10% in the field. But first, you have got to want it badly enough.

So, without any delay, I'll get into the TOP THREE things that you can start doing today that will help you to get to that goal of becoming one of the highest paying front-end developers in your field.

1. Pick a Stack (or Two)

When I first started my career in 2005, there was no such thing as a stack. Developers like myself are usually considered a generalist that is versatile enough to learn on-the-job, and also do anything that may be required (i.e. backend and front-end).

But it wasn't until the 2010s that I finally started to recognize the value of having different technology stacks. This separation of specific skills in their related stacks made it possible for devs like myself to focus in on an area that we know we are best at.

The thing about picking a stack is not about making a random choice, neither is it about finding one and just sticking with it.

Technology stacks since the 2010s have evolved and grown. Today, we have multiple stacks that we can choose from, like .NET, MERN, MEAN, LAMP, etc. I'll be humble enough to admit that I may have missed something. But you get the idea.

Before any of us can decide on which stack to focus on, we need to first give ourselves the opportunity to experience using it, coding with it. It is only be gaining some experience with those different stacks that we can truly discover which ones we're best at.

Once you understand and know clearly the stack(s) you are most good at, you can then make a final decision.

In my experience, it is often a misconception that developers should only be specialized in a single stack. While that might make you the best at that stack, it won't increase your overall value as a front-end developer. I highly recommend having a primary stack (best at), and a secondary one (very good at).

2. Maintaining a Portfolio.

After speaking to many front-end developers as a mentor/coach, I've observed a common misconception among front-end developers. They would often assume that it is designers that need a portfolio. But that is actually not true. I do believe that front-end developers do need a portfolio if their own as well.

My first ever portfolio consists of a 10-page word document with screenshots of my past works. I also included code snippets and explanations of the challenges that I was trying to solve. I would also showcase a problem, and then explain my solution. If designers were artists, then the painting itself is their works, and for us front-end developers, our work is the sculpture, or that furniture that we had handcrafted.

Having a great portfolio as a front-end developer is about showcasing our critical thinking and problem solving skills. One of the best things that you should aim to showcase in your portfolios, are the unique problems/solutions that you have helped to solve & build. Pick out 3 to 5 of your best works.

3. Know Your Unique Value Proposition

In today's context, it's no longer just good enough to be extremely proficient in a particular set of skills that you're specializing in. In order to become one of the highest paying front-end developers, you need to be able to showcase your unique value proposition. What makes you shine out and differentiates you from your peers?

Speaking for myself, I've discovered over the years that I have a unique value in areas like UX, Agile, Testing. While they are not areas of my greatest strength, it is my knowledge and proficiency in those areas that helps to add-value back to my work as a front-end developer. It has allowed me to have an edge over other developers in the same line of work. It is the very same unique value proposition that enabled me to earn more than any other freelancers back in the early 2010s. While most developers were still fighting over sub-10K opportunities, I was already making my first 5-figure income as a freelancer.

Final Thoughts

This journey/road to becoming the best in the field hasn't been easy too. Trying to standout and be different 20 years ago is often seen as weird, or unacceptable. For the most part, I have been alone and on my own for a long time. I had to learn how to view myself differently (independent of other people's opinions about me, or what I can do). But it is also because of my willingness to be different that would eventually pay off.

Looking back now, part of the reason why I feel so passionately about mentoring and coaching other devs is because I understood how difficult it was for me to get to where I wanted to be. I wished I had help, or at least someone to guide me along the way. I didn't. So, instead of taking a few years to reach a particular goal, I had to take a much longer time. I had to be willing to experiment, make mistakes and fail over and over and over again. Looking back now, I think it is those same mistakes and failures that eventually helped me to become who I am today.

Don't be afraid to make your own mistakes. That's the final lesson and tip I can provide you today. Yes, it helps a lot to have someone to guide us, so we can learn from their mistakes and failures. It is such guidance that will help us to avoid and prevent potential pitfalls, saving us time, energy and sometimes even money. But don't let it become an excuse to avoid failure or making your own mistakes. At the end of the day, I think it is important for us to take some risks, try new solutions, work on novel problems. Yes, there is a risk you might fail at it. But until you've tried, how can you know whether or not you would succeed or fail, right? So, don't be afraid to try.

Paid Coaching & Mentoring for Devs

I offer paid coaching and mentoring services to devs. It's something that I have been doing since early 2015. Since then, I have coached and mentor hundreds of developers across the Asia Pacific region. This has been extremely fulfilling and it is something I intend to continue doing for as long as I can. If you are interested, or know someone that is, you can drop me an email at d2d.weizhi@gmail.com