91–100 of 225 posts
On the other hand, I asked a friend in the bay area about an engineering position he had applied for. 13 rounds, and he was finally told no.
Oh we all value diversity so so much. Just fucking all dress alike, it's our culture, no diversity here. Hypocrisy.
While you sort of have a point there, there's much more diversity in how people dress at top tech companies than in, say, finance or consulting. It seems you're upset that an interviewer might be biased against someone for wearing a suit. That's fair; an interviewer shouldn't be biased against a candidate for that. And most wouldn't be -- consciously. But subconscious bias can still exist. It's best to skip the suit,…
Earlier quoted context omitted.
Referrals are honestly a great strategy. Often employees will be open to referring you even if you don't know them well. Use social media, Facebook groups, Quora, etc. Recruiters want to be found. Have an active github. Make yourself Google-able. Have a website where you list projects. Screenshots help make things feel more "real", especially if it's a recruiter/sourcer who might not understand some of the technical…
For people not in college anymore, those are great advices. Having been on the recruited and recruiting side for one of the big 5, I'd add an extra advice: Don't panic if you don't have any of the things mentioned above, especially when still young in College. I didn't have an active github, nor a website, nor screenshots of my side projects. If you're genuinely passionate when you talk about it (no matter how small…
So if your goal is to get the interview, go through referrals. Don't expect anything from side projects.
Build something on your own. Nine-to-5 isn’t enough. Practice, Practice, Practice. Single parents or carers need not apply, eh? Diversity?
Some companies want to attract people who spend 40 hours a week on their job and nothing more and that's OK. Other might be out of reach unless you spend many more hours learning every week and that's OK too.
Whereas people are spending their free time with their kids or learning or watching television it's up to them.
We've adopted a new process for interviewing software engineers. It has three interview sessions held on subsequent dates: 1. Candidate learns about the company and the tech during a set of 2-4 interviews with our engineers. We don't tell them to learn as much as they can because we want to see how inquisitive they are. Interviewers are coached to be fairly open and talk about our products and tech. If there are no r…
You're going to get a lot of people dropping out of that funnel. If you only get 2 to 3 people who also have offers from 3 to 4 other places this kill your ability to hire. plus thats a huge time investment for the interviewer as well.
Earlier quoted context omitted.
The biggest problem I have with these companies is that they feel like a cult. And the people working there are doing a lot to keep that cult spirit alive. All of these companies want you too feel and act like they are the single best entity in the entire universe and you should be honored that they even acknowledged you. This works great for young graduates that are full of dreams and hopes but it discourages experi…
> I would rather make more money in a stupid corporate job than working on more aggressive ways of making people to click on ads. Could you name a few "stupid corporate jobs" that pay better than Google or Facebook (200k - 300k for a senior engineer) ?
Earlier quoted context omitted.
1. No, you don't need to know everything. You should know what a binary search tree. You probably don't need to know the specifics of how to balance one. (If a company is requiring this knowledge, then they're doing whiteboard interviews poorly [or they have a very specific skillset needed]. That's not a problem with whiteboard interviews. That's a problem with that company or interviewer. It takes maybe a week for a…
>1. No, you don't need to know everything... It takes maybe a week for a smart developer without a CS degree to learn what they need to know for interviews. I just went through a job search and I didn't find this true. I think the bar on algorithms has raised significantly with all of the prep material (your book included) out there. I also found a few companies sent over "things to study" lists that were quite compr…
These Cracking the Code interview type interviews are not even close to what we do all day everyday.
Most of it is good advice for fresh graduates who want to get into big companies. Shouldn't we be telling these young people to aim higher?. If you derive your sense of worth from a bigger brand and not your own efforts and caliber, you might be complacent for a while then life happens and you will regret not accomplishing anything meaningful in life. Before preparing for your interview and seeking validation for you…
Startups aren't that special, and I lost a lot of income by doing small startups first as an employee for 4/5 years. Startups even in successful cases are just break even working at AFGAM. Usually you'll quickly be throwing away $100k/yr in income instead. And that $60k/yr your not putting in your stock brokerage account you could of used for whatever bootstrapped digital business or financial independence base you c…
Build something on your own. Nine-to-5 isn’t enough. Practice, Practice, Practice. Single parents or carers need not apply, eh? Diversity?
This is not related to diversity. Some companies want to attract people who spend 40 hours a week on their job and nothing more and that's OK. Other might be out of reach unless you spend many more hours learning every week and that's OK too. Whereas people are spending their free time with their kids or learning or watching television it's up to them.
Sure- you don't need a CS degree but you need to know everything taught in a CS degree regardless of it's applicability to real life software engineering. You should also buy a bunch of books and section off at least a month to study. Especially if you don't have that CS degree. Hope you don't have other obligations like a family or a demanding job. You should also spend a lot of time doing coding competitions even i…
1. No, you don't need to know everything. You should know what a binary search tree. You probably don't need to know the specifics of how to balance one. (If a company is requiring this knowledge, then they're doing whiteboard interviews poorly [or they have a very specific skillset needed]. That's not a problem with whiteboard interviews. That's a problem with that company or interviewer. It takes maybe a week for a…
1. Obviously you have a lot of experience with this but I just can't see how a week is anywhere near accurate judging from my personal experience, people I've talked to, and the numerous online stories of people's personal experience.
2. To be honest, I kinda expect the world's smartest organization to find some better way to evaluate talent. Google says they want diversity but requiring a month of studying isn't going to allow for that. Their process throws false negatives on a lot of people that could otherwise be great engineers (which they largely admit to).
3. They're different skillsets. One is about knowledge, the other is about memorizing question patterns and practicing implementation speed.
4. Does Google have data here? My experience is a lot of candidates shut down at a whiteboard because it's not what they're used to. They're afraid to experiment or erase or use longer clearer variable names because of the overhead of writing by hand and dealing with space limitations. It's a lot more messy to modify and extend code you've already written.
5. No, it's really bad. It's like this weird mix of cursive and small caps. I'm not sure what is going on.