I have thoughts on how to deal with this. My priors are this won’t work if I communicate it through text (but I have no idea why). Still, seems like the friendly thing would be to write it down
My recommendation on how to read this:
If this advice fits you, it should read as “ah obviously, how didn’t I think of that?”. If it reads as “this is annoying, I guess I’ll do it, okay....”—then something doesn’t fit you well, I missed some preference of yours. Please don’t make me a source of annoying social pressure
Again, for some reason this works better when speaking than in writing. So, eh, … idk.. imagine me speaking?? get a friend to read this to you?
(whatever you chose, consider telling me how it went? this part is a mystery to me)
So,
TL;DR:
The goal of interviews is not to pass them (that’s the wrong goal, I claim). The goals I recommend are:
Reducing uncertainty regarding what places will accept you. (so you should get many rejections, it’s by-design, otherwise you’re not searching well)
Practicing interviews. Interviews are different than actual work, and there’s skill to build there. So after interviews, I’ll review stuff I didn’t know, and I’ll ask for feedback about my blind spots. I have some embarrassing stories about blind spots I had in interviews and would never notice without asking for feedback. Like, eh, taking off my shoes and walking around the room including the interviewer 🫣 these are actual blind spots I had which are absolutely unrelated to my profession of software development
Something about the framing of “people who interview a lot beat others in getting better jobs”—and motivation to be one of those
Get yourself ice cream or so after interviewing
Important sub point: Positive reinforcement should be for “doing good moves” (like scheduling an interview, or like reviewing what you could do better), and NOT for passing interviews (which imply to your brain that not-passing is negative, and so if your brain has uncertainty about this—it will want to avoid interviewing)
Asking a close friend / partner / roommate what they think could work for you. They might say something like “play beat saber, that always makes you feel good” which I couldn’t guess
Sometimes people spend a lot of time on things like writing cover letters (or other things that I think are a wrong use of time and frustrating (and in my model of people: some part of them knows this isn’t a good idea and it manifests as stress/avoidance, though I’m no therapist)). I’d just stop doing those things, few things are (imo) worth the tradeoff of having more stress from interviews. It’s a tradeoff, not a game of “do interviews perfectly and sacrafice everything else”
1.a. and b.: Reframing it like that sounds nice! :-D Seems like you solved your problem by getting shoes that are so cool, you never want to take them off! (I so wouldn’t have expected someone to have a problem with that though…) I usually ask for feedback, and often it’s something like “Idk, the vibe seemed off somehow. I can’t really explain it.” Do you know what that could be?
2. I’m super noncompetitive… When it comes to EA jobs, I find it reassuring that I’m probably not good at making a good first impression because it reduces the risk that I replace someone better than me. But in non-EA jobs I’m also afraid that I might not live up to some expectations in the first several weeks when I’m still new to everything.
3. Haha! Excellent! I should do that more. ^.^
4. You mean as positive reinforcement? I could meet with a friend or go climbing. :-3
5. Aw, yes, spot on. I spent a significant fraction of my time over the course of 3–4 months practicing for Google interviews, and then never dared to apply anyway (well, one recruiter stood me up and I didn’t try again with another). Some of the riddles in Cracking the Coding Interview were so hard for me that I could never solve them in 30 minutes, and that scared me even more. Maybe I should practice minimally next time to avoid that.
Thank you so much for all the tips! I think written communication works perfectly for me. I don’t actually remember your voice well enough to imagine you speaking the text, but I think you’ve gotten everything across perfectly? :-D
I’ll only pounce on amazing opportunities for now and continue GoodX fulltime, but in the median future I’ll double down on the interviewing later in 2024 when our funds run out fully. Then I’ll let you know how it went! (Or I hope I’ll remember to!) For now I have a bunch more entrepreneurial ideas that I want to have at least tried. :-3
I usually ask for feedback, and often it’s something like “Idk, the vibe seemed off somehow. I can’t really explain it.” Do you know what that could be?
This sounds like someone who doesn’t want to actually give you feedback, my guess is they’re scared of insulting you, or being liable to something legal, or something like that.
My focus wouldn’t be on trying to interpret the literal words (like “what vibe”) but rather making them comfortable to give you actual real feedback. This is a skill in itself which you can practice. Here’s a draft to maybe start from: “Hey, I think I have some kind of blind spot in interviews where I’m doing something wrong, but I don’t know what it is and a friend told me I probably won’t notice it myself and I better get feedback from someone else. Any chance you’d tell me more about what didn’t work for you? I promise not to be insulted or complain for not passing or anything like that”
2.
But in non-EA jobs I’m also afraid that I might not live up to some expectations in the first several weeks when I’m still new to everything.
This is super common. Like, I’m not making this up, I had dozens of conversations and this is a common thing to worry about, and it’s probably true to many other people interviewing to the same position.
My own approach to this is to tell the interviewer what I’m worried about, and also the reasons that I might not be a good match for whatever this is. For example, “I never worked with some-tech-you-use”. If after hearing my worries they still want to hire me, that’s great, and I don’t need to pretend to know anything. I also think this somewhat filters for hiring managers that appreciate transparency (and not pretending everything is perfect), which is pretty important to me personally.
(also, reasonable managers understand you will need onboarding time, and if they don’t understand that—then I prefer they don’t hire me)
This all totally might be a Yonatan-thing, idk.
4.
You mean as positive reinforcement?
Yeah
I could meet with a friend or go climbing. :-3
I think (?) I’d aim for something short that I could do right-after, so my brain will understand this is a positive reinforcement and not just an unrelated fun evening? This is just my own intuition. I guess it would work if I’d meet a friend and they’d keep saying “good job for interviewing! now let’s get you chocolate!” or whatever :)
I don’t really know, I recommend you trust your own introspection, I might be unusual here
5.
Maybe I should practice minimally next time to avoid that.
Eh, you might have (right now) downsides to applying and not having it work well. The downsides might be subjective or “technically wrong” but if you’re averse to applying with minimal practice, I would acknowledge that feeling and try to address it (or if you can’t—I’m not personally pushing you to apply to Google unprepared, if it seems scary or so).
Examples of things that might worry you:
a. “will google never invite you to interview again if you fail” --> You can check Google’s policy. I think they have a 6-12 months cooldown for people who didn’t pass, but you can apply again. Is this time too long? Maybe you don’t care at all? I don’t know, depends on your circumstances
b. maybe you’re not interviewing to dozens of places and so it (maybe correctly) feels like Google is your only chance? ( --> I’d recommend interviewing to dozens of places, to be clear :P )
I think a useful answer here would mainly involve listening to you which I can’t really do over text. If you want to brainstorm out loud here, I can try to contribute “textbook solutions” if I have them. Or you could do introspection with a friend, or we could talk, or none of the above! just trying to share how I’d approach this
This sounds like someone who doesn’t want to actually give you feedback, my guess is they’re scared of insulting you, or being liable to something legal, or something like that.
Oh, interesting… I’m autistic and I’ve heard that autistic people give off subtly weird “uncanny valley”–type vibes even if they mask well. So I mostly just assume it’s that. Close friends of mine who surely felt perfectly free to tell me anything were also at a loss to describe it. They said the vibes were less when I made a ponytail rather than had open hair, but they couldn’t describe it. (Once I transition more, I hope people will just attribute the vibes to my probably-unfortunately-slightly-imperfect femininity and not worry about it. ^.^ I just need to plant enough weirdness lightning rods. xD)
But he was US-based at the time, and I’ve heard employers in the US are much more careful with giving feedback than around here, so maybe it was just guardedness in that case.
I like your template! I remember another series of interviews where I easily figured out what the problems were (unless they were pretenses). I think I’m quite attuned (by dint of social anxiety) to subtle indications of disappointment and such. When I first mentioned earning to give in an interview, I noticed a certain hesitancy and found out that it’s because the person was looking for someone who has an intrinsic motivation for building hardware for supply chain optimization rather than someone who does it for the money. But in other cases I’m clueless, so the template can come into action!
My own approach to this is to tell the interviewer what I’m worried about, and also the reasons that I might not be a good match for whatever this is. For example, “I never worked with some-tech-you-use”. If after hearing my worries they still want to hire me, that’s great, and I don’t need to pretend to know anything. I also think this somewhat filters for hiring managers that appreciate transparency (and not pretending everything is perfect), which is pretty important to me personally.
Oh yes, I love this! I think I’ve done this in virtually every interview simply because I actually didn’t know something. One interviewer even asked me whether I know the so-and-so design pattern. I asked what that is, and then concluded that I had never heard of it. Good call too, because that thing turned out to be ungoogleable. Idk whether he made it up or whether it was an invention of his CS professor, but being transparent about such things has served me well. :-D
Examples of things that might worry you:
I think for me it’s mostly about what the other people in the room will think about me, not about consequences for me. I’m also afraid of playing games with friends or strangers for the same reason even though my blunders in such games wouldn’t realistically have any consequences for me. :-/
My training with actual interviews will have to wait though because I found a great ETG-oriented EA-run company that is basically my best-case employer. :-D My personal growth will have to continue not down the path of becoming braver but down the path of understanding gas optimization in Uniswap v3. ^.^
Thank you so much for all your ideas! (How is your work going? :-D)
I have thoughts on how to deal with this. My priors are this won’t work if I communicate it through text (but I have no idea why). Still, seems like the friendly thing would be to write it down
My recommendation on how to read this:
If this advice fits you, it should read as “ah obviously, how didn’t I think of that?”. If it reads as “this is annoying, I guess I’ll do it, okay....”—then something doesn’t fit you well, I missed some preference of yours. Please don’t make me a source of annoying social pressure
Again, for some reason this works better when speaking than in writing. So, eh, … idk.. imagine me speaking?? get a friend to read this to you?
(whatever you chose, consider telling me how it went? this part is a mystery to me)
So,
TL;DR:
The goal of interviews is not to pass them (that’s the wrong goal, I claim). The goals I recommend are:
Reducing uncertainty regarding what places will accept you. (so you should get many rejections, it’s by-design, otherwise you’re not searching well)
Practicing interviews. Interviews are different than actual work, and there’s skill to build there. So after interviews, I’ll review stuff I didn’t know, and I’ll ask for feedback about my blind spots. I have some embarrassing stories about blind spots I had in interviews and would never notice without asking for feedback. Like, eh, taking off my shoes and walking around the room including the interviewer 🫣 these are actual blind spots I had which are absolutely unrelated to my profession of software development
Something about the framing of “people who interview a lot beat others in getting better jobs”—and motivation to be one of those
Get yourself ice cream or so after interviewing
Important sub point: Positive reinforcement should be for “doing good moves” (like scheduling an interview, or like reviewing what you could do better), and NOT for passing interviews (which imply to your brain that not-passing is negative, and so if your brain has uncertainty about this—it will want to avoid interviewing)
Asking a close friend / partner / roommate what they think could work for you. They might say something like “play beat saber, that always makes you feel good” which I couldn’t guess
Sometimes people spend a lot of time on things like writing cover letters (or other things that I think are a wrong use of time and frustrating (and in my model of people: some part of them knows this isn’t a good idea and it manifests as stress/avoidance, though I’m no therapist)). I’d just stop doing those things, few things are (imo) worth the tradeoff of having more stress from interviews. It’s a tradeoff, not a game of “do interviews perfectly and sacrafice everything else”
1.a. and b.: Reframing it like that sounds nice! :-D Seems like you solved your problem by getting shoes that are so cool, you never want to take them off! (I so wouldn’t have expected someone to have a problem with that though…) I usually ask for feedback, and often it’s something like “Idk, the vibe seemed off somehow. I can’t really explain it.” Do you know what that could be?
2. I’m super noncompetitive… When it comes to EA jobs, I find it reassuring that I’m probably not good at making a good first impression because it reduces the risk that I replace someone better than me. But in non-EA jobs I’m also afraid that I might not live up to some expectations in the first several weeks when I’m still new to everything.
3. Haha! Excellent! I should do that more. ^.^
4. You mean as positive reinforcement? I could meet with a friend or go climbing. :-3
5. Aw, yes, spot on. I spent a significant fraction of my time over the course of 3–4 months practicing for Google interviews, and then never dared to apply anyway (well, one recruiter stood me up and I didn’t try again with another). Some of the riddles in Cracking the Coding Interview were so hard for me that I could never solve them in 30 minutes, and that scared me even more. Maybe I should practice minimally next time to avoid that.
Thank you so much for all the tips! I think written communication works perfectly for me. I don’t actually remember your voice well enough to imagine you speaking the text, but I think you’ve gotten everything across perfectly? :-D
I’ll only pounce on amazing opportunities for now and continue GoodX fulltime, but in the median future I’ll double down on the interviewing later in 2024 when our funds run out fully. Then I’ll let you know how it went! (Or I hope I’ll remember to!) For now I have a bunch more entrepreneurial ideas that I want to have at least tried. :-3
1.a and b.
This sounds like someone who doesn’t want to actually give you feedback, my guess is they’re scared of insulting you, or being liable to something legal, or something like that.
My focus wouldn’t be on trying to interpret the literal words (like “what vibe”) but rather making them comfortable to give you actual real feedback. This is a skill in itself which you can practice. Here’s a draft to maybe start from: “Hey, I think I have some kind of blind spot in interviews where I’m doing something wrong, but I don’t know what it is and a friend told me I probably won’t notice it myself and I better get feedback from someone else. Any chance you’d tell me more about what didn’t work for you? I promise not to be insulted or complain for not passing or anything like that”
2.
This is super common. Like, I’m not making this up, I had dozens of conversations and this is a common thing to worry about, and it’s probably true to many other people interviewing to the same position.
My own approach to this is to tell the interviewer what I’m worried about, and also the reasons that I might not be a good match for whatever this is. For example, “I never worked with some-tech-you-use”. If after hearing my worries they still want to hire me, that’s great, and I don’t need to pretend to know anything. I also think this somewhat filters for hiring managers that appreciate transparency (and not pretending everything is perfect), which is pretty important to me personally.
(also, reasonable managers understand you will need onboarding time, and if they don’t understand that—then I prefer they don’t hire me)
This all totally might be a Yonatan-thing, idk.
4.
Yeah
I think (?) I’d aim for something short that I could do right-after, so my brain will understand this is a positive reinforcement and not just an unrelated fun evening? This is just my own intuition. I guess it would work if I’d meet a friend and they’d keep saying “good job for interviewing! now let’s get you chocolate!” or whatever :)
I don’t really know, I recommend you trust your own introspection, I might be unusual here
5.
Eh, you might have (right now) downsides to applying and not having it work well. The downsides might be subjective or “technically wrong” but if you’re averse to applying with minimal practice, I would acknowledge that feeling and try to address it (or if you can’t—I’m not personally pushing you to apply to Google unprepared, if it seems scary or so).
Examples of things that might worry you:
a. “will google never invite you to interview again if you fail” --> You can check Google’s policy. I think they have a 6-12 months cooldown for people who didn’t pass, but you can apply again. Is this time too long? Maybe you don’t care at all? I don’t know, depends on your circumstances
b. maybe you’re not interviewing to dozens of places and so it (maybe correctly) feels like Google is your only chance? ( --> I’d recommend interviewing to dozens of places, to be clear :P )
I think a useful answer here would mainly involve listening to you which I can’t really do over text. If you want to brainstorm out loud here, I can try to contribute “textbook solutions” if I have them. Or you could do introspection with a friend, or we could talk, or none of the above! just trying to share how I’d approach this
:)
Oh, interesting… I’m autistic and I’ve heard that autistic people give off subtly weird “uncanny valley”–type vibes even if they mask well. So I mostly just assume it’s that. Close friends of mine who surely felt perfectly free to tell me anything were also at a loss to describe it. They said the vibes were less when I made a ponytail rather than had open hair, but they couldn’t describe it. (Once I transition more, I hope people will just attribute the vibes to my probably-unfortunately-slightly-imperfect femininity and not worry about it. ^.^ I just need to plant enough weirdness lightning rods. xD)
But he was US-based at the time, and I’ve heard employers in the US are much more careful with giving feedback than around here, so maybe it was just guardedness in that case.
I like your template! I remember another series of interviews where I easily figured out what the problems were (unless they were pretenses). I think I’m quite attuned (by dint of social anxiety) to subtle indications of disappointment and such. When I first mentioned earning to give in an interview, I noticed a certain hesitancy and found out that it’s because the person was looking for someone who has an intrinsic motivation for building hardware for supply chain optimization rather than someone who does it for the money. But in other cases I’m clueless, so the template can come into action!
Oh yes, I love this! I think I’ve done this in virtually every interview simply because I actually didn’t know something. One interviewer even asked me whether I know the so-and-so design pattern. I asked what that is, and then concluded that I had never heard of it. Good call too, because that thing turned out to be ungoogleable. Idk whether he made it up or whether it was an invention of his CS professor, but being transparent about such things has served me well. :-D
I think for me it’s mostly about what the other people in the room will think about me, not about consequences for me. I’m also afraid of playing games with friends or strangers for the same reason even though my blunders in such games wouldn’t realistically have any consequences for me. :-/
My training with actual interviews will have to wait though because I found a great ETG-oriented EA-run company that is basically my best-case employer. :-D My personal growth will have to continue not down the path of becoming braver but down the path of understanding gas optimization in Uniswap v3. ^.^
Thank you so much for all your ideas! (How is your work going? :-D)
I find your comments fun and authentic. I like your approach to voicing your concern that you don’t know something and it helps filter good managers.
“The goal of interviews is not to pass them (that’s the wrong goal, I claim). The goals I recommend are:
Reducing uncertainty regarding what places will accept you. (so you should get many rejections, it’s by-design, otherwise you’re not searching well)”
I get very anxious the closer I am to interview day. I started doing mock interviews to practice.
Shifting to reducing uncertainty/research vs passing seems helpful.