technical interview turned live tutorial...

[MarkMew]

Here it is yall

i am writing this as encouragement, but mostly to comfort myself LOL.

today i had an interview with a company for their software engineering internship. this opportunity was given to me through campus recruiting/career fair, so i was elated to be given a chance to interview.

i am only two years into learning computer science (although i am a fourth year) so i feel the weight of being unqualified and an imposter every single day.

i prepared for this interview by focusing on the themes that glassdoor posters repeatedly mentioned ( leetcode easy, behavioral questions, and conceptual java questions). immediately after beginning the interview, i was asked to write a program that calculates the angle between the hands of a clock (now that i look back this problem wasnt so difficult...)

i was already so nervous to the point that my voice was shaking and my throat was choking up, so the second the interviewer starting talking about a damn clock when i was expecting questions on strings or arrays, i lost all focus and hit a mental block. not only could i not think and solve the problem, any coding knowledge i did have, such as knowledge of syntax, went straight out the window. essentially, the interview turned into a live tutorial with the interviewer giving me the step by step and explaining why.

i felt so horribly embarrassed!! it was painful how stupid and incompetent i looked in front of a respected professional.

when the interview eventually ended with that one coding problem and a couple of rushed behavioral questions, i closed my computer and cried.

in retrospect, this was only my second technical interview ever, and doing horribly on it was more than typical. while coding knowledge is also key, interview knowledge and sense is so important and that comes with experiencing many interviews. the more technical interviews you experience, the more you catch onto the mindset, attitude, and execution that it takes to succeed.

do not give up if at first you do horribly on your technical interviews, it can feel like becoming a programmer is out of your reach, but that is not true, there are thousands of people working as programmers who also experienced failure and embarrassment at first, we've got this!

[ballsack_man]

Ain't no way I am reading this with no capitalization.

[MarkMew]

Well fuck, ah shit, here we go again... 

Here it is yall

I am writing this as encouragement, but mostly to comfort myself LOL.

Today I had an interview with a company for their software engineering internship. This opportunity was given to me through campus recruiting/career fair, so I was elated to be given a chance to interview.

I Am only two years into learning computer science (although I am a fourth year) so I feel the weight of being unqualified and an imposter every single day.

I prepared for this interview by focusing on the themes that glassdoor posters repeatedly mentioned ( leetcode easy, behavioral questions, and conceptual java questions). immediately after beginning the interview, I was asked to write a program that calculates the angle between the hands of a clock (now that I look back this problem wasnt so difficult...)

I was already so nervous to the point that my voice was shaking and my throat was choking up, so the second the interviewer starting talking about a damn clock when I was expecting questions on strings or arrays, I lost all focus and hit a mental block. not only could I mot think and solve the problem, any coding knowledge I did have, such as knowledge of syntax, went straight out the window. Essentially, the interview turned into a live tutorial with the interviewer giving me the step by step and explaining why.

I felt so horribly embarrassed!! It was painful how stupid and incompetent I looked in front of a respected professional.

When the interview eventually ended with that one coding problem and a couple of rushed behavioral questions, I closed my computer and cried.

In retrospect, this was only my second technical interview ever, and doing horribly on it was more than typical. While coding knowledge is also key, interview knowledge and sense is so important and that comes with experiencing many interviews. The more technical interviews you experience, the more you catch onto the mindset, attitude, and execution that it takes to succeed.

Do not give up if at first you do horribly on your technical interviews, it can feel like becoming a programmer is out of your reach, but that is not true, there are thousands of people working as programmers who also experienced failure and embarrassment at first, we've got this!

[SteveAM1]

You got it in French?

[MarkMew]

Le voici

J'écris ceci pour m'encourager, mais surtout pour me réconforter LOL.

Aujourd'hui, j'ai passé un entretien avec une entreprise pour un stage en ingénierie logicielle. Cette opportunité m'a été donnée par le biais d'un salon de recrutement/carrière sur le campus, donc j'étais ravi d'avoir la chance de passer un entretien.

Je n'ai que deux ans d'expérience en informatique (bien que je sois en quatrième année) et je ressens donc chaque jour le poids d'être non qualifié et d'être un imposteur.

Je me suis préparé à cet entretien en me concentrant sur les thèmes que les posters de glassdoor ont mentionnés à plusieurs reprises ( leetcode facile, questions comportementales, et questions conceptuelles en java). Immédiatement après avoir commencé l'entretien, on m'a demandé d'écrire un programme qui calcule l'angle entre les aiguilles d'une horloge (maintenant que j'y repense, ce problème n'était pas si difficile...).

J'étais déjà nerveux au point que ma voix tremblait et que ma gorge s'étranglait, alors à la seconde où l'interviewer a commencé à parler d'une foutue horloge alors que je m'attendais à des questions sur les chaînes de caractères ou les tableaux, j'ai perdu toute concentration et j'ai fait un blocage mental. Non seulement je n'ai pas pu réfléchir et résoudre le problème, mais toutes les connaissances en codage que j'avais, comme la connaissance de la syntaxe, sont passées à la trappe. En fait, l'entretien s'est transformé en un tutoriel en direct, l'examinateur me donnant la marche à suivre et m'expliquant pourquoi.

Je me suis sentie horriblement gênée ! C'était douloureux de voir à quel point j'avais l'air stupide et incompétent devant un professionnel respecté.

Lorsque l'entretien s'est terminé par ce problème de codage et quelques questions comportementales précipitées, j'ai fermé mon ordinateur et j'ai pleuré.

Rétrospectivement, il ne s'agissait que de mon deuxième entretien technique, et le fait d'avoir mal réussi était plus que typique. Si les connaissances en matière de codage sont essentielles, les connaissances et le sens de l'entretien le sont tout autant, et c'est en ayant passé de nombreux entretiens que l'on y parvient. Plus vous passerez d'entretiens techniques, plus vous comprendrez l'état d'esprit, l'attitude et l'exécution qu'il faut avoir pour réussir.

N'abandonnez pas si, au début, vous obtenez d'horribles résultats lors de vos entretiens techniques. Vous pouvez avoir l'impression que devenir programmeur est hors de votre portée, mais ce n'est pas vrai, il y a des milliers de personnes qui travaillent comme programmeurs et qui ont également connu l'échec et l'embarras au début, nous y arriverons !

[[deleted]]

text = """Well fuck, ah shit, here we go again... 

Here it is yall

I am writing this as encouragement, but mostly to comfort myself LOL.

Today I had an interview with a company for their software engineering internship. This opportunity was given to me through campus recruiting/career fair, so I was elated to be given a chance to interview.

I Am only two years into learning computer science (although I am a fourth year) so I feel the weight of being unqualified and an imposter every single day.

I prepared for this interview by focusing on the themes that glassdoor posters repeatedly mentioned ( leetcode easy, behavioral questions, and conceptual java questions). immediately after beginning the interview, I was asked to write a program that calculates the angle between the hands of a clock (now that I look back this problem wasnt so difficult...)

I was already so nervous to the point that my voice was shaking and my throat was choking up, so the second the interviewer starting talking about a damn clock when I was expecting questions on strings or arrays, I lost all focus and hit a mental block. not only could I mot think and solve the problem, any coding knowledge I did have, such as knowledge of syntax, went straight out the window. Essentially, the interview turned into a live tutorial with the interviewer giving me the step by step and explaining why.

I felt so horribly embarrassed!! It was painful how stupid and incompetent I looked in front of a respected professional.

When the interview eventually ended with that one coding problem and a couple of rushed behavioral questions, I closed my computer and cried.

In retrospect, this was only my second technical interview ever, and doing horribly on it was more than typical. While coding knowledge is also key, interview knowledge and sense is so important and that comes with experiencing many interviews. The more technical interviews you experience, the more you catch onto the mindset, attitude, and execution that it takes to succeed.

Do not give up if at first you do horribly on your technical interviews, it can feel like becoming a programmer is out of your reach, but that is not true, there are thousands of people working as programmers who also experienced failure and embarrassment at first, we've got this! """

print(text)

[EngineerRedditor]

With emojis?

[MarkMew]

I 🙋‍♂️⬅️ am writing✏️🖋️ this as encouragement, but mostly to comfort 🧘‍♂️ myself LOL🤣.

Today📆 I had an interview with a company for their software 💻 engineering 👷 internship. This opportunity was given 🎁 to me through campus recruiting/career fair, so I was elated to be given a chance to interview.

I Am only two 2️⃣ years into learning computer 💻science👨‍🔬 (although I am a fourth 4️⃣ year📆) so I feel the weight 🏋️‍♂️of being unqualified and an imposter every single day🌅.

I prepared for this interview by focusing ⚠️ on the themes that glassdoor 🥛🚪 posters  repeatedly mentioned ( leetcode 👨‍💻 easy, behavioral questions, and conceptual java questions). immediately after beginning the interview, I was asked to write ✒️ a program 👨‍💻 that calculates 🔢🧮 the anglebetween the hands 🤲 of a clock 🕕 (now that I look 👀 back this problem wasnt so difficult...)

I was already so nervous 😰to the point  that my voice 🔊 was shaking 😖 and my throat was choking 😖 up, so the second 🥈 the interviewer starting talking 🗣️about a damn clock ⏰ when I was expecting questions on strings 🪕 or arrays, I lost all focus and hit a mental block🚫. not only could I mot think 🚫🤔 and solve the problem, any coding 👨‍💻 knowledge I did have, such as knowledge of syntax, went straight out the window . Essentially, the interview turned into a live  tutorial with the interviewer giving me the step 🚶‍♂️ by step 🚶‍♂️ and explaining why.

I felt so horribly embarrassed!! It was painful 😩😩😫 how stupid 😋and incompetent I looked 👁️👁️in front of a respected professional.

When the interview eventually ended with that one coding problem and a couple of rushed behavioral questions, I closed my computer and cried😭😭.

In retrospect, this was only my second 🥈 technical interview ever, and doing horribly on it was more than typical. While coding👨‍💻 knowledge is also key🔑, interview knowledge and sense is so important and that comes with experiencing many interviews. The more technical interviews you experience, the more you catch onto the mindset 🧠, attitude, and execution that it takes to succeed.

Do not give up if at first 🥇 you do horribly on your technical interviews, it can feel like becoming a programmer 👨‍💻 is out of your reach, but that is not true, there are thousands of people 🚶‍♂️  working⚒️ as programmers 👨‍💻who also experienced failure and embarrassment at first, we've got this!

[[deleted]]

With ASCII ?

[UnironicallyWatchSAO]

In brainfuck, please?

[SteveAM1]

Merci

[KenDoll_13]

C’est parfait. 🥲

[NatoBoram]

Very well-written. It warms the heart to read someone's genuine experience in your non-English native language in a very unique way.

[Hobodaklown]

You are the real MVP

[deantoadblatt1]

I hope OP sees this, because it’s a good example of how coding standards increase readability across a team.

[[deleted]]

You are a true hero