02.07.2013 Views

.NET Interview Questions 4 th Edition By Shivprasad ... - A2Z Dotnet

.NET Interview Questions 4 th Edition By Shivprasad ... - A2Z Dotnet

.NET Interview Questions 4 th Edition By Shivprasad ... - A2Z Dotnet

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Figure :- 0.2 IT Company hierarchy<br />

It’s very important during interview to be clear about what position you are targeting. Depending<br />

on what positions you are targeting <strong>th</strong>e interviewer shoots you questions. Example if you are<br />

looking for a project manager position you will be asked around 20% technical questions and<br />

80% management.<br />

Note: - In small scale software house and mid scale software companies<br />

<strong>th</strong>ere are chances where <strong>th</strong>ey expect a PM to be very much technical. But<br />

in big software houses <strong>th</strong>e situations are very much different,<br />

interview are conducted according to positions.... Unless <strong>th</strong>e<br />

interviewer changes <strong>th</strong>e rule.<br />

Above is a figure of a general hierarchy across most IT companies.<br />

Note: - There are many small and medium software companies which do not<br />

follow <strong>th</strong>is hierarchy and <strong>th</strong>ey have <strong>th</strong>ere own adhoc way of defining<br />

positions in <strong>th</strong>e company.<br />

So why is <strong>th</strong>e need of hierarchy in a interview.<br />

“<strong>Interview</strong> is a contract between <strong>th</strong>e employer and candidate to achieve specific goals.”<br />

So employer is looking for a suitable candidate and candidate looks for a better career. Normally<br />

in interviews, <strong>th</strong>e employer is very clear about what type of candidate he is looking for. However,<br />

90% times <strong>th</strong>e candidate is not clear about <strong>th</strong>e positions he is looking for.<br />

How many times it has happened wi<strong>th</strong> you <strong>th</strong>at you have given a whole interview and when you<br />

mentioned <strong>th</strong>e position you are looking for...pat comes <strong>th</strong>e answer, “ we do not have any<br />

requirements for <strong>th</strong>is position”. So be clarified about <strong>th</strong>e position right from when you start <strong>th</strong>e<br />

interview.<br />

Following are <strong>th</strong>e number of years of experience according to position.<br />

• Junior engineers are especially freshers and work under software engineers.<br />

• Software engineers have around 1 to 2 years of experience. <strong>Interview</strong>er expects software<br />

engineers to be technically at a medium level.<br />

• Senior Software Engineers have around 2 to 4 years of experience. <strong>Interview</strong>er expects<br />

<strong>th</strong>em to technically be very strong.<br />

• Project leads should handle majority technical aspect of project and should have around 4<br />

to 8 years of experience. They are also indirect architect of <strong>th</strong>e project. <strong>Interview</strong>er<br />

expects <strong>th</strong>em to be technically strong so <strong>th</strong>at <strong>th</strong>ey can drive <strong>th</strong>e architecture part of <strong>th</strong>e<br />

project. <strong>Interview</strong>er also expects <strong>th</strong>em to have people management skills.<br />

• Project Manager are expected to be around 40% technically strong and should have<br />

experience above 10 years plus. But <strong>th</strong>ey are more interviewed from aspect of<br />

project management, client interaction, people management, proposal preparation etc.<br />

So now judge where you stand, and where you want to go..........<br />

Resume Preparation Guidelines<br />

First impression <strong>th</strong>e last impression

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!