DEV Community

Discussion on: What Am I Doing Wrong?

Collapse
 
recursivefaults profile image
Ryan Latta

Darrell,

People have covered a lot of things with you here. I'll offer my story and advice. I left college with no internships or experience and found myself needing a job. There was no Github either. At the time the advice everyone gave was having a really good business card and going to career fairs. So after fumbling around with that I changed course and went from almost never getting a call after applying to getting a call every single time.

I believe your issue is your resume and cover letter. This, of course, removes the absolute best way of getting a job which is through a friend or your network. Even if that happens you need a good resume so people can't find a reason to reject you.

There's a fantastic post on this site already about building a resume, but let me summarize some key things about a great resume:

  1. In the beginning, each job gets its own resume. Eventually, this will turn into each role but for now each job. This lets you dial things in.
  2. You will need to list your skills. This needs to be near the top and contain some of the major asks for the job. It doesn't need to be 100% perfect, but the big items need to be there.
  3. For "Experience" talk about your accomplishments and the value you brought. Never talk about the tasks you did. You didn't build a react web-application, you delivered a web an application that services 50,000 users a day.
  4. Use numbers in your accomplishments and value statements. They stand out they beg for a story.
  5. Be brief, but don't overly limit yourself. You'll find lots of advice telling you to keep your resume to 1 page or two. This has never been an issue for me. What you're doing is conveying that you are a perfect fit as effectively as you can within 30-60 seconds. Two pages of mind-blowing stuff are better than one pointless one.
  6. Make an adjustment to every application. It is hard to know what will make people call you, but keep trying.
  7. Apply EVERYWHERE. You need to get the skill of getting a job before you get the job you want.
  8. Cover letters are very important. You buy a few minutes of time with them where you can tell your story and why you belong there. Don't squander that opportunity, take your time with it and think about this from their perspective.
  9. No typos, no errors, make the resume look clean and sleek.
  10. References available upon request.

It took me about 3 months to go from getting no calls to consistent calls with every application. What nobody tells people is that getting a job is completely different than doing a job. They are separate skills and require practice and dedication.

Good luck to you, and you would like help with your resume hit me up.

Collapse
 
inceptioncode profile image
Darrell Washington

Those where great tips I never thought about needing to restructure my resume. I have gotten other tips but those suggestions are great. Can you give me the link or title of the post you are referring to?

Also the apply to everywhere tip is something I need to work on honestly. This may sound weird but I do filter my job search. Things like 2-3+ years of experience, knowing A-H technologies, and understanding X,Y and Z scare me off.

I do need to get past that.

Collapse
 
recursivefaults profile image
Ryan Latta

Here is the post: dev.to/agazaboklicka/how-to-write-...

The job search is a draining experience. It takes practice, discipline, and a lot of resilience. Hang tough and don't stop until you get a job.

Then, get a different one if it doesn't work out.

Thread Thread
 
inceptioncode profile image
Darrell Washington

Thanks, Ryan, I'm not planning on giving up. I will keep trying
different actions until I get the results.👍