Read on Twitter
Dear amazing human wanting to become a developer,Looking for your first job can feel like you're throwing two hundred darts blind-folded, hoping just one hits the dartboard.
However, there are some things you can do to give yourself an edge.
Ideas in-thread
RESUME TIPS
1. Put effort into crafting your resume. This is what gets you in the door for an interview. Aim to be interesting, concise, honest. Interesting because you need to stand out from 50 other applicants. Concise because the reviewer doesn't have time to read 3 pages.
1. Put effort into crafting your resume. This is what gets you in the door for an interview. Aim to be interesting, concise, honest. Interesting because you need to stand out from 50 other applicants. Concise because the reviewer doesn't have time to read 3 pages.
Honest because lying about your skills will always come back to bite you in the butt .
2. Find an attractive resume template - a clean, sharp layout is best. You can get one for $5-10 on https://creativemarket.com/search?q=developer&categoryIDs=2%2C43. Or you can use the ones on https://www.canva.com/ for free!
2. Find an attractive resume template - a clean, sharp layout is best. You can get one for $5-10 on https://creativemarket.com/search?q=developer&categoryIDs=2%2C43. Or you can use the ones on https://www.canva.com/ for free!
3. Find a tech recruiter who's willing to review your resume. Ask them for feedback. What's good. What could be improved. Is there anything you could add that would grab their attention?
4. Don't do what everyone else does in their 'professional summary' section. Of course you're hard-working and know Microsoft Word. That shit is so generic. Add a brief blurb that reveals your personality. For mine I put that I've loved building things ever since I was kid
playing with Legos and painting, and that coding scratched that same itch. I've had quite a few recruiters and hiring managers rave about that part. What's your story? What are you interested in that could be related to the job you're applying for?
5. Prominently list projects you've made that you're passionate about. Employers worth their weight in salt will appreciate this section. Apparently it's rare to find an entry-level developer who builds shit and can also talk about the codebase in a coherent manner?
APPLYING TIPS
1. Don't apply to large amounts of positions in short bursts. You'll burn yourself out and give up. Instead, pace yourself. 2 applications/day for a week ends up being better than 8 applications on a single day.
1. Don't apply to large amounts of positions in short bursts. You'll burn yourself out and give up. Instead, pace yourself. 2 applications/day for a week ends up being better than 8 applications on a single day.
2. Use a tool to track the jobs you've applied for. This is so important. How the hell are you supposed to juggle 150 different variables in your head alone? Think about all the steps. Applying. Following up. Writing thank you notes. 150*3 is 450 tasks on your mental todo list!
There are spreadsheets floating around the web you can use. Or you can use a free tool like https://huntr.co/ , which is basically Trello for job-hunting.
3. IMO, you shouldn't spend your time applying to jobs that say things like "posted 2 months ago". Sadly the truth is first movers have the advantage. Many job boards have an option to create an alert for new jobs matching specific terms or criteria. Set some up and apply ASAP.
INTERVIEW TIPS
1. Send
a thank-you note after EVERY interview. Even phone screens. Just do it! Read more at https://www.theladders.com/career-advice/sample-of-a-thank-you-email-after-an-interview.
1. Send
a thank-you note after EVERY interview. Even phone screens. Just do it! Read more at https://www.theladders.com/career-advice/sample-of-a-thank-you-email-after-an-interview.
2. Be prepared with questions you want to ask the interviewers. Do your research on the company and think of what else you'd like to know. This a MUTUAL interview! You want to know if they're a good fit for you as well. Also, having questions ready shows initiative and curiosity.
3. Technical interviews are probably the scariest part of this whole process. I don't have too much to say here except that this article is fantastic and will help you prepare/feel less anxious --> https://www.freecodecamp.org/news/interviewing-prep-tips-and-tricks/
4. Demonstrate to the interviewers that you're both teachable and curious. They want to know...
Are they going to be able to mold you into their image?
Are you going to have the initiative to learn new things without being explicitly told to?
Are they going to be able to mold you into their image?
Are you going to have the initiative to learn new things without being explicitly told to?
P.S. If you made it this far, I'll review your resume if you DM it to me. 
