Skip to content

Instantly share code, notes, and snippets.

@MrAaronOlsen

MrAaronOlsen/job_search_action_plan.md

Last active July 30, 2017 23:08
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save MrAaronOlsen/47be30fd0ed463d544fbfe04dbb11781 to your computer and use it in GitHub Desktop.
Save MrAaronOlsen/47be30fd0ed463d544fbfe04dbb11781 to your computer and use it in GitHub Desktop.
Download ZIP
Mod 3 PD Job Search Action Plan
Raw
job_search_action_plan.md

Module 4 Goals

  • Have multiple job contacts in the pipeline (4 - 5)
  • Have at least one job prospect
  • Have at least three contacts outside of turing
  • Have stable versions of side projects
  • Have consistant blog posts

Strategy To Achieve Goals:

Coding (both including your module 4 curriculum and anything outside of it):

  • Repeat. Redoing the frameworks of projects and in class exercises.
  • Continue work on side projects and updating Git.
  • Have solid looking projects I can use as demonstration.
  • Continue with blog posts.
  • Update and polish past projects README files and maybe touch up a few things in the code too.

Opportunities Research:

  • I've been searching companies on-line and narrowing them down based on my interests. The list grows, and as it does I've gotten a better feal for what companies I should spend more time researching.
  • The next step is to reach out to a contact in the companies I seem to like the most, regardless of job openings.
  • From there it's a job of following up on contacts, keeping myself in the loop, and trying to be a good person.
  • My wife is also helping to reach out since she's in contact with a lot proffesionals in her job. She's helped build my list of companies.
  • Meetups and other such events are good for me only because they force me to talk about myself, tech, and see how this weird world turns. In that way it helps my research.

Cold Outreach/Network:

  • Continue to build list of companies and individuals I'm interested in.
  • At the very least I want to make 2 or 3 cold outreaches each week on my list.
  • I'd like to meet with someone once(ish) a week, but there's a lot I can't controll here.

Timeline:

  • Launch blog by end of mod3
  • Have at least one more 'solid' contact by the end of intermission
  • Have a list of 20 or more companies to start bugging by the end of intermission

Module Tasks:

  • Week one:
    • Have at least 5 or more contacts in the 'ether'.
    • Have had or at least set up two prep interviews.
  • Week two:
    • Have met with two or more contacts.
    • Have made 'contact' with one or two more.
  • Week three:
    • Have an interview? This is hopeful, but a goal.
    • Also by now I should have gone to two or more Meetups I'm interested in. They're on the calendar...
  • Week four:
    • Have good stabel working demonstration of my side projects.
    • Be killing it at Turing's course work.
  • Week five: Turing. I have a sense this week is going to be hard.
  • Week six: Use this time to catch up or do extra things.

Weekly Tasks:

  • For a while now I've dedicated a minimum of 8 hours each week to my side projects, making outside contacts, meetups, etc...
  • Monday mornings I'm at my freshest, and this is when I code on my personal projects.
  • Tuesday are when I write e-mails and research companies.
  • Wednesday is when I send those email (or slack messages) or perhaps make calls. People tend to want to meet on wednesdays too. Wednsday are also the day before projects are due, so I try to keep this day dedicated to Turing.
  • Thursday is when I do anything else I need to do. Could be any of the above.
  • Friday is a wash. Go home Aaron and relax. Your exhausted.
  • Typically one day each Weekend is dedicated to Turing while the other is off limits. Like Thursdays this ends up being what ever it needs to be.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment