...
Full Bio
Use Machine Learning To Teach Robots to Navigate by CMU & Facebook Artificial Intelligence Research Team
219 days ago
Top 10 Artificial Intelligence & Data Science Master's Courses for 2020
220 days ago
Is Data Science Dead? Long Live Business Science
248 days ago
New Way to write code is about to Change: Join the Revolution
249 days ago
Google Go Language Future, Programming Language Programmer Will Get Best Paid Jobs
570 days ago
Top 10 Best Countries for Software Engineers to Work & High in-Demand Programming Languages
722565 views
Highest Paying Programming Language, Skills: Here Are The Top Earners
669036 views
Which Programming Languages in Demand & Earn The Highest Salaries?
474141 views
Top 5 Programming Languages Mostly Used By Facebook Programmers To Developed All Product
459354 views
World's Most Popular 5 Hardest Programming Language
389607 views
How To Write A Engineering Resume & Showcase For Your Software Engineering Skills
For those of you who are starting out on your software engineering job search, and have questions about how to prepare a great resume that can get your foot in the door, then this article is for you.
- Do's in a resume
- Don'ts in a resume
- Extra tips
- Advice for new graduates
- Tools/resources I recommend
- Be consistent. Use consistent font (Arial/Times New Roman are OK) and no more than three font sizes for readability
- Use sections (use four major ones: Work Experience, Education, Skills, Projects)
- Use keywords in your resume, and be accurate. Recruiters do look for keywords in resumes (e.g. Java, Python, Hadoop, real-time are some examples of keywords).
- Social media accounts are OK to list if it's relevant. GitHub is popular for hosting software, so that's OK to list. Snapchat, not so much.
- Explain why you are suitable for the position. You can write a cover letter as an add-on, or a brief summary at the top of your resume. These give recruiters a stronger signal of who are you and why you want to apply.
- Use numbers. If you helped a website scale, don't just write it verbatimâ??-â??put a metric in there. "I helped the website scale from 10K views/day to 100K views/day."
- Use an active voice. Use verbs like "designed," "implemented," "executed," "drove," and "planned."
- Use PDF. Any other file format, like .docx, might cause your resume to render differently.
- Pick two to three projects you know really well. You should know these from top to bottom, front to back. Knowing two to three projects really well shows dedication and ability to ship things, two desirable traits any company needs.
- Do not list all the positions you've held since high school. A retail position you held in high school over summer would not be of much interest to a tech company.
- Do not quantify your skill level. Put technologies you've worked with, and skip out on labeling them as "Good," "Expert," and so on.
- Do not list every single buzzword you've heard of. Some examples include "big data," "real-time," "machine learning," "docker," and "batch streaming." Use them with care. You'll probably be asked to demonstrate your knowledge of these technologies during the interview.
- Do not go in-depth without explaining how it's relevant. Most candidates have done something cool, but they fail to make recruiters see how it's relevant.
- do not list irrelevant skills. Microsoft Excel, Word, and so on are basic computer skills most people know, so you can leave those out.
- backend engineer
- RESTful architecture
- scalable
- product visionary
- Cracking the Coding Interviewâ??-â??a great starter book on coding in general, and some resume writing tips in there. I used this to prepare my first draft of my resume.
- The Google Resumeâ??-â??great starter book, for new grads in particular. Talks about majors/minors to pick, how to write resumes, and sort of a step-by-step guide for getting the dream job.
- Elements of Programming Interviews: Great for more difficult coding problems
- OneNote: I use this to store all code snippets
- Evernote: For everything else
- Refdash: Run by a bunch of ex-Googlers. The quality of mock interviews here is. The interviewers are ex-Googlers. I highly recommend trying them out.
- CodePath: A non-profit org that helps people prepare for a career in tech. Nathan and Tim are great people and I have learned a lot from them. The community is very helpful and everyone is willing to give a hand.
- Fine-point markers: Bring these to your interview. I highly recommend them!