Interview tips for full time

[oneway]

Full time ki try cheyalanukuntuna and have experience as Full stack java developer but full time interviews ante konchem nervous and how to overcome and prepare for that

[JANASENA]

intha exp unchukoni nervous ante ela baa cheppu. okato rendo interviews isthey ade vachesthundi dhairyam and job kooda ATB

[JANASENA]

calling @Amrita

[HugoStrange]

behavioral questions chusuko, be prepared with examples. Appatlo nenu ala chesa ela chesa aa situation lo ani. 

[oneway]

konchem coding ante bhayam undi bro spontaneous ga rayamante i cant and anni full time interviews lo do they ask to write the code

[WHAT]

Leetcode 

[Amrita]

Opika unte 

Below and attached is some information to help you prepare for the interview. Please review carefully.

After reviewing my prep material attached and below; please plan to be in a quiet room, by yourself, in front of a computer to take the  Technical Phone Screen. This screen focuses on : OO development, Computer Science fundamentals and Best Practices, OO Data Structures and System Design.

 

Here is a video which might help answer some of your questions.

 

The phone interview and onsite interviews are comprised of the following components:

 

1. Technical/coding and design questions:

 

These questions will test your ability to solve a technical problem. If you are rusty, you should study up on:

o    Trees (binary/red black trees/N-ary trees, tree symetric (inverse image), tree traversal, sorting trees)

o    hash maps, stacks/queues/heap/priority que, describe hashtable

o    link lists/reverse link lists (space vs time)

o    recursion/recursive strings

o    binary search

o    Arrays - 2d/3d

o    graphs/graph traversal

o    Big O notation

-          This is the Website that recent candidates hired at Amazon, have said helped them immensely to prepare: https://www.interviewbit.com/

 

-          Specific type of tree<https://en.wikipedia.org/wiki/Trie> to review. 

Some tools you might find useful to study up for the coding portion include:

o    Leet Code or Codefights

o    Elements of Programming Interviews

o    Cracking the coding interview

o    AWS Application Architecture Center – these are the tools that we use to develop amazon services/products.

 

Some interviewers may expect you to beable to discuss examples of big-O notation,

http://pages.cs.wisc.edu/~vernon/cs367/notes/3.COMPLEXITY.html

 

And there will be basic questions on OO data structures and algorithms.

Think about all the edge case scenarios during system design (especially authentication mechanisms)

Must beable to substantiate depth of knowledge when questioned on basics of CS like Algorithms, Data structures and ability to think through the downsides with the system design.

Queues and Arrays

And they may ask you to design a system you have designed recently (distributed system design).

 

Examples of big-O notation, which is a common topic:

http://pages.cs.wisc.edu/~vernon/cs367/notes/3.COMPLEXITY.html

 

basic questions on data structures and algorithms.

Think about all the edge case scenarios during system design (especially authentication mechanisms)

Must beable to substantiate depth of knowledge when questioned on basics of CS like Algorithms, Data structures and ability to think through the downsides with the system design.

Queues and Arrays

Describe the most interesting or complex E2E system you have designed recently

 

Coding questions..see samples that you can find on Interviewbit.com and Leetcode:

-Describe Hashtable

 

 

White Boarding:

You will be coding on the white board. If you need to make assumptions, voice those assumptions with the interviewer and through the course of your exercise, let your interviewer know what you are thinking as he/she is as interested in your thought process and how you approach the problem. There may be missing information in the problem. So, ask clarifying questions before jumping into a solution. There are no trick questions. Share your thought process when solving a problem. The thought process is as important as the solution itself. 

Also, the interviewer may provide hints along the way if you have voiced your approach.  

 

Coding:

Use sites like Interview Cake or Critique My Code to prep.

Practice on a whiteboard.

Come up with solutions in a timely manner.  Take yourself thru a practice problem prior to interview. 

Make sure your code is clean, bug-free and properly handles edge cases. If you need to write pseudo-code to gather your thoughts first (pseudo-code does not count and you must code in a specific l language of your choice), verbally tell the interviewer this is what you are doing.

 

[futureofandhra]

35 minutes ago, Amrita said:

Opika unte 

Below and attached is some information to help you prepare for the interview. Please review carefully.

After reviewing my prep material attached and below; please plan to be in a quiet room, by yourself, in front of a computer to take the  Technical Phone Screen. This screen focuses on : OO development, Computer Science fundamentals and Best Practices, OO Data Structures and System Design.

 

Here is a video which might help answer some of your questions.

 

The phone interview and onsite interviews are comprised of the following components:

 

1. Technical/coding and design questions:

 

These questions will test your ability to solve a technical problem. If you are rusty, you should study up on:

o    Trees (binary/red black trees/N-ary trees, tree symetric (inverse image), tree traversal, sorting trees)

o    hash maps, stacks/queues/heap/priority que, describe hashtable

o    link lists/reverse link lists (space vs time)

o    recursion/recursive strings

o    binary search

o    Arrays - 2d/3d

o    graphs/graph traversal

o    Big O notation

-          This is the Website that recent candidates hired at Amazon, have said helped them immensely to prepare: https://www.interviewbit.com/

 

-          Specific type of tree<https://en.wikipedia.org/wiki/Trie> to review. 

Some tools you might find useful to study up for the coding portion include:

o    Leet Code or Codefights

o    Elements of Programming Interviews

o    Cracking the coding interview

o    AWS Application Architecture Center – these are the tools that we use to develop amazon services/products.

 

Some interviewers may expect you to beable to discuss examples of big-O notation,

http://pages.cs.wisc.edu/~vernon/cs367/notes/3.COMPLEXITY.html

 

And there will be basic questions on OO data structures and algorithms.

Think about all the edge case scenarios during system design (especially authentication mechanisms)

Must beable to substantiate depth of knowledge when questioned on basics of CS like Algorithms, Data structures and ability to think through the downsides with the system design.

Queues and Arrays

And they may ask you to design a system you have designed recently (distributed system design).

 

Examples of big-O notation, which is a common topic:

http://pages.cs.wisc.edu/~vernon/cs367/notes/3.COMPLEXITY.html

 

basic questions on data structures and algorithms.

Think about all the edge case scenarios during system design (especially authentication mechanisms)

Must beable to substantiate depth of knowledge when questioned on basics of CS like Algorithms, Data structures and ability to think through the downsides with the system design.

Queues and Arrays

Describe the most interesting or complex E2E system you have designed recently

 

Coding questions..see samples that you can find on Interviewbit.com and Leetcode:

-Describe Hashtable

 

 

White Boarding:

You will be coding on the white board. If you need to make assumptions, voice those assumptions with the interviewer and through the course of your exercise, let your interviewer know what you are thinking as he/she is as interested in your thought process and how you approach the problem. There may be missing information in the problem. So, ask clarifying questions before jumping into a solution. There are no trick questions. Share your thought process when solving a problem. The thought process is as important as the solution itself. 

Also, the interviewer may provide hints along the way if you have voiced your approach.  

 

Coding:

Use sites like Interview Cake or Critique My Code to prep.

Practice on a whiteboard.

Come up with solutions in a timely manner.  Take yourself thru a practice problem prior to interview. 

Make sure your code is clean, bug-free and properly handles edge cases. If you need to write pseudo-code to gather your thoughts first (pseudo-code does not count and you must code in a specific l language of your choice), verbally tell the interviewer this is what you are doing.

 

That's a good info