Learn How to Code
  • Welcome
  • Foundations
    • Introduction
      • Becoming a web developer
      • Motivation and mindset
      • Join a supportive community
      • How does the web work?
    • Requirements
      • Prerequisites
      • Text editors
      • Command line basics
      • Setting up Git
      • Setting up Node
    • Git
      • Git basics
      • Project: Practicing Git
    • Frontend
      • HTML and CSS
      • Developer Tools
      • Project: Create a web page
    • JavaScript
      • Strings and Conditionals
      • Using Developer Tools
      • Functions
      • Problem solving
      • Project: Rock paper scissors
      • Writing clean code
      • Arrays and Loops
      • The DOM
      • Project: Etch-A-Sketch
      • Objects and More Arrays
      • Project: Calculator
    • Backend
      • Frameworks
    • Next steps
  • Deep dives
    • Computer Science
      • Pseudocode and algorithms
      • Recursion and algorithms
        • Project: Fibs and sorting
        • More on algorithms
        • Big O
        • Project: Practicing Big O
      • Data structures
        • Maps, Stacks and Queues
        • Project: Stacks and Queues
        • Nodes, Linked Lists and Trees
        • Project: Linked Lists
        • Project: Trees
        • Next steps
    • Databases
      • Databases and SQL
      • Project: SQL Zoo
    • Design / UX
      • Fonts and typography
      • Grids
      • Project: Teardown
      • Responsive design
      • Project: Mobile friendly
      • CSS frameworks
      • Project: Bootstrapping
    • HTML / CSS
      • HTML Basics
        • Linking
        • Images and media
        • Project: Embedding media
        • HTML5
        • Tables
        • Lists
        • Forms
        • Project: Make a form
      • CSS Basics
        • Box model
        • Floats and positioning
        • Flexbox
        • Grids
        • Project: Breaking news
        • Best practices
        • Backgrounds and gradients
        • Project: One more thing
        • CSS3
        • Preprocessors
        • Project: Your own framework
      • Next steps
    • JavaScript
      • Refresher
      • Organization
      • Objects and constructors
      • Project: Library
      • Factory functions and module patterns
      • Project: Tic Tac Toe
      • Classes
      • ES6 Modules
      • Project: Restaurant
      • Object Oriented Programming
      • Project: Todo list
      • Linting
      • Menus and sliders
      • Forms
      • ES6 features
      • JSON
      • Callbacks and promises
      • Using APIs
      • Async and Await
      • Project: Weather
      • Testing
      • Project: Testing 1-2-3
      • Advanced Testing
      • Project: Battleship
      • Backends
      • Project: Where's Waldo?
      • Project: All-Star
      • Next steps
    • NodeJS
      • Project: Going to school
      • Project: Passing the test
      • Express
        • Templates and middleware
        • CRUD and MVC
        • Project: Message board
        • Routes
        • Displaying data
        • Forms and deployment
        • Project: Inventory
      • Authentication
      • Security
      • Project: Clubhouse
      • APIs
      • Securing an API
      • Project: Blog
      • Testing
      • Testing with a database
      • Project: Social network
    • React
      • Props and State
      • Render lists and handle inputs
      • Project: CV
      • Lifecycle methods
      • Hooks
      • Project: Memory card
      • Router
      • Project: Shopping cart
      • Advanced concepts
    • Ruby
      • Installation
      • Data types
      • Variables
      • Input and Output
      • Conditionals
      • Loops
      • Arrays
      • Hashes
      • Methods
      • Enumerables
      • More enumerables
      • Nested collections
      • Blocks
      • Pattern matching
      • Debugging
      • Project: Caesar cipher
      • Project: Substrings
      • Project: Stock picker
      • Project: Bubble sort
      • Object oriented programming
      • Project: Tic Tac Toe
      • Project: Mastermind
      • Serialization
      • Project: Event manager
      • Project: Hangman
      • Computer Science
        • Recursion
        • Project: Merge Sort
        • Data structures and algorithms
        • Project: Linked Lists
        • Project: Binary Search Trees
        • Project: Knight Travails
      • Testing
      • RSpec
      • Project: Four in a row
      • Git
      • Project: Open Source
      • Project: Chess
      • Next steps
    • Ruby on Rails
      • Using Heroku
      • Installing Rails
      • Basics
        • Routing
        • Controllers
        • Views
        • Asset pipeline
        • Deployment
        • Project: Blog
      • Active Record
        • Project: Upvote
      • Forms
        • Cookies, sessions, and authentication
        • Project: Password
      • Advanced forms and Active Record
        • Associations
        • Project: Private Events
        • Callbacks
        • Menus, helpers and nested forms
        • Project: Ticket agent
      • APIs
        • External APIs
        • Project: Animals
        • Project: Photo widget
      • Mailers
        • Project: Confirmation
      • Advanced topics
        • Action Cable
      • Project: Social network
      • Next steps
  • Getting hired
    • Preparing to find a job
      • Plan a strategy
      • What companies want
      • Get yourself together
      • How to prepare
      • Project: Make your website
    • Applying and interviewing
      • Qualifying leads
      • Project: Make your resume
      • Applying for jobs
      • Preparing for an interview
      • Handling an offer
      • Final words
  • Maintained by
    • wbnns
  • License
    • CC BY-NC-SA 4.0 © 2022
Powered by GitBook
On this page
  • Understanding their perspective
  • Life behind the curtain
  • Internships
  1. Getting hired
  2. Preparing to find a job

What companies want

Companies are looking for someone who can add value as soon as possible and who will be able to grow with the organization.

PreviousPlan a strategyNextGet yourself together

Last updated 4 years ago

Understanding their perspective

Now that you've figured your own situation out, the fact is that you can't get hired by just thinking about why you need or deserve the job. You have to think about things from the perspective of the company. Why are they interested in hiring you? What, therefore, will they look for?

Life behind the curtain

Hiring managers are busy people. That's why they need someone new... to remove some of their workload and get their team working better or faster. They also have to deal with potentially hundreds of unqualified applicants every week, which takes up too much of their valuable time. They just want to get back to building stuff and not have to hire again anytime soon. So they are looking for someone who can add value as soon as possible and who will be able to grow with the organization.

The second characteristic, growth, is something you shouldn't have much trouble selling if you've come this far and learned web development on your own. The key is to present yourself as a growth curve, not just a static line (i.e. you'll continue learning and improving very rapidly and not stop). You have real career goals and you've learned incredibly fast so far to get to where you are (right?).

The first part, adding value immediately, is more difficult -- that's where they want to see that you've had relevant experience before and can meet their technical bar. There's a bit of a catch-22 with getting hired -- the easiest way to show you are employable is to have been employed before. It's a check mark next to you. So to cater to this; do whatever you can to show that other people have believed in you enough to use your work and skills.

Aside from those two characteristics, there is another major factor -- fit. The hiring manager wants someone they and their team can work well with. All the other stuff represents minimum hurdles for being considered. But you often make or break your chances by being someone the team members want to know better and work with all day long. Almost all hiring processes ask the full team to evaluate a late-stage candidate.

So to summarize, hiring managers are usually looking for 3 main things:

  1. Capability

  2. Motivation

  3. Fit

You can learn a bit about the perspective of hiring managers by reading blog posts about how to hire developers. No need to go crazy, but try to get a picture of why they're hiring you:

  1. , which should give you an idea of the need and pain of hiring great engineers.

  2. . Look for "people who are 1. Smart, and 2. Get things done".

Internships

A good way to start getting experience and show others that you're employable is to get an internship. Just make sure it's a paid internship because no one values things they get for free. You want the people you work with to value your contributions and feel like they have a stake in helping you succeed. The good part is that internships tend to focus more on your growth potential than what you've done before, so you can start to avoid that chicken-and-egg problem described above.

The hiring process for internships is usually similar to but not quite as rigorous as full-time positions. Internships are basically just long interviews by that company to see if they want to bring you on full-time.

These should be useful links for you:

The Best Way to Hire Software Developers
How to Hire Talent
Joel Spolsky has a lengthy diatribe on hiring developers
Joel Spolsky's Guerrilla Guide to Interviewing 3
Beyond a Resume: What Tech Recruiters Want
Thread on "How do I get a Software Internship" from MetaFilter
InternMatch