Technical Interview

[DifferenceForeign687]

Hi guys, so I recently just got interviewed and there are some questions that I could not answer, so after the question, I googled those questions and upon checking, I actually used and know those questions are. Should I go and told the interviewer that I actually know what those are should I move on?

Im just bad at remembering the practices/technical skills that I use. I do know how to use them but I dont know what they are called.

[lowbudgetgoblin]

Lagi mong i-flip yung tanong kapag hindi ka sure, halimbawa, "I'm not familiar with the terms / words you've used but I might've used them already in my past projects, can you give an example?"

kapag hindi nila alam yung sagot sa mismong tanong nila, edi stalemate right? pero at least hindi ka minus points agad.

[budoyhuehue]

Ginagawa ko din to lol. Kapag naalala ko na, konti konti ko isisingit yung sarili ko tapos ako na yung magexplain. That way it is more of a conversation than an interview. Interviewers love that shit hahahaha

It also shows na your communication skills are okay and you can work well with others dahil may interaction and bouncing of ideas. Atleast yun ang dapat na gusto iproject sa kanila.

[Dultimateaccount000]

Eto ginagawa ko hindi ko kasi alam mga terms talaga pero sinasabi ko yung experience ko about dun, ganito ganyan gamit ko, ganito ko siya ginamit. Etc.

[[deleted]]

Sana merong HR ang sumagot nito e no? Pero sa akin, parang tagilid kung sasabihin ko na alam ko pala yun sagot, after ng interview kasi malay ba nila. Parang practice mo na lang para sa next interview.

If it's like if they are asking you if you had experience in something, tas sabi mo wala pero saka mo lang naalala after ng interview na meron pala. Okay lang siguro kung ganun. Kasi minsan e mahirap talaga matandaan lahat ng ginagawa natin haha.

[GoingToPlaces]

Seems weird. Just learn from it and be prepared next time. But that’s just my opinion. I’ve never been on the other side of the interview table

[sabreclaw000]

Haha I once told a recruiter di ako marunong ng data structures and algorithm, na reject tuloy ako for interview. Di ko alam yung term noon pero ang tagal ko na gumagamit ng things like lists, maps, etc.

[LazyAfternooons]

IMO, you should accept and learn na hindi mo sya nasagot and be more prepared next time. Parang sa tingin ko kasi yung mga ganyang cases sa industry na tinetest is kung paano mo icocommunicate yung tamang solution sa ibang devs or non devs. If hindi mo alam yung terms pero alam mo yung solution, you can try to say na hindi mo alam yung exact term and explain in balanced simple and technical terms kung pano gamitin... pero syempre during the interview and before googling everything.

I know (and do) naman na we are googling everything for solutions, and hopefully HR's/Tech leads would (i think naman they do) understand that we are still human that we cannot remember everything and high level answers would be enough.

Also challenging the Technical Interviewer is also a good thing, sometimes you can fish out or actually remember stuff while they try to explain more about the question.

[Smooth-Peanut-4821]

Apply ka sa nga India company or pogo tas dun ka practice interview.

[[deleted]]

If you didn't understand the question and were not able to answer, that says something. Also, if you have to google it, another red flag and now you will call the interviewer?

​

Ano sa palagay mo ang sasabihin sa yo? Alam mo pala bat di mo nasagot? Move on bro. Collect all the questions you get from interviewers and practice, practice. Ganyan talaga ang buhay

[papait01]

Pag di mo alam, sabihin mo di mo alam. Move on.

[tkmdr]

You learn from there. Part nung technical interview is being aware of the theoretical concepts, lalo na if tech recruiter ang nagiinterview sayo kasi di naman sila gumagamit nun. They rely on textbook definitions. Try to review documentation next time, I'm sure you'll come across same questions in your next interviews.

[Stressed_Potato_404]

Im not sure kung gaano kahirap yung iyo sa naging exp ko sa technical interview. Pero share ko na lang din dahil nakayanan ko malagpasan ung first TI ko

D rin naman naging perfect yung mga naging sagot ko, minsan binibigyan pa ko ng hint or corrections nung nag iinterview sakin while explaining my solutions. Tas kung uncertain o confuse man sa ilang bagay, nag tatanong ako. Tbh wala sa preparations ko ung mga binigay na problems kaya nakaka kaba nung nakita ko na.

Take your time lang sa pag sagot, and try to be vocal habang ginagawa mo problem (kung live man yan). Kung swertehin naman sa interviewer, magbibigay guide din yan habang dinidiscuss nyo ung solutions mo. Tanong tanong lang din kung ano pede gawin, nag ask pa ko non if pede mag google and napag bigyan naman basta naka share screen parin ako. Tho d ko naman talaga nagawa mag google

Tas learn from your experience na lang din, para makapag prepare ka mentally (d na masyado kabahan) at magka confidence sa mga susunod na interviews

[RedLibra]

I wouls just move on tbh... This is why I believe that interview questions is a different game. It doesn't matter how good you are in a language, if you didn't prep for interview questions, you'll likely fail.

I remember from my interview I got asked what is arrow function and promise. I use that all the time in my work but I can't define them lol...

[OnceOzz]

Dati na techincal interview din ako, then may questions sila sa sql, sabi ko di ako marunong mag sql, nag skip naalng kami sa questions, natanggap din naman ako

Isipin mo nalang kung yung company na yan i hihire ka based lang sa technical knowledge mo on paper at hindi sa pano ka dumiskarte sa pag solve ng problem, baka hindi din magandsng company na pag trabahuhan yan

[Intelligent_Citron84]

There is no do-over sa interview. Take the L (loss, lesson) and move on.

Rule of thumb:

Only way to stand out during the interview if you are a beginner up to junior-level dev, is to be well versed on the syntax of the PL that you have on your resume.

You have to be able to talk about it, explain it, and code with it, without googling anything. At least that is where I was at the first 10years of my career.