Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

How I Conduct Technical Interview


Published on

This webinar by Dmytro Mrachkovskyi (Consultant, GlobalLogic) was delivered at Java Community Webinar #4 on November 12, 2020.

Webinar agenda:
- Why conduct technical interview
- Technical interview structure
- The basis of the topic for questions

More details and presentation:

Published in: Technology
  • Be the first to comment

  • Be the first to like this

How I Conduct Technical Interview

  1. 1. SLIDESMANIA.COM How I conduct interview
  2. 2. SLIDESMANIA.COM Dmytro Mrachkovskyi HELLO! Lead Software Engineer GlobalLogic Ukraine
  3. 3. SLIDESMANIA.COM Disclaimer If needed
  4. 4. SLIDESMANIA.COM Overview Why to conduct interview Interview structure Themes and areas Q&A
  5. 5. SLIDESMANIA.COM What to expect from this techtalk For you Hope you’ll find some useful tips and hints on how to conduct interview For me Psychotherapy session
  6. 6. SLIDESMANIA.COM ONE Why to conduct interview
  7. 7. SLIDESMANIA.COM Why we need interview sessions Examine candidate`s tech and soft skill Check if candidate fits team mentaly Prove yourself you are better
  8. 8. SLIDESMANIA.COM Interview format Structured Go through prepared list of topics and areas you what to discuss. Not structured Just start discussing some random (but prepared) topic trying to cover everything you are interested in.
  9. 9. SLIDESMANIA.COM Pros and Cons Structured Easy to adopt and conduct Not Structured Hard to cover all areas in time Easy to give formal feedback Informal Harder for interviewer Easier to cover a lot of topics Too formal Harder to give formal feedback
  10. 10. SLIDESMANIA.COM Evaluate not only what people say but also how they say it
  11. 11. SLIDESMANIA.COM Key points to pay attention on Correctness (if applicable) Clarity Structure
  12. 12. SLIDESMANIA.COM Correctness “volatile” forbids caching “volatile” guranties read of the latest successful write What does “volatile” modifier mean
  13. 13. SLIDESMANIA.COM Clarity ArrayList, TreeSet, LinkedHashMap, etc List guarantees order, Set guarantees uniqueness ArrayList, TreeSet, LinkedHashMap, etc
  14. 14. SLIDESMANIA.COM Structure ArrayList, Set, LinkedHashMap, etc Iterable, Collection, List, Set, Queue, Map Name interfaces from java.util.collections
  15. 15. SLIDESMANIA.COM Ask same questions to Juns, Mids, Seniors but expect different answers
  16. 16. SLIDESMANIA.COM TWO Interview structure
  17. 17. SLIDESMANIA.COM Main sections of the interview Greeting and small-talk Project introduction Soft skill interview Tech skill interview Q&A session
  18. 18. SLIDESMANIA.COM Greeting and small-talk Greeting Introduce yourself, ask the candidate to introduce himself. Offer cup of tea/coffee, glass of water. Make a short introduction to the interview process Small-talk Spend 2-3 minutes on some random (non-technical) talk. E.g. how was his trip to the office, did he find good place to park his car, etc.
  19. 19. SLIDESMANIA.COM Do not be an enemy to the interviewee. You are on the same side.
  20. 20. SLIDESMANIA.COM Project introduction Spend 5-10 minutes describing the project. What is the business idea, how company and teams are structured. What are the process used. Describe main tech stack the project is built on
  21. 21. SLIDESMANIA.COM Soft skills interview Can be done by project manager Usually they ask questions like: Why did you leave your current project or where you see yourself in 5 years, blah-blah-blah Can be done by me In this case I do not extract it in a separate section but trying to make a picture during the tech interview part
  22. 22. SLIDESMANIA.COM Tech interview Will be covered in details in the next section
  23. 23. SLIDESMANIA.COM Q&A session Leav about 5 minutes to let the candidate to ask any questions he has. Avoid giving direct feedback to the interviewee if ask one.
  24. 24. SLIDESMANIA.COM THREE Tech interview
  25. 25. SLIDESMANIA.COM General structure for the next slides For each area to discuss I will highlight three main points Who - June, Mid, Senior Why - What is the value of the question Question examples
  26. 26. SLIDESMANIA.COM OOP Who - Junior - Middle - Senior - Tech Lead This question should be ask to candidates of any level Why OOP is the fundamental software development process for Java. Candidate should know and understand its main principles and how they help us Examples Describe main OOP principles and, the most important, how they help us to develop software
  27. 27. SLIDESMANIA.COM Java core/Java 8-11 features Who - Junior - Middle - Senior - usually only Optional and Stream API - Tech Lead - usually only Optional and Stream API Why This is the basics of the engineer day-to-day work. If candidate struggles to answer this questions it is doubtful he/she will be able to execute even simple tasks Examples - What is “static”, “final” - Override vs overload - Exceptions - Optionals and Streams API
  28. 28. SLIDESMANIA.COM Collections Who - Junior - Middle - Senior - Tech Lead Why In day-to-day we mostly work with some data that we need to store, retrieve or process. Engineer should be able to select correct data structure for the task he is implementing Examples - Interfaces in java.util.collection - List vs Set - How HashMap works
  29. 29. SLIDESMANIA.COM Concurrency Who - Middle - really - Senior - Tech Lead Why MId and Senior engineer should be able to work with concurrent environments, understand how it build under the hood, implement such structures by themself or choose correct lib/framework Examples - What does “synchronisation” means - What does volatile means - Locks - Atomics/CAS - etc.
  30. 30. SLIDESMANIA.COM Data stores Who - Junior - basics - Middle - Senior - Tech Lead Why MId and Senior engineer should be able to work with different data storages, understand how it build under the hood, its pros and cons, which data store to chose. Examples - SQL vs NoSQL - CAP theorem - SQL - Transactions
  31. 31. SLIDESMANIA.COM JVM / GC Who - Middle - rearly, only basics - Senior - Tech Lead Why Senior engineers and tech leads should be able to troubleshoot issues related not only to the application code or libs used but also related to JVM it self, as well as work on performance optimization of the application Examples - Name GC you know/work with - How JVM memory is structured - JIT - native calls/intrinsics - bytecode
  32. 32. SLIDESMANIA.COM Troubleshooting Who - Senior - Tech Lead Why Senior engineers and tech leads should be able to troubleshoot issues with re running app in production when trivial methods (like app logs) fails Examples - Java monitoring tools (JMC, jConsole) - heap dumps - Useful JVM params - OS specific monitoring tools
  33. 33. SLIDESMANIA.COM Frameworks Who - Junior - basics - Middle - Senior - Tech Lead Why Depending on the project needs engineer should be able to work with different frameworks, choose correct one to solve particular problem. Examples - Spring - Hibernate
  35. 35. SLIDESMANIA.COM Thank you for attention