Your algorithm was correct, your code was correct, but you still got rejected. This is not only possible, but incredibly common.
Candidates are routinely surprised when it does because they don’t quite understand the interview process and how they are evaluated. Read More
If you want an A+ career in technology, you should move to the San Francisco Bay Area. The same argument can probably be made of finance and New York. It’s not that you can’t do it in another city, but your odds are just much better in your industry’s hub. So if you want an A+ career and your industry has a clear hub, go there. Read More
Accept that invitation to do a talk that you don’t really you’re qualified for. Go meet that person for coffee, even if you don’t really see the point. Throw together that website that will almost certainly never lead anywhere.
Opportunities start from saying yes.
Say yes. Read More
Like friendships, mentorships — the ones that actually exist, not the ones that exist in name only — rarely start from a formal request, and certainly not from a near stranger. It doesn’t work for mostly the same reasons. It’s artificially trying to create a personal relationship. Read More
I'll get to the fifteen pieces of advice. But first, let me explain what awesome careers look like.
They don't look like nice linear graphs, where you're moving up a little bit each month. (Heck, even so-so careers don't look like that. You don't move up every month. You get a bit better at your career every month, but you move up in big steps.) Read More
After coaching hundreds of people through coding, behavioral, and product manager interviews, I’ve distilled some of my core advice into some handy prep sheets.
Study these sheets before your interview. Really understand them. Email me questions if you have any.
As you prepare for interviews, use these sheets. Walk through your next coding problem closely following the procedure below. It’ll help you — I promise. Read More
Not everything about the interview process is predictable, but you can bet that you’ll be asked a few behavioral questions – and probably a few behavioral questions per interview. Behavioral questions can be questions like, “what would you do if _______?”, but more likely they’re of the form, “Tell me about a challenging interaction with a coworker on _____ project.” Contrary to popular belief, you can and should prepare for behavioral questions. Yes, I know it’s “just talking about yourself,” but that doesn’t mean that you can’t use a few tricks to nail down your answers.
»» Read more on Dice.com Read More
Another day, another overly-hyped article on Google’s “crazy” interview questions. This one though gives hope to aspiring Googlers; Google has finally seen the light and realized that brainteasers aren’t useful! Not exactly.
Nothing has changed. Read More
I talked before about why it’s good to tell your interviewer when you already know the solution to a problem. But what happens when you don’t know the answer? What do you do then?
»» Read more on Dice.com Read More
Some people love testing — and with good reason. Poking around and figuring out how to break stuff can be a lot of fun. However, some people take SET/SDET roles as a way into a company, and hope to move to being a plain ol’ software developer shortly thereafter. In many cases, these people find themselves stuck and unable to make that transition.
How do you make that jump? Read more on Dice.com. Read More