The methodical approach is applaudable, and I'm really glad it works for people like the author. Maybe it is indeed the best strategy. But after a few rounds of doing this, it gets old. Not old as in, "I'd rather be watching westworld than drafting this cover letter". But old as in, "I'd rather be shoveling diarrhetic pig shit than doing this code exercise". I really love being a software engineer. The job applicatio…
Don’t Get Attached, It’s Just Luck. My Interviewing Advice and Tips
91–100 of 108 posts
Re: Don’t Get Attached, It’s Just Luck. My Interviewing Advice and Tips
#92This has got to be one of the most honest descriptions of how job hunting actually works ever written and posted on HN. It's a sharp contrast to a lot of the stuff that is posted here that depicts job hunting like some kind of spiritual search for your life's passion.
I think this is a great description of the job hunting process early in your career. Later in your career, if you have kept connections alive, the job hunt should look like this: "Hi , I'm looking for a position doing X at Y, and I noticed you know Sara at Y. Do you mind doing intros? I'd really appreciate it." ... intros/coffee with Sara. ... resume to the hiring manager, perhaps through some automated system, but w…
Re: Don’t Get Attached, It’s Just Luck. My Interviewing Advice and Tips
#93Earlier quoted context omitted.
> "i also agree these take homes are not 4 hour affairs. they give you no direction so you can't sacrifice ui/ux for functionality because you have no clue how they judge it." I had a take home for a UI position that I spent ~10-12 hours on. It was some pretty standard UI stuff and they had 5 points of functionality they wanted you to code. Make it responsive, have these sections in a different order on mobile, make…
Given their cluelessness, would you even want to work with them? I'm guessing you "failed" that interview, and it was probably a good thing, too.
Re: Don’t Get Attached, It’s Just Luck. My Interviewing Advice and Tips
#94While I agree that interviewing is a bit of a crap shoot, the above paragraph from the OP is actually a pretty good argument for not doing anything to prepare for it.
If going into interviewing mode means you stop working on your own stuff, or having free time, or generally doing stuff that a) you enjoy and b) make you better at your work (rather than interviews) then you're paying a cost alright, and it's at least comparable to the cost of take-home coding exercises.
If you're just applying anywhere you can it probably means you don't care where you go anyway. If you apply in sufficiently many places eventually you'll find the one place where they like you, you like them, you got what they want and they're willing to hire you.
In fact if you take the time you'd waste in getting good at interviewing and invest it in learning a new language, or framework, or following a MOOC etc, you'll probably end up with much better qualtiy work, because your actual work skills will get better. It might take a bit longer to get there but you'll (probably) stick around for longer and you'll get more out of it.
Re: Don’t Get Attached, It’s Just Luck. My Interviewing Advice and Tips
#95Lots of great stuff here. It is a numbers game in many ways since I've been in interview processes where we turned down lots of people who go on to succeed in amazing ways at other companies. I would be wary about recommending most people write cover letter templates. I can tell a templated letter most of the time. I'd recommend just writing a few sentences from the heart. Why you're great for them. Copy+Paste doesn'…
For cover letters, I think I'm using template more loosely and probably should have provided examples. The template part is for describing myself, however I still write out a paragraph or two specific to that company. I think I noted on researching the place before hand so you can include your favorite things about the place in the letter.
Re: Don’t Get Attached, It’s Just Luck. My Interviewing Advice and Tips
#96"Things like knowing the box model, closures, map/filter/reduce, object vs array, prototypes, bind/call/apply, event delegation. These made up almost ever single first phone screen interview I’ve ever had." Seems pretty hefty for a junior-frontend-position.
Re: Don’t Get Attached, It’s Just Luck. My Interviewing Advice and Tips
#97Earlier quoted context omitted.
So you prioritized for people willing to sink many hours into your assignment. The need to sink many hours into a homework assignment is the criticism.
Phone interview - 1h during work hours. On-site interview - ~3h total, but probably a whole day off work. Test - ~1h at any time you choose. I'm not sure I follow your logic. They would spend just as many hours, at a more inconvenient time of day without the test. I did the task myself to a level I'd expect at the time to make sure it does not take "many hours". If that simple task would take people many hours, then…
Do you really think "the 1 person who made a proper package, a short .rst install & use documentation, and included crazy unicode test cases" spent only an hour?
Re: Don’t Get Attached, It’s Just Luck. My Interviewing Advice and Tips
#98"Things like knowing the box model, closures, map/filter/reduce, object vs array, prototypes, bind/call/apply, event delegation. These made up almost ever single first phone screen interview I’ve ever had." Seems pretty hefty for a junior-frontend-position.
Re: Don’t Get Attached, It’s Just Luck. My Interviewing Advice and Tips
#99Re: Don’t Get Attached, It’s Just Luck. My Interviewing Advice and Tips
#100I have noticed that too often the interviewers look for people like themselves, which I find really naive - chances of you finding your own copy are slim to none. A recent anecdote from my own experience. I've interviewed with this company. Everything seemed to go well, I had a talk with hiring manager, then with one of the guys from technical team where we discussed real world problems, etc. Everything goes well. As…
I find that older, more experienced engineers tend to know not to ask these kinds of deep domain-specific questions (unless the are directly relevant to the position being applied for).
The unfair part about this type of interview process is that the interviewer assumes that what the candidate knows is only a subset of what they know - But they completely ignore the knowledge that lies outside of the intersection (which could also be useful).