3 Tips for Landing a Web Developer Interview
Вставка
- Опубліковано 17 чер 2024
- 3 Tips For Landing a Web Developer Interview
Timestamps
0:28 - Become a specialist
5:18 - Build your portfolio
10:45 - Get a referral
1) Become a specialist
Companies have specific needs. Their product is built with a certain tech stack and they are going to be looking at someone that is familiar with that tech stack. A common misconception among developers is that you have to learn as many technologies as you can. Don't do that. If you do, then you are becoming a jack of all trades, but a master of none. It's better to focus your skills and become excellent in one or two technologies/stacks and then apply for companies that have that particular need.
It's like if you were applying to a company and that company uses React specifically in their product. You, being a jack of all trades, you know a little bit of React (maybe only 3-6 months worth), but you also know Angular, Vue, Svelte. But you're only able to build a to-do list level applications.
But then another guy applies for the same position and he ONLY knows React. But he's been using React for 5 years and he's built larger full stack applications with it. He knows about server-side React rendering with Next.js. He styles his components using Emotion. He knows all about how to tests his components using React Testing Library. He has a lot more React-specific domain knowledge that will allow him to easily transition and become an asset in the company.
And even though you know a little bit of React, the fact that you know all these other frameworks are inconsequential to the company. The hiring manager is not necessarily going to care about the fact that you know Deno.js and Svelte and Angular etc if this is a React position. Will your knowledge in Deno and Angular and Vue make money for the company if this is a React position? Probably not.
So my advise is to pick a specific tech stack and get REALLY, REALLY good at it. Learn the ins-outs and quirks of the stack. Build real projects with that stack - projects that solve real business solutions. Forget tic-tac-toe, forget todo lists. Try to find a friend or a freelancing client that you can build a website for - a website that addresses a real need.
2) Build your portfolio
You have to be able to demonstrate your skills as a developer so that a hiring manager knows what you're capable of. To demonstrate your skills, you need to build projects that solve real problems.
3) Referrals
Referrals are a good way to get your foot in the door of a company. Referrals can allow you to bypass a stack of applicants by getting someone that already works at the company to put in a good word for you.
You can get referrals through LinkedIn, Twitter, or just by building your social media presence overall. Add some technical recruiters as connections on LinkedIn. They oftentimes post job openings about positions they are hiring for. Start making UA-cam videos that demonstrate your technical ability. Your channel can be used as 'social proof' for a potential hiring manager that finds it.
📕 Expand your JavaScript knowledge by downloading my latest e-books!
payhip.com/DevSage
🤖 Join me on Discord
/ discord
👕 DevSage Merchandise
cottonbureau.com/people/devsage
good tips .thanks, man. I guess I am the first viewer of this one.
Thanks!
Btw those auto generated chapters are super cool.
Thanks for the tip. Very helpful👍 .
You're welcome!
Great channel, keep up the good work man!
I appreciate that!
Hey, did you ever go over how you achieved that particle self-portrait effect on your portfolio site? I found it really cool and would love learning how to build things like that.
I think the reason why there is the misconception that you have to know as many technologies as possible, is because sometimes when you browse through job openings, you'll quite often stumble upon those where they expect experience within a ridiculous amount of technologies. Personally, I quite rarely find ones where they expect you to "just" know React and Node or something like that, quite often they have this long list of requirements, where it's just painfully obvious that it's an HR person, who is just listing the technologies that the person has heard of. That's at least what made me think that I should learn a new stack as often as possible back when I was job hunting.
Good advice, and makes sense. Otherwise where does the rabbit hole end?
good advice. for me, i recommend learning vanilla JS, c-sharp and sql.