Technical interview notes

tech_interview

# Technical interview:
-take your laptop
##Questions the interviewer might ask you:
 1. Describe the project you are most proud of
    * get technical, describe the tech you used
    * if you go more than five minutes, you're not doing it right
    * if you have your laptop, offer to show interviewer your app/site/etc (may or may not take you up on it)
    * distinguish between exciting tech (stripe) and not (rails gems)

2. Testing
    * what kind of tests did you use (integration, unit, etc)
    * test-driven development is a different beast

## Questions for them:
  ### You need to be asking questions!
  * have specific things that show you have looked at their website and understand the things they've put out there publicly
  * detailed digging into what they do and work environment
    * how much pair programming
    * do you have JS frameworks you rely on
    * methodology
    * what type of agile
    * what would life be like if I worked here
    * what do you like about working here?
    * how many hours do developers work here?
    * do I get assigned to projects, will I work on one thing or many in a [length of time]
    * what about projects I can't see from the outside, suite of apps that you build, integrations (do you have to do separate work for each client, or are you changing some config parameters for a preexisting codebase)
    * show you're passionate about what they do
    * frame yourself as a consumer of their product

## Technical questions:
  1. Talk through it!
    * The interviewer might get up and write on the board, or ask you easier question if you're struggling
  
    #### Examples of tech questions    
    1. You have eight pool balls, one of which weighs more than the others. They all look the same, you can't tell a difference from looking or picking them up. Given a set of scales, how many attempts would it take to figure out which is heaviest? 
    
    2. Write a method that returns an array of the first 1k primes:
  ####*LISTEN TO QUESTION. FIRST THOUSAND PRIMES IS DIFFERENT THAN PRIMES UP TO ONE THOUSAND
      
    3. Debug question might come up:
      * this isn't working, what's wrong
      * this is working, but why is it bad

    4. They might quiz on general Ruby questions:
      * what's MVC
         - draw diagram if you think of it
      * what's REST

### Site that you can use to practice:
http://www.rubeque.com/