Skip to content

Instantly share code, notes, and snippets.

@jillmd501
Last active March 9, 2016 01:40
Show Gist options
  • Save jillmd501/02662ac668fd02e96d3c to your computer and use it in GitHub Desktop.
Save jillmd501/02662ac668fd02e96d3c to your computer and use it in GitHub Desktop.

The 'Job Hunting' Assignment

Company #1

  • List any Turing/gSchool/Hungry Academy grads that work there
    • None
  • List anyone else you know that works there
    • None
  • Link to the company's Github page(s)
  • List the tech stack of the company
    • HTML, CSS, JS, Ruby, Rails
  • Divide the tech stack into:
    • tech you've worked with
      • ALL OF IT
    • tech you're familiar with
    • tech you know almost nothing about
  • List any meetups and events they have recently or will soon sponsor
    • Pretty small startup, couldn't find any yet....
  • List any technical interview information you can find about the company
    • none on glassdoor, but great reviews :)
  • List 'pros' and 'cons' of working for this Company
    • PROS: Consultancy, looking for a junior, super trendy, HIGH glassdoor ranking
    • CONS: still haven't heard after a week and a half, WANT THIS RUL BAD
  • What is your next step to pursue working at this company?
    • Contacting someone at the company - what do I have to lose?

Company #2

  • List any Turing/gSchool/Hungry Academy grads that work there
    • none
  • List anyone else you know that works there
    • hopefully me soon
  • Link to the company's Github page(s)
  • List the tech stack of the company
    • You can find the tech stack in a few different ways
      • ruby, JS, rails, angular, java, html, CSS
  • Divide the tech stack into:
    • tech you've worked with
      • ruby, rails, js, html, css
    • tech you're familiar with
      • angular
    • tech you know almost nothing about
      • java
  • List any meetups and events they have recently or will soon sponsor
    • not that I could find, but I am following them on twitter now
  • List any technical interview information you can find about the company
    • 'Everyone I met really did a great job at putting me at ease and the company did a good job in letting me know who I'd be interviewing with and what would be expected (as far as if it were a technical or personality interview)."
    • no whiteboarding!
  • List 'pros' and 'cons' of working for this Company
    • PROS: young, fun company, heart of portland, consultancy
    • CONS: some bad reviews on glassdoor
  • What is your next step to pursue working at this company?
    • Reach out to a specific person to talk

Company #3

  • List any Turing/gSchool/Hungry Academy grads that work there
    • HOPEFULLY ME
  • List anyone else you know that works there
    • not A DAMN PERSON
  • Link to the company's Github page(s)
  • List the tech stack of the company
    • Ruby, miniTest, Rails
  • Divide the tech stack into:
    • tech you've worked with
      • ALL of THEM!
    • tech you're familiar with
    • tech you know almost nothing about
  • List any meetups and events they have recently or will soon sponsor
  • List any technical interview information you can find about the company
    • "That interview went well and then I had another skype interview with the guy in charge of hiring. Wasn't too difficult. They didn't try to stump me. Very conversational. Each lasted about 30 mins."
  • List 'pros' and 'cons' of working for this Company
    • PROS: BAD ASS outdoor company, outdoor minded people, good reviews, familiar stack
    • CONS: Currently not hiring...
  • What is your next step to pursue working at this company?
    • CONTACT THEM ANYWAY!

Company #4

  • List any Turing/gSchool/Hungry Academy grads that work there
  • List anyone else you know that works there
    • Jess Goulding has a friend who used to work there and loved it
  • Link to the company's Github page(s)
  • List any open source projects actively maintained (have commits in the last 6 months)
  • List the tech stack of the company
    • Scala, with a bit of Clojure, Java, and Ruby
  • Divide the tech stack into:
    • tech you've worked with
      • Ruby, JS
    • tech you're familiar with
      • React
    • tech you know almost nothing about
      • Java, Clojure, Scala
  • List any technical interview information you can find about the company
    • "There were no highly-technical whiteboard questions or anything of that nature. Most of what was asked was hypothetical scenario questions, or technical history questions."
  • List 'pros' and 'cons' of working for this Company
    • PROS: socially concious! awesome office, seems like an open minded office, I feel more confident intheir stack
    • CONS: some bad glassdoor reviews, working internally vs. consultancy
  • What is your next step to pursue working at this company?
    • Reaching out to people via twitter/email/linkedin who are currently working there

Company #5

  • List any Turing/gSchool/Hungry Academy grads that work there
  • List anyone else you know that works there
    • Mike has a solid connection and is willing to write a letter of recommendation
  • Link to the company's Github page(s) repos
    • List any open source projects actively maintained (have commits in the last 6 months) open-source
  • List the tech stack of the company
    • java, mySQL, HTML/CSS, Andriod, ios
  • Divide the tech stack into:
    • tech you've worked with
      • HTML/CSS
    • tech you're familiar with
    • tech you know almost nothing about
      • Java, Android, iOs, mySQL
  • List any meetups and events they have recently or will soon sponsor
    • Not a lot - they are in Issoquah, WA
  • List any technical interview information you can find about the company
    • What project would you recommend Costco take on next to improve user's experience?
  • List 'pros' and 'cons' of working for this Company
    • Pros: Very good company to work for, treats employees well
    • Cons: SUPER corporate, not downtown, work internally - might get bored
  • What is your next step to pursue working at this company?
    • Reach out to Mike
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment