One of the best pieces of career advice I received is this: don’t do what most people do.
Most people want to work for known, brand name companies. Most people apply for jobs with resumes and cover letters. Most people focus on skills. Most people wait for a response from companies. Most people never hear from most companies.
Do do that. Especially if you’re struggling to get a break.
The fastest way to land a tech job is to get into early stage companies…
Want a job? network. Want to start a company? network. Want to make a sale? network.
Seems like the answer to everything in life is network.
But if you just graduated from college, hardly know anyone, and dying to get a job, how the heck do you network? If you’re an engineer who loves coding, when do find the time to network? If you’re an introvert who can barely tolerate people, why on earth should you network?
Let me start with a simple fact:
Network is a side effect, not an outcome.
If you go to Stanford, you’ll have access…
If you’re just starting out as an engineer, here’s a few things you should keep in mind. I wish someone told me these when I was starting out.
When you start out, you know how to code but you don’t know what’s good and what’s bad yet. So it’s important that you work on a code base that’s well organized and well designed. The best way to do this is to go to companies that have a strong engineering culture; work with engineers that care about code…
I hate this question so much — I think you should seriously reconsider your decision to join a company if they ask. No sensible hiring manager should be asking this question. It’s thoughtless, and it’s insulting.
But since it’s often asked, in the interest of helping you land a job, I’m going to give you an answer — a powerful answer.
Why is it that some engineers are more effective than others? Why is it that smart people get stuck in their careers while not-so-smart people race to the top? Why is it that some people always seem to “have their way”?
If you want to join a startup, directly emailing founders can be your best bet. In small companies (1–50 people), the founders spend a lot of time recruiting people. They don’t have dumb recruiting systems and processes that scan and eat your resume or throw riddles and puzzles at you. Founders are generally more thoughtful and human about recruiting. They do have biases, but you have a good shot at overcoming them — your success entirely depends on how creative and persistent you are.
Elon Musk is perhaps the most celebrated entrepreneur of our generation. A true super hero who’s trying to save the planet. A man who does what he says and says what he does. He’s been called Thomas Edison, Henry Ford, Steve Jobs, even Iron Man.
There’s a lot written about Elon. I don’t want to sound like a simpleton and restate the obvious. However, I do want to highlight one important career lesson which is in this (perhaps the most introspective) video interview of Elon.
Technical interviews suck. There’s no correlation between your interview performance and real performance on the job. We know that as long as Google and StackOverflow are alive we can build anything. Yet, sadly, companies prefer technical interviews to real accomplishments.
But to their defense, companies don’t have a choice. When a company has half a dozen people, the founder CEO can — and often does — spend as much time as possible recruiting the right people using a good set of…
This question is almost guaranteed to come up in job interviews. Most people don’t think much about it — they just make up some cookie cutter answer such as “I want to be a tech lead” or “I want to learn more skills”, etc. There’s thousands of blog posts that offer perspectives on how to answer this question.
Many hiring managers generally ask this question to see if you have a vision for yourself. Not having one is okay. …
There’s an age old myth in the tech industry that product managers can benefit from knowing how to code. Commonly cited reasons:
Many product managers believe this and take online coding classes, bootcamps and what not.
Coding — or scripting to be more precise — is generally a good skill to have for…