Skip to main content



Tips for Telephone interview:


Telephone contact means that there are no visual clues unlike a face-to-face interview, In a telephone interview you have to sell yourself using only words and the tone of your voice


Smile! Amazing as it might sound, smiling whilst you talk really helps. You will come across as more friendly and confident. Try it!



Few Minutes Before Telephonic:

Should have compile list of :

• Your strengths and weaknesses
• Your background and skills,

• Answers to typical interview questions

Make sure you have :

• Keep your resume in clear view, so it's at your fingertips when you need to answer questions.

• Have a pen and paper handy for note taking.

• Turn mobile phones off, so your call isn't interrupted

• Practice reducing "ums" and "uhs" and "okays"



During the Interview:

• The first 15 seconds are crucial and interest in your voice is the key. Just the way you answer the phone has an impact on the caller. Talk distinctly and with confidence.

• Smile! Smiling whilst you talk really helps. You will come across as more friendly and confident.

• Use gestures as in normal conversation and be enthusiastic where appropriate

• The tone and rhythm of your voice are important. If you speak in a monotone this will be more apparent on the telephone.

• The interviewer may start with the question, "Tell me about yourself." You should be able to explain the value you added to the company.

• Review a problem that you turned into a positive situation for each position that you list. If possible try to quantify accomplishment in each position

• Give short answer to questions. Short sentences are more easily understood over the phone than long orations. They also give more opportunity for interchange between you and the interviewer, which helps both of you maintain your interest

Listen to Interviewer carefully :


• When the interviewer speaks give him your undivided attention

• Don’t look at your notes or think of anything else during that time

• Don't answer a question that you haven't fully understood.

Restate the question.

• This will also give you time to prepare an answer and prevent long silences on the phone.

• Don't do this too often, as the interviewer will quickly become tired of repeating himself or herself.

Answer questions courteously.


• Try to sound relaxed and confident.

• A note of irritation or frustration in your voice is much more noticeable over the phone, and can't be offset by positive body language.

• Try not to be put off by pauses from the interviewer - (s)he may be taking notes .Don’t feel compelled to fill in pauses with some comments or questions.


Strengths and Weaknesses.

• You must be able to specify your major strengths.

• Your weaknesses, if such must come up, should only be turned around to positives.

Donts :

• Rambling,

• Interrupting the interviewer



Winding up…


• The end of the call is always a tricky thing. A good suggestion is to thank the caller for his or her time.

• If you don't already have it, be sure to ask for the interviewer's exact title and name spelling, along with a email address, so that you can send a thank you note.


Best of Luck • • •








Comments

Girijesh said…
Thanks, will follow this.

Popular posts from this blog

NULL VALUES and NULL INDICATORS in DB2

In DB2, the columns defined as NULL needs to be handled carefully else it will throw null exception error, in order to over come this error data type can be handled by using null indicator . NULL is stored using a special one-byte null indicator that is "attached" to every nullable column. If the column is set to NULL, then the indicator field is used to record this. Using NULL will never save space in a DB2 database design - in fact, it will always add an extra byte for every column that can be NULL. The byte is used whether or not the column is actually set to NULL. The indicator variable is transparent to an end user Consider below Table : Create Table SAMP_TAB SN CHAR (10) SNAME CHAR (10) STATUS CHAR (2) NOT NULL BY DEFAULT CITY CHAR (10) NOT NULL Note :: Unless you specify NOT NULL, the default is to allow for NULL In above table SN and SNAME columns holds null values by default, in order to handle these null variables we need to have NULL-INDICATORS declares in the Pro

Mainframe Written test @ Accenture

1. What r the 2 function we can get by using INSPECT verb? (c) A. file handling, error handling B. opening a file, closing a file. C. char counting, replacing. D. none of the above 2. Indicate which of the following is not true about the formal parameters in a subroutine? (c) A. every formal parameter must appear in the linkage section of the subroutine B. every formal parameter must appear in the using phrase of the procedure division header of the subroutine C. A formal parameter name can appear more than once in the using phrases of the procedure division header of the subroutine. D. A formal parameter can not be declared with value clause in a subroutine 3. What is the value of A? (B) 01 A pic 9(3). Move 100 to A. Perform 1000-para thru 1000-exit. Display the value of a=A Stop run. 1000-para. If A=100 Perform 1000-exit Else Move 150 to A End-if. Move 200 to A. 1000-exit. Exit. a.100 b.200 c.150 d. none of the above is correct. 4. What is the value of B? (A) Move 1 to A Evaluate tr

How to Solve SOC7 Abend - with screen shots

Below process helps to find out the statement, caused the SOC7 error. Check the Sysout of RUNJCL . This shows the error statement and lists offset value Take the Offset Value 000003C0 Got to respective Compilation Job listing, check the sysprint Search for the offset value 0003C0 (delete +00 -- initial 3 letters of Offset value and search for it) check below 2 screen shots This Offset value is listed under line no 0045 – which refers to Move statement. Take this no. 045 and find for it in same sysprint. This points to the exact statement, caused SOC7 T his 045 pints to the Move statement 1526, this is the exact line in the program Check for the above line no. In source program . This points to the statement highlighted below . Check the statement, variable check-4, which is added to check-6. These are having different Picture clause. check-4 is alfhanumaric, holding some junk data, when this data is moved to Chcek-6 variable(of comp-3) creates SOC7 error. This is just an example to e