Saltar al contenido
Underc0de /foro

What do I evaluate in technical interviews?

🌐 This is an automatic translation of a topic from Underc0de, the largest Spanish-speaking hacking and IT community. Read the original (Spanish) and reply →
Alex ·
Los enlaces son solo para miembros. Registrate o iniciá sesión
<br /><br />Hi, I've been doing technical interviews for a while now, for two different companies, and here I'd like to share what I evaluate/ask in a technical interview:<br /><br />I start the interview by explaining who I am and what my background is, where I've worked and what I do at the current company I'm interviewing for.<br /><br />I ask how things are going at their current job, if they have one, and why they're looking to change, what they dislike and what they like (to learn a bit from other people's failures and successes)<br /><br />Then I start the evaluation by asking Los enlaces son solo para miembros. Registrate o iniciá sesión /><br /><br />
    <br />
    • Data structures (hashmaps, lists, etc.)
    <br />
    • OOP (inheritance, polymorphism, overloading, statics in their variants, finals in their variants).
    <br />
    • I ask how reactive programming works.
    <br />
    • Depending on seniority, I ask about design patterns and why Singleton is used instead of a purely static class.
    <br />
<br /><br />If it's for somewhat more recent versions, Java 8+, I start asking things like:<br />
    <br />
    • How and where to use Optionals
    <br />
    • How the streams API works in Java.
    <br />
    • How lambdas work
    <br />
<br /><br />Spring? I ask about the different parts of Spring:<br />
    <br />
    • Spring security
    <br />
    • Spring data, JPA,
    <br />
    • Differences between different types of controllers (RestController, Controllers for sockets, ETC).
    <br />
    • * If Hibernate is required (things like what an ORM is, how lazy loading works, and what the difference is with JDBC templates).
    <br />
    • * if required, I ask about JSP, JSF, Thymeleaf
    <br />
<br /><br />I ask whether they've used Maven/Gradle before and how they work.<br /><br />If required, I ask:<br />
    <br />
    • whether they've consumed any SOA,
    <br />
    • whether they've built any SOA
    <br />
    • how WSDLs work
    <br />
<br /><br />Then I ask whether they've used microservices<br />
    <br />
    • How a REST API works
    <br />
    • How JWT works
    <br />
    • what advantages JWT has compared to Http Session, and what disadvantages
    <br />
    • Whether they've used GraphQL and how it works
    <br />
<br /><br />Then I move on to databases:<br />
    <br />
    • Which databases they've used
    <br />
    • Some SQL things, like joins or what a view is and when to use it.
    <br />
    • Whether they know non-relational ones, how these DBs work and how they differ from relational ones
    <br />
<br /><br />Then, if it's for a microservices architect, I ask about other matters:<br />
    <br />
    • Have you used Redis or similar? When is it used, how would you implement a cache
    <br />
    • How Elastic works, when to use it
    <br />
    • How the pub/sub pattern and message queues work, what problems there could be with the order in which messages are received, and how to solve them.
    <br />
    • How circuit breaker works and why you use it
    <br />
    • anything else that occurs to me to ask at the moment.
    <br />
<br /><br />Then I move on to testing:<br />
    <br />
    • Do you know what TDD is and how it works?
    <br />
    • Describe to me an example of what the development process would look like using TDD
    <br />
    • Have you used JUnit, TestNG, cucumber, mockito?
    <br />
    • Obviously I ask for details on how to use those technologies.
    <br />
<br /><br />Finally I add questions about <br />
    <br />
    • Git
    <br />
    • Git flows
    <br />
    • Pull request
    <br />
    • Types of PR merges such as squash
    <br />
<br /><br />If AWS or agile questions are required, I add them at the end.<br /><br />End of questions.<br /><br />
<br /><br /><br />At this point in the interview several things may have happened: the interviewee may have been very descriptive and elaborated a lot, in which case I skip some points (if I see they've already mentioned them, and I try to reduce the number of questions to harder things so I don't have to ask so much), since I try to keep the questions under 45 minutes while covering all the topics.<br /><br />When the interviewee doesn't know some technology or answer, I try to explain the technology to them, or give them a well-summarized answer so they can take it as a base, walk away with an idea and expand their knowledge later.<br /><br />The idea of my interview is to do a 360 sweep across all aspects of programming, see the level in each one, and make sure the interviewee takes away something they didn't know from the interview and that it wasn't just a set of questions, and if they can teach me something, even better.<br /><br />After the questions, I give feedback on my technical perception, making clear that it's not an answer from the company but my opinion and the feedback I'm going to give HR so they can continue the process; this way the interviewee leaves at ease knowing what I told HR, and from then on it's up to the company how to proceed.<br /><br />And to close the interview I usually ask the interviewee for feedback on the interview, to know whether they found it tense, boring, dynamic or what their perception was, in order to improve the evaluation process in the future.<br /><br />At all times I try to be dynamic and put the interviewee at ease, explaining that no question is a blocker, and that answering wrong or saying they don't know isn't a bad thing, but rather improves the accuracy of our picture of their knowledge.<br /><br />As a tip: interviews are not a school exam, nor is the intention to show how little, average or much the interviewee knows, but simply to gather information about their level of knowledge without making them nervous or torturing them.<br /><br />Then, depending on the position they're applying for, there are other stages related to putting together a solution and defending it.<br /><br />I'm not a big fan of challenges; although they're very illustrative, they consume a lot of the dev's time, and I think it's unfair that, just so we can evaluate them, we require them to do a challenge.<br /><br />Regards.<br /><br />If you want to chat about something, have questions or whatever, you can almost always find me in the chat embedded in the forum (which is an IRC) or from an IRC client in the #underc0de channel at irc.hirana.net<br />
xL00Px ·
Thank youuuu, this is going to be really useful to me
juampi.avila ·
Excellent info Alex, especially for us newcomers. Super important to know what happens in an interview. Thanks!
ANTRAX ·
Great contribution Alex!! It's excellent!!!<br />Now I'm waiting for one with the possible answers!! hahaha
Marcos Funes ·
Thanks a lot Alex, a thousand thanks!
Coder inked ·
Spectacular contribution, thanks!!
SabriBus ·
good advice, very complete, thanks!
jmpkb8-24 ·
Very good info Alex! Much appreciated
Brian007 ·
You're awesome, thanks!
Alex ·
Well, you're welcome, I thank everyone who replied to my post. What I would like to clarify, though, is that not all interviews follow that format or use those questions, but that's how I do interviews.<br /><br />
Cita de: ANTRAX en Febrero 18, 2022, 12:40:33 PM<br />Aportazo Alex!! Esta excelente!!!<br />Ahora espero uno con las posibles respuestas!! jajaaj<br />
<br /><br />that's cheating!
FernandoCabrera ·
Great contribution!! Could you tell us what the goal is, or what one should answer, to questions like: Expected salary? Where do you see yourself 5 years from now? Or any advice you can give us on how to answer some other typical interview question that at first sounds like a trick question? Thank you very much  :)
Grupo de WhatsApp