What is a "weak yes" and what is a "weak no"
I watched the DS&A course on Taro and I thought the video on what a "yes" and a "strong yes" mean was really helpful.
I was wondering if the same analysis can be done for what a "weak no" and a what a "weak yes" mean? I think this comparison would be helpful since it gives us an understanding of the small details that can push someone between passing and failing territory.
Another question I have is that I've finished questions with optimal time complexity but I still fail the interview. So under what circumstances would candidates get a "weak no" (or even "no") even with an optimal solution? This is obviously a super broad question, so I tried breaking it down into several categories:
Communication:
- Clarifying questions
- Explaining thought process
Problem Solving:
- Needing hints
- Time/Space complexity analysis
Coding:
- Debugging
- Code quality
Verification:
- Test suite composition
![Senior Software Engineer [E5] at Meta company logo](/_next/image/?url=https%3A%2F%2Ffirebasestorage.googleapis.com%2Fv0%2Fb%2Ftech-career-growth.appspot.com%2Fo%2Fcompany_logos%252Fmeta.jpeg%3Falt%3Dmedia%26token%3Da7a5bcc0-e178-4b5b-b71e-09bf6c6aefae&w=48&q=75){kind=small}
![Entry-Level Software Engineer [L3] at Google company logo](/_next/image/?url=https%3A%2F%2Ffirebasestorage.googleapis.com%2Fv0%2Fb%2Ftech-career-growth.appspot.com%2Fo%2Fcompany_logos%252Fgoogle.jpeg%3Falt%3Dmedia%26token%3D780356ef-3efc-4728-9eb4-d909b75bb4a6&w=48&q=75){kind=small}
Discussion
(3 comments)- 1
3 months agoEngineer @ RobinhoodThere's a lot going into the mind of interviewers, but this is what usually goes on in mine for the 2 cases.
- Weak no: candidate's strengths and candidate's weaknesses are roughly equal. Round down to no because I didn't have strong enough reads on the candidate's strengths to be convinced they can code indepedently.
- Weak yes: candidate's strengths and candidate's weakness are roughly the same. Round up to yes because there is some mix of strengths that convinces me that candidate has good enough fundamentals around coding, but just didn't quite get this particular problem.
- 03 months agoSoftware Engineering InternTaro Community
What would be some factors that would push a candidate to one side or the other?
- 03 months agoEngineer @ Robinhood
The main thing for me is the candidate has a clear line thought: am I able to follow along with where they're going? Or are they more often than not rambling and/or typing random stuff.
