It's pretty simple (I have one already made on my fork), but I think it would be nice to publish this as a github page.

I can't push a seperate fork however, so if you could either 1. make a new branch called "gh-pages" so I can submit a pull request or publish this as a github page, that would be much appreciated 😄

pennappsfellows.com which is linked to under Fellowships redirects you to a shady site that tries to get you to download an extension :(.

(Thanks for this awesome repo btw)

This is one I've been thinking about a bit lately. A lot of folks come to interviews with projects they have done for GA/HackerSchool/A hackathon etc. They say "this is an example of my work but it's not complete because we didn't get time to finish it or do x". I'm really impressed by those people who have:

a) Worked more on the project AFTER their course or event. "I didn't have time to do x but I decided it'd be useful/learning to add it."

Or if not

b) Can articulate what they'd do next. And importantly why that is a "next" not something they did. It shows good product sense if you can articulate what was MVP, what you excluded and why.

Still embryonic thought but interesting.

The provided link for the "Cracking the Coding Interview, by Gayle Laakmann McDowell" webpage is broken, that is, it leads to a 404 page, the URL seems to be slightly different than the actual one. I've included the correct one below, kindly consider changing the link. Cheers!

Current link: https://www.crackingthecodinginterview.com/w

Correct link: https://www.crackingthecodinginterview.com/

Is getting-a-gig open for translation opportunities?
I would love to collaborate on a Spanish version of this!

Some ideas.

1. It's okay to say "I don't know". Bonus if you can credibly add "but I'd probably use Google/try this thing/do this other thing". Honesty.
2. Research, research, research - read up (don't stalk) your interviewers.
3. Know something about the company and their product that is interesting - what would you change, what's not great, heritage, technical stack.
4. Ask good questions - about the company, their product ("Why does the product do x?"), the role, their expectations, their process, mentoring, onboarding.

Hi!

I have made numerous presentations about Portfolio building. Would you like me include some tips as a separate section here?

So this is extremely minor, but I think mailing address is relevant and can help you get a job on your resume because a lot of companies where I live (maybe its because a lot of them are security clearance/government consulting type jobs) need to see that you're a local candidate. Maybe I've just had the bad luck of dealing with fools, but I took my mailing address off my resume and was asked 5-10 times if I was out of state (because I had an out of state phone number + no mailing address).... despite my current work history being local and having it mentioned in my cover letter.

Sounds silly I know but I'd hate to know that my resume got thrown out for not being clear that I was local... wouldn't want that happening to anyone.

I spend last few days searching for a good resume template. Can you suggest one?

Under General Guides Data Structures and Algorithms Overview link is now broken and leads to phishing advertisements

Mulo

Para páginas web

Also might be a good idea to add maintaining a gig as well, because well you might get the gig but then lose it?

These links are very Google focused, but GOOD companies recruit like Google :)

Problems and blog posts

• https://sites.google.com/site/steveyegge2/five-essential-phone-screen-questions
• http://www.dsalgo.com/2013/02/index.php.html?m=1
• https://docs.google.com/document/d/116s-IXQFsf6FNaPsc2jFXs_1wTJzemh1QNA7KVSaoII/edit
• https://oj.leetcode.com/problemset/algorithms/
• http://alexbowe.com/failing-at-google-interviews/
• https://www.quora.com/What-should-I-expect-in-a-Software-Engineer-interview-at-Google-and-how-should-I-prepare?srid=vhu&share=1
• http://courses.csail.mit.edu/iap/interview/materials.php
• https://www.google.ca/about/careers/lifeatgoogle/hiringprocess/
• http://javarevisited.blogspot.ca/2013/03/top-15-data-structures-algorithm-interview-questions-answers-java-programming.html
• http://bigocheatsheet.com/
• https://code.google.com/codejam/contests.html
• http://www.fitcoding.com/

Books

• https://github.com/kasaquan/book/blob/master/Robert%20Sedgewick%20and%20Kevin%20Wayne%20-%20Algorithms,%204th%20edition.pdf
• http://greenteapress.com/complexity/thinkcomplexity.pdf
• http://larc.unt.edu/ian/books/free/poa.pdf