🧵The job market for junior devs is not great these days (to put it mildly), so here are a few tips from recruiters, hiring managers, and my own experience about how to get your first job as a developer: #CodeNewbie#DEVCommunity
1. Check multiple job boards, not only LinkedIn - junior positions are easier to fill, so there's no need for companies to advertise them everywhere, they'll get a lot of candidates anyway
2. Check out careers page of larger companies around you, and sign up for updates if they have such option. Careers page is where the job offers appear first, so be the first one to know about them
3. Don't worry about meeting all requirements in the job description, as long as you meet 50% or even 30%, give it a go. I've never met 100% requirements and I've been working in this industry for more than a decade
4. If you see mid-level job opportunity, you can reach out directly to the company and see if they're open to hiring a junior dev. Small companies are not so strict, often resumes are checked by co-founders, use that (you can move to a larger company later, it'll be much easier!)
5. Remember that all you need is just 1 offer. It doesn't matter whether you get 1 offer after 5 applications or after 500 applications, 1 job offer is all that you need in the beginning, that's your goal
6. Attend dev-related/career-related events. they'll often feel like a waste of time, but here's the thing: sometimes you'll meet people who can help you there. It might be a recruiter that'll send your resume to a company, maybe someone will suggest changes in your resume etc.
7. Which brings me to the dreaded networking - having a real professional network will have a huge impact on your career, so start early. Meet people, chat with people, follow up with people. It might not help you directly now, but it's a long-term game
8. Harsh truth: your resume is almost the same as 95% of other resumes, and that's normal. But you can tailor it to the company you're applying - send more colorful and informal version to small company, send more stiff and professional version to corpo
9. Portfolio: not many people look at these. You should build projects to gain more skills, but from hiring perspective 1 creative and polished project is worth more than 10 React applications built by following tutorials step by step
10. We're getting to some tense stuff, pay attention: finding your first job might take a long time - whether it's first job in tech, first job in a new domain, first job in a new country etc. you will have disadvantage, which means you'll need to put more effort and wait longer
11. It's easy to burn out, it's easy to get depressed, it's easy to start doubting yourself, so pay attention to your mental health. Last year my wife spend a few months looking for a new job, and every rejection hits hard, especially when you get to the later interview stages
12. Set a pace and stick to it - one day you might find 10 new job offers, and the next day 0. You should rather send 5 applications on the first day and then another 5, that way you'll be able to put more time into applications and you'll feel more productive
13. Treat finding a job as a job itself - start in the morning, spend some time finding new offers, some time reaching out to people, some time applying, have a daily rhythm that you keep Monday to Friday
14. TAKE TIME OFF. If you can, take weekends off, if you've been searching for 3 months, take a few days break. It'll be hard to stop thinking about resumes and job applications, but it'll allow you to go longer
15. I can't emphasize how helpful it it - last year I took a few days off and my wife took a break from job search. Even though we could not go anywhere, it gave us both a lot of energy and motivation
16. Last part: use free resources that are available. See whether there's a junior dev community like juniordev.io around you, check online communities, even Reddit can be useful when it's not toxic
17. Not to mention YT channels or places like @ThePracticalDev where people share their knowledge. It's easy to get swamped by all these resources, so make sure to pick one thing at a time
18. A year ago I interviewed a few recruiters and hiring managers about finding job as a junior dev. Their advice is still relevant today:
19. Finally, I provide some free advice via @ClubMentoring - I mostly talk to senior devs and engineering managers, but if you have questions about getting your first job in the industry, you can check out when I'm available: mentoring-club.com/the-mentors/gr…
20. Obligatory "this should have been a blog post". Yeah, I know, I know. /🧵
• • •
Missing some Tweet in this thread? You can try to
force a refresh
One interesting thing I've learned from the Alibaba story was how in EBay went from 90%+ of the market in China in 2002, to leaving China entirely just 5 years later. (1/5)
There are many reasons why EBay lost, but one interesting one is that they refused their Chinese team to drive the product. Instead they tried to unify the platform globally, so that the whole site worked and looked the same everywhere. (2/n)
These days it's changing, but generally Chinese web design is very different than western design - sites are more busy and flashy, there's a lot of information there. Compare main page of Amazon vs JD: (3/n)
The president of Square Enix (Final Fantasy games and more) wrote about play-to-earn and NFTs as upcoming major trend in gaming in 2022. A large part of the letter feels like crypto bros' wet dreams, but a small part there could lead to something positive:
The bad parts are obviously that they want to shove NFTs and blockchain in players' faces, which I believe is a dangerous and completely unnecessary trend.
Also saying that goodwill and volunteer spirit are inconsistend in comparison with willing to make money makes me cringe
I don't think that play-to-earn will make games more exciting, instead it'll turn them into weird worlds with little to no authentic enthusiasm. It's like a party where some guests are there to have fun and some are hired actors, but you don't know who's who.
This year I've read so far 20 books. Here's what I do and don't recommend: 📕
1. "Multipliers" - a book about a leadership and being a genius vs genius maker (someone who helps other to reach their potential). Overall ok, but it should be 50 pages instead of 250
2. "System design interview" by @alexxubyte - great read when preparing for tech interviews. Very solid and yet concise examples. It helped me to pass a number of interviews. Highly recommended!
With 💎 Ruby 3 released, let's have a look at how the language evolved since the version 2.0 was released more than 7 years ago. A history thread about #ruby#ruby3 🧵:
In 2013 @yukihiro_matz announced Ruby 2.0 and he said the core team would release a new minor version every year during Christmas time🎄This was huge news 🎉 for Ruby devs since until then the releases were irregular. It made the future look very bright
Ruby 2.0 brought a bunch of features: keyword arguments, module#prepend and lazy enumerators.
One minor, but verys useful feature was %i literal to create arrays of symbols - I use it so often! 💪🏻