Skip to main content

Job Interviews

 All of us reach a moment in career when we need to pass interview. It may be tough, stressful process that we want to finish faster. Personally, I feel enthusiastic about interviews. Why? Let me share my viewpoint in this post (when I say 'interviews' it is mainly about 'engineering job interviews'). 

Initially, I divide job interviews into 2 categories: 

  1. external - when you want to get into a new company
  2. internal - when you want to pass an interview for promotion inside your current company.
 Despite to the category, you of course need a solid technical preparation. Everyone has own approach to technical preparation while I may suggest to write key points by hand. The purpose is not to reread these records later but mainly to remember the information in a structured format as we structure records in a paper. I will not write about resources for preparation as different position and companies have different requirements. Just google it, and do some research.  

What about time? I also divide interviews by preparation time into 2 categories: 
  1. Regular - when you you different sources (books, documentation, blogs, videos), reinforce with examples/solved problems. 3 - 6 months.
  2. Accelerated - when you learn mainly from documentation and blogs specific techs/tools. 1 - 2 moths.
Rarely, any candidate fully satisfies all requirements for job position. Interviewers and hiring mangers also understand it whereas they often choose best matching candidate, not the "best". Interview is process where you are examined 20% from 100% of what you know/what is required. Therefore, it is important to keep the balance between the width and depth of knowledge. Try to cover wider list of required topics and do not deeply dive into a specific topic unless it is specified in job description. During the interview stop thinking that you are being examined, instead try to build the communication in a way where you and interviewer just discussing about different topics. It helps you to release the stress and interviewer may feel sympathy due to your confidence. 

So, why do I like to attend interviews as an interviewee? Firstly, it is the fastest and most transparent way of objectively testing my knowledge and competence. Moreover, soft skills interviews encourage me to develop my communication and management skills. Finally, I just like to talk with someone who is more experienced and has wider vision. 

At the end, I recommend you to apply for interviews more frequently, even if you are not planning to work for that company. 


Comments

Post a Comment

Popular posts from this blog

A little bit about myself

Let's get acquainted! Junior student at Inha University in Tashkent, Software Engineer at Exadel, web development enthusiast, and just a cool guy😅. But, you can just call me Abdujabbor. In this blog we will talk about development, engineering, programming, and IT in general. If words like Frontend, SOLID, CI/CD do not scare you, you are in right place. If these words still scare you, stay tuned anyway, it is the best time to start.  In the first post, I will talk about my experience in a programming, and briefly introduce to technologies I used and my interests. My first experience in programming was in high school with C++. Like a true oldschool programmer I decided to start with low level programming language(PL),  and also because it was the only non-fiction book I found at home while I was sick for a month. Reading the book and writing code was quite fun and challenging. When my first program successfully compiled and showed output I felt so satisfied, and understood what prof
Post a Comment
Read more

How? Where? When?

 This post will(or at least tries to) answer to the question from the title in context of starting career in IT.  To start with, let's discuss some common misconceptions: You need to have an inborn talent to become IT specialist - IT jobs are nothing but regular jobs as jobs in Medicine, Sport or Law. And like doctors, sportsmen or lawyer you need to be engaged to what you do in order to become a qualified specialist.  You need to have full technical knowledge to work in IT - image of geek programmers is left at 60s. Now, IT is more than just development software. You may be an accountant, HR manger, recruiter, project manager, QA, consultant, and still work in IT. For this positions you do not need to fully understand college course of mathematics. Taking into consideration recent trends, even for engineers soft skills and adaptability may be more preferable than specific technical skills.       How to start? There plenty of resources on the web that teach specific skillsets req
Post a Comment
Read more

OOP from non-technical angle

 If you have been exposed to software coding/designing  then you probably have heard about OOP. OOP - Object Oriented Programming, is a programming paradigm that builds the structure of application and handles communication between modules by the usage of classes and objects.  Now, in simple words. Let's start with comparison. There are other programming paradigms as Functional programming or Procedural programming . So, why OOP is overwhelmingly popular compared to other paradigms whereas almost all popular programming languages(PL) are either fully designed based on OOP concepts or partially supports it.  First of all, OOP is one of the most researched and consistent paradigms(snowball effect). Where have it started? The main influencers of the start of hype around OOP were big tech companies and PLs they primarily used. Microsoft with C++ (later with C#), Oracle with Java, Apple with Objective C. But, we still have not found the root reason. Why these companies have chosen/desi
Post a Comment
Read more