1. Description
1.1. Author
1.1.1. Randall Kanna
1.1.1.1. https://twitter.com/randallkanna/status/1277968548078292999
1.1.1.2. https://twitter.com/RandallKanna
1.2. A complete guide for developers on Job Hunting, acing the interview and landing the job
1.3. The Standout Developer
2. 1. Standing out
2.1. You need a roadmap and a proven formula to beat the odds
2.2. Becoming a standout developer will move your career forward, increase your income, and make it easier to quickly land a new job
3. 2. Establishing an Online presence
3.1. having an online presence and being known in your engineering niche means more companies will discover you and want to hire you
3.2. Define your Niche
3.2.1. Look at twitter bios of engineers who have careers you admire
3.2.2. Make sure your resume highlights your experience in that niche
3.3. Leveraging twitter
3.3.1. Twitter can be an invaluable tool for engineers to advance their carrer.
3.3.2. Building a twitter following
3.3.2.1. 1. Provide value in your tweets
3.3.2.1.1. Tweets that help people learn will be incredibly valuable
3.3.2.1.2. if you are sharing your journey and you share what you're learning, other people will want to learn along with you and from you
3.3.2.1.3. make authentic tweets, no need to make a 'tweet quota'
3.3.2.2. 2. Find an audience
3.3.2.2.1. you need to start carving out a specific audience
3.3.2.3. 3. Spend time analyzing your tweets that do well
3.3.2.3.1. don't focus on your follower count or what tweets will bring you the most followers
3.3.2.3.2. don't focus solely on having a large audience
3.3.2.3.3. quality of follower matters + engagement with people in the same industry/like-minded will lead to amazing opportunities
3.3.2.4. 4. At the end of you blog posts, link to your twitter profile
3.3.2.4.1. people want to get to know who you are before subscribing to an email list (for example)
3.3.2.5. 5. Building a strong twitter profile
3.3.2.5.1. make sure you have a twitter account with a professional handle and your photo
3.3.2.5.2. create a powerful twitter bio
3.3.2.6. 6. Answer your DMs
3.3.2.6.1. DMs can impact your twitter growth
3.3.2.6.2. craft tweets based on what people ask you
3.3.2.7. 7. give away free stuff
3.3.2.7.1. consider the time commitment involving in offering a free service that takes up time before you twee it
3.4. Interview with Daniel Vassalo, founder of Userbase (@dvassallo)
3.4.1. Everyone Can Build a Twitter Audience
3.4.2. You are significantly better off as an engineer if other people know about you
3.4.3. Teach what you know without any expectations
3.4.3.1. As soon as you learn something that can fit in a 280-chars tweet, share it with others
3.4.4. don't just reply with any statement on someone's tweet, make sure you are adding value
3.4.5. if you are junior, you can write about your coding journey
3.5. LinkedIn
3.5.1. your online resume
3.5.2. Your headline matters
3.5.2.1. keywords matters on linkedin search; having a relevant headline will help you increase your odds of getting found
3.5.3. Write a compelling summary
3.5.4. Use the accomplishments section to your benefit
3.5.5. Fill out every section on linkedin
3.5.5.1. all-star users are 40 times more likely to get contacted via linkedin
3.5.6. Get a custom URL
3.5.7. Ask someone to write a recommendation for you
3.5.8. Use a professional headshot
3.5.9. have a professional website
3.5.9.1. buy your domain
3.5.9.2. make sure your website includes: blog, contact section, projects, relevant links
3.5.9.3. get feedback before you go live
3.6. My TO DO System
3.6.1. Standup
3.6.1.1. spend a few minutes at the end of every day writing a summary of all the work I completed that day
3.6.1.1.1. helps me to not struggle to remember all the things I did
3.6.1.1.2. help me to be better prepared for future interviews
3.6.2. Meetings
3.6.2.1. take notes on this section if I need to remember something for a particular meeting
3.6.3. Three big Daily's
3.6.4. Daily work
3.6.4.1. mandatory task that you need to do every day for you job
3.6.5. Habits
3.7. Taking breaks
3.7.1. Pomodoro technique helps to stay focused and to remember to take breaks
3.7.1.1. set a timer 25-45 minutes and stay focused on one task at hand; no distractions; When the timer rings take a break 5-15 minutes;
3.8. Don't fake it until you make it. Do this instead
3.8.1. it's ok to not know everything
4. 3. Creating a successful Blog
4.1. having a blog is a big part of having an online presence
4.2. get into the habit of writing
4.2.1. once you've broken the barrier and written one post, the posts that follow will be significantly easier
4.3. Write a compelling blog post
4.3.1. not easy to write a compelling blog post
4.3.2. a good post can build credibility and help companies find you online
4.4. creating an outline
4.4.1. when you are writing the outline, think about what your reader will gain from reading your post
4.5. creating a compelling title
4.5.1. pick a title that will catch the attention of potential readers
4.6. write the post
4.6.1. your blog post shouldn't be too short or lacking detail
4.6.2. when you are writing your post, ask yourself who will be reading it
4.7. write a powerful introduction
4.8. don't forget the conclusion
4.9. editing
4.9.1. use grammarly to check what you've written to find issues
4.9.2. ask for feedback from peers who can write
4.10. select a good image
4.11. decide where you'll publish your post
4.12. creating a content calendar
4.12.1. a calendar can help you keep track of what you want to write about and when it should be published
4.12.2. can you commit to one blog post a month to start?
4.13. Promoting your content and finding your audience
4.13.1. building a list of readers will motivate you to write more blog posts
4.14. best places to share your blog posts
4.14.1. a few places you can post your blog to get some traction:
4.14.1.1. twitter
4.14.1.2. reddit
4.14.1.3. freecodecamp
4.14.1.4. hacker noon
4.14.1.5. hacker news
4.14.1.6. dev.to
5. 4. Leading a speaking gig
5.1. Speaking at conferences is one of the most valuable things you can do
5.2. “First of all, I’d like to make clear that everybody gets nervous on stage! Even the most experienced speakers do. Some speakers do it just for that feeling, for experiencing that thrill! That being said, what helps me is using a couple of thought “reframings.”
5.3. reframings
5.3.1. “I am not getting nervous, I’m just getting excited about it!” ”
5.3.2. “The second reframing I do is related to the reason I’m speaking. I avoid thinking of myself as an expert or that I’m going to teach the audience how to do things the right way”
5.4. getting ready
5.4.1. speak at meetup
5.4.1.1. best venue to get started
5.4.1.2. typically smaller
5.4.1.3. informal
5.4.1.4. can have lightning talks
5.4.2. create youtube tutorials
5.4.2.1. not as valuable as previous speaking experience, but they will help you stand out
5.4.3. blog on a plataform like freecodecamp or dev.to
5.4.3.1. can help build your reputation as reliable and valuable member of the community
5.5. how to get your first conference gig
5.5.1. learning about the next big thing
5.5.1.1. it is easier to stand out from the crowd as the competition is smaller
5.5.2. submitting a pitch
5.5.2.1. create a list of conferences that are feasible for you to speak, prioritize in terms of application deadlines
5.5.2.2. next: start brainstorming a list of conference topics; you'll need to come up with two or three topics for your speaker application
5.6. tips for becoming a confident speaker
5.6.1. talk slowly
5.6.2. practice constantly
5.6.3. act natural
5.6.4. make eye contact
5.6.5. dress up
6. 5. The standout resume
6.1. resume screening
6.1.1. your resume will have to beat ATS
6.2. what is ATS?
6.2.1. application tracking system
6.2.1.1. tracking system that scan your resume for key-words and filters that the company is looking for
6.3. the cv screen
6.3.1. having an outstanding resume determines whether you'll get to a cv screen
6.4. the fundamentals
6.4.1. your resume needs to be formatted well, should clearly showcase your work experience
6.4.2. using the best template
6.4.2.1. tools
6.4.2.1.1. 15 Free Tools to Create Professional Resumes - Hongkiat
6.4.2.1.2. canva
6.4.2.2. find a resume template that matches your experience level
6.4.3. crafting a powerful summary section
6.4.3.1. having a powerful summary section can mean you get noticed and stand out in a pile of resumes
6.4.3.2. the key to writing a standout summary is to do it last
6.4.3.2.1. write resume first and then focus on summary section
6.4.3.3. create your summary section to the job you are applying for (if possible)
6.4.3.4. make sure your summary section isn't too short or too long
6.4.4. work experience
6.4.4.1. the most important part of your resume
6.4.4.2. shouldn't focus on bland tasks or contributions
6.4.4.3. what makes a resume stand out the most is relevant experience - Ben Ilegbody (StichFix)
6.4.4.4. avoid non-specific statements such as
6.4.4.4.1. Led a project team for the new checkout experience
6.4.4.4.2. Created a web application built in mean stack
6.4.4.4.3. Provided support for the company’s main application
6.4.4.4.4. Test driven development using Jasmine
6.4.4.4.5. Practiced object-oriented design patterns
6.4.4.5. try to focus on specific results and archivements
6.4.4.5.1. examples
6.4.4.6. if you don't have work experience as a developer, focus on expanding your resume projects section and adding extra courses
6.4.4.7. examples
6.4.4.7.1. Independently delivered the “XYZ” project built in Node.js and Vue.js three weeks ahead of schedule.
6.4.4.7.2. “XYZ” was used by 2,500 users in the first month.
6.4.4.7.3. Implemented “XYZ,” which improved loading time of ${whatever you sped up!} by ${loadTime}.
6.4.4.7.4. Researched and found an existing automated testing solution that allowed the development team to catch ${bugCount} issues in QA once implemented.
6.4.4.7.5. Created a deploy tool using ${techUsed} that reduced the overall deploy time from thirty minutes to two minutes.
6.4.5. projects
6.4.5.1. adding a personal project to a resume is the best thing you can do when you have little or no job experience
6.4.6. skills
6.4.6.1. only list the skills you feel confident about answering questions
6.4.6.2. don't list too many skills
6.4.7. education
6.4.7.1. not having a CS degree won't prevent you from advancing as long as you position your skills and achievements correctly
6.4.7.2. if you have a degree in other field, you should list it
6.4.7.3. if you have several degrees, list the most relevant first
6.4.7.4. if you are still in school, list where you are
6.4.7.5. if you dropped out of college, but only had a few classes left to graduate
6.4.8. courses
6.4.8.1. list what you've done to advance your skills
6.4.9. certifications
6.4.9.1. certifications add strength to your resume
6.4.10. contact me
6.4.10.1. make sure you include
6.4.10.1.1. personal website
6.4.10.1.2. e-mail address
6.4.10.1.3. phone number
6.4.10.1.4. twitter profile
6.4.10.1.5. github profile
6.5. editing your resume
6.5.1. mistakes on resume make your resume look unprofessional
6.5.2. formatting and consistency
6.5.2.1. what you can do to make your resume look more professional
6.5.2.1.1. Keep capitalizations consistent.
6.5.2.1.2. If you use bullet points, use only one type of bullet point; don’t mix and match with arrows and circular shaped bullets.
6.5.2.1.3. Your font type and size need to stay consistent throughout your resume, with few exceptions such as for a main header.
6.5.2.1.4. Stay consistent in how you write about yourself—don’t switch from “I” to “she” or “he” in your about me or summary section.
6.5.2.1.5. Make sure the formatting is perfect.
6.6. common mistakes that will get your resume rejected
6.6.1. 1. including personal details
6.6.1.1. don't need to put on your resume
6.6.1.1.1. age/birthday
6.6.1.1.2. Gender
6.6.1.1.3. A photo of yourself
6.6.1.1.4. Your physical address. For security and safety reasons, don’t list your full address. Put something general like San Francisco, CA, for example.
6.6.1.1.5. Your hobbies. Adding your hobbies to your resume isn’t necessary.
6.6.1.1.6. Insignificant information that takes up space on your resume.
6.6.2. 2. not using a career change
6.6.3. 3. not using keywords
6.6.4. 4. readability
6.6.4.1. don't use small fonts
6.6.4.2. don't add too much information
6.6.5. 5. lazy errors
6.6.5.1. grammar errors
6.6.6. 6. avoid first-person pronouns
6.6.6.1. try to say "delivered new feature".. instead of "I delivered..."
6.6.7. 7. don't go to second page
6.6.8. 8. not tailored to the job
6.6.8.1. just list what's relevant about the job you are appling for
6.6.9. 9. inflating your resume
6.6.9.1. be honest about what you've accomplished
6.6.10. 10. sending the wrong document type
6.6.10.1. send a pdf version
6.6.10.2. use yournameresume.pdf - easier to search for your name
6.6.11. 11. listing references
6.6.11.1. avoid saying you have references
6.6.11.1.1. it looks outdated
6.6.11.2. getting references is part of the interview process
6.6.12. 12. applying to too many jobs
6.6.12.1. “ATS software shows recruiters how many jobs an applicant has applied to within their company. Applying to too many jobs in the same company can tell a recruiter that you don’t really know which job you want, or worse—that you aren’t sure of your skills.”
6.7. final thoughts on creating a standout resume
6.7.1. craft compelling story
6.7.2. don't be shy!
6.7.2.1. write your achievements
6.7.3. showcase your passion
7. 6. Portfolio
7.1. taking a project to an interview is a powerful tool
7.2. having a standout portfolio will benefit you at any point in your career
7.3. how to plan your first portfolio project?
7.3.1. 1. sketch out the flow of the app
7.3.2. 2. sketch out how the app will work
7.3.2.1. how the app will work?
7.3.3. 3. sketch out the flow of how the different parts of your app will interact
7.3.3.1. what tools do you need to use or learn?
7.3.4. 4. create a trello board with a list of tasks
7.3.5. 5. set concrete deadlines for your project