Have you ever observed your Interview before?

Narendra Harny
6 min readDec 15, 2020

A few essential points for the interview that I have researched, and the details, are experienced by many of the people connected with me.
I reached a conclusion where I have some points to write as suggestions for the better interview.

Photo by Clay Banks on Unsplash

This article has details about how one can observe their interviews.

Here are the three points which you should observe in your interviews after reading this article.

  1. What is the question chaining in interviews?
  2. How to observe the interviews with 100% presence of mind.
  3. How to keep a positive impact while giving each answer.

I will use Python programming language topics as a reference for describing “What are Questions Chaining?”.

If you do not belong to the Python society!!!

Don’t worry

The topics & concepts I have used are relative to most of the programming languages, and I believe, anyone from a non-programming background also can understand what I want to explain.

Suggestions: Please concentrate on bold-italic words in answers, and please read the notes associated.

Let's start →

Assume you got the first question, “What are the Python features?” and the possible answer is below.

1. What are the Python features?

The possible answer will be given:

  • Python is an interpreted language.
  • Python is a dynamically typed language.
  • Python is an Object-Oriented programming language.
  • Python does not have access modifiers like (C++ and JAVA, Public, Private, Protected)
  • Python has a large amount of Library support.
  • Python is easy to use and provides ways to be more productive as a Programmer.

After answering the first question, The observation begins.

What do you think? can you guess what is the next question?

Yes with a 50% probability, I will make it easy!!!

  1. The second question will be asked on the core keyword you have used in the previous answer.
  2. Or It will be a different or a new question on a different topic.

Let's find the core keyword used in the answer.

Interpreted, Dynamically typed, Object-Oriented, Access modifiers, library support, Productive as a Programmer.

If the first case is true then the possible second questions will be related to the above keywords.

Considering the keywords, “Interpreted ” is preferred, and this question has arisen from the prior answer so, I am heading it as 1.1 and see the further interview discussion on the chain of questions [1.1], [1.1.1], [1.1.2]

1.1 What is the difference between an interpreter and a compiler?

Possible Answer: The interpreter translates the code line by line.
If line number 11 has an error interpreter will not move to line 12, whereas the compiler compiles the entire program collectively.

1.1.1 So Which one is faster?

Possible Answer: An interpreter is faster in analyzing the code and slower in execution. The compiler is slower in analyzing the code but faster in execution.

Conclusively interpreter is slower, and the compiler is faster.

Here in this answer, you marked the information as a statement that An interpreter is slower & a compiler is faster.

So be ready to explain a little further on this topic for some whys?

The next possible question would be →

1.1.2 If the interpreter is slow, then why does Python use an interpreter instead of a compiler, and why does even any other language use an interpreter?

Note:

  • The answer to this question is an opportunity to make the first positive impact.
  • Saying don’t know or the wrong answer will have versa negative impact too.
  • This Kind of question at level 3 down, I mean [1 →1.1 →1.1.1 →1.1.2] is a decision-making question for an interviewer to be positive or negative on you.

Possible Answer: Python does require a compiler to execute Python programs, but when we relate Python execution with other compiled languages, then we think it is an interpreted language.

Conversion of high-level languages to its CPU-understandable instruction set is necessary, and that can be done either by the compiler or interpreter.

Compiler Converts high-level code to machine bytecode, to do this, It checks for its syntax first and converts the whole program to machine or CPU-understandable bytecode.

The interpreter takes each expression or line of code converts it to machine code, and executes it. If any line has a syntax error, interpreters throw an error only when that line is analyzed.

Conclusively, Python is a “COMPILED INTERPRETED” language.

To prove this concept:

When the Python program runs.

  1. First, The code syntax will be analyzed.
  2. Second, It compiles and converts it to bytecode, and directly bytecode is loaded in memory and then compiled bytecode interpreted from memory to execute it

If you have observed the Python execution, then you might see the .pyc file generated for other modules used in your main module.
The .pyc file is the compiled version of the other module program.

Note:

  • The first question chain is completed, successfully.
  • Mostly after this kind of discussion, there won’t be further questions asked on the same topic.
  • It is not necessarily always each question will be chained till level 3 down.
  • We got a few more keywords from the first answer, and there might be a few questions may arise from them.

1.2 What exactly is the meaning of dynamically typed? ( keyword- dynamically typed)

1.3 What features does Python have for access modifiers? (Keyword- access modifiers)

As Python uses single “_” and doubles “__” instead of access modifiers.

1.3.1 Here questions may arise on using the members with practical examples in code so be clear about using “_” and “__” practically.

For: Create two classes and try accessing the variable and functions as public, private, and protected.

Note:

  • If all the above topics are attempted well, 7 to 10 minutes are passed.
  • Here is the time when the context of the first question will shift for the second case I mentioned above.

I hope by using the above example I have explained clearly what is question chaining, and how you should observe the interview.

I would like to write some conclusive points that will definitely improve your confidence for your next interview if followed properly.

  • Understand what the interviewer desires to understand from you because often obscure questions will be asked to examine, whether you are fully knowledgeable of the subject or not.
  • You can shape the interview by placing weight on keywords that you are self-confident about and often you will get your next question as an opportunity for the same.
  • Providing a real-time use case, writing code on paper, and designing flow charts, and other diagrams are for establishing a positive impact.
  • If you will be observing the interview as I described above then It will help to be 100% attentive in an interview
  • If answers are simplistic and clear then one can bypass a lengthy conversation on question chaining also. do it when any topic comes on you are not confident enough.
  • If you think It will be easy for you to explain in diagrams or code please go ahead and do that.
  • When the context changes concerning moving on to a different question, remember this is a fresh opportunity to keep an impact.
  • The initial impact should be positive always.
  • You can rate your interview by calculating how many times you think you made a positive impact.
  • The next question comes from your prior answer until the context of that question is not completed, so be centered.
  • Every statement will make an impact either positive or negative.
  • Making a bit negative impact on a very high-level level of questions according to your level of experience might be acceptable sometimes for some interviewers, but a negative impact on a basic question won’t be acceptable.
  • No interviewer will be demanding, you should be 100% informative and accurate in all the subjects, so if anything you don’t know please don’t try to describe it incorrectly.
  • When you get a chance to explain something on paper please consider that as an opportunity.
  • Ask the feedback at the end of the interview, It might not be important for you when you get selected. But It will be most important to know what you should improve.
  • Yes, of course!!! If the preparation is well before the Interview, If you will attempt interviews without preparing well and without a positive mindset then an unnecessary rejection will make you disconcerted. So don’t do it at all.

Hope this article will help you with your next interview, Please provide feedback in the comment section if any points have to be added to this list.

Thanks for Reading! If this article was helpful. Please hit the clap!

Follow on medium https://medium.com/@narendra147h

Connect on Linked In: linkedin.com/in/narendraharny

Please Follow & subscribe to Make Android Publication by Narendra K H for prompt updates on Android platform-related blogs.

Thank you!

--

--

Narendra Harny

Connect on https://medium.com/make-android | Write On, Android AOSP & Applications | Python | DevOps | Java | C++ | Kotlin | Shell | Linux | Android Auto | IVI