Monday, January 11, 2016

Cracking the Coding Interview (College) - Gayle McDowell



http://www.slideshare.net/gayle2/cracking-the-coding-interview-college
How to Get an Interview
Your Background
Education
Work Experience
Projects
Github / Online Profile
Make a great resume

Pull resume out of giant stack
Spot-check: companies, projects, etc.
Skim bullets to see if you’ve written real code.

“Glanced at,” not read. 15 seconds
How CS Resume Should Look

One Page Only!
Unless > 10 years exp.
A Real Resume Format
with organized columns
Short (1 – 2 line bullets)
Focus on Accomplishments
not responsibilities

3 – 4 Projects
Courses & independent
Finished or unfinished
List of Technical Skills
Short! Cut the “fluff.”

Talking to Recruiters
Show:
What you’ve done (mobile app? Show it!)
What you’re excited about
Have a “pitch” ready
Weird is okay
(arrogant is not)

Behavioral Questions
The Pitch / Resume Walk-Through
Shows of success
Prompt the interviewe
Hobbies

Your Past Work
1 – 2 Hard Projects
Hard / cool
You were central
Technical depth

All Past Work
Challenges, architecture, tradeoffs, mistakes, successes, motivations
What did YOU do?

Technical Questions
How did you do RELATIVE to other candidates on the SAME question?

It’s not about how quickly you solved the problem…
… it’s about how quickly you solved it relative to other candidates.
Knowledge Questions
Design/Scalability
Algorithms/Problem Solving

How do indices work in SQL?
If you list it, know it
If you don’t know it, admit it
Derive it if possible.

How would you design TinyURL?
How to approach
What u would do at work

Scope, Key components, identify issues, repair
Scope the Problem
Ask questions
Make appropriate assumptions
Define Key Components
Can be somewhat naïve
Identify Issues
Bottlenecks, tradeoffs
Repair & Redesign

Discuss Top-> Down
DRIVE
Lead the process
Be open about issues

TEAMWORK
Be open to feedback
Tweak as necessary

How to prepare
Read about design of major companies
Twitter, Facebook, Quora, Google, etc.
Think about WHY they’re designed that way
Learn/review key concepts
Task queues, databases, sharding, etc.
Practice questions

Algorithm Preparation
Problem solving, not puzzles!

How to… attempt to solve a hard problem
Closing Advice
Do projects
Study for your interviews
Chase interviews
… but don’t chase money
Check-in on your career.
Is this what you want to do with your life?

Labels

Review (572) System Design (334) System Design - Review (198) Java (189) Coding (75) Interview-System Design (65) Interview (63) Book Notes (59) Coding - Review (59) to-do (45) Linux (43) Knowledge (39) Interview-Java (35) Knowledge - Review (32) Database (31) Design Patterns (31) Big Data (29) Product Architecture (28) MultiThread (27) Soft Skills (27) Concurrency (26) Cracking Code Interview (26) Miscs (25) Distributed (24) OOD Design (24) Google (23) Career (22) Interview - Review (21) Java - Code (21) Operating System (21) Interview Q&A (20) System Design - Practice (20) Tips (19) Algorithm (17) Company - Facebook (17) Security (17) How to Ace Interview (16) Brain Teaser (14) Linux - Shell (14) Redis (14) Testing (14) Tools (14) Code Quality (13) Search (13) Spark (13) Spring (13) Company - LinkedIn (12) How to (12) Interview-Database (12) Interview-Operating System (12) Solr (12) Architecture Principles (11) Resource (10) Amazon (9) Cache (9) Git (9) Interview - MultiThread (9) Scalability (9) Trouble Shooting (9) Web Dev (9) Architecture Model (8) Better Programmer (8) Cassandra (8) Company - Uber (8) Java67 (8) Math (8) OO Design principles (8) SOLID (8) Design (7) Interview Corner (7) JVM (7) Java Basics (7) Kafka (7) Mac (7) Machine Learning (7) NoSQL (7) C++ (6) Chrome (6) File System (6) Highscalability (6) How to Better (6) Network (6) Restful (6) CareerCup (5) Code Review (5) Hash (5) How to Interview (5) JDK Source Code (5) JavaScript (5) Leetcode (5) Must Known (5) Python (5)

Popular Posts