Interview Tips for Freshers 2013

An interview is a final step for selection to any job. Eligibility for giving interview means that the candidate have right aptitude and knowledge for the job, he has required knowledge about the subject. A one-one communication in the form of interview makes the decision final that whether the candidate should be selected for the job or not. 

Student Success Strategy

Different types of interview sessions 

1) Questions asked on the basis of your CV and past academics background. 

2) Interview by a number of people where the candidate is pressurized by asking number of question during the same time. 

3) Interview on doing and explaining some task on some traits like leadership, management etc. 

Best Jobs in India

Preparation tips for interview round 

1) Read your resume completely. 

2) Prepare question which can be asked by the interview panel. Questions related to your academic records and your hobbies are generally asked by the interview panel. 

3) Read about the organisation for which you are interviewed, go through the official website of the organisation once completely and have a look on the products and services offered by the company. 

4) Rehearse your interview round, gave interview in front of your teacher or an interview expert few times before the actual interview. 

Useful Memory Techniques

Resume Sample Best For You    Check Now!

Consider the following points 

Be punctual - Arrive on time better half an hour earlier. Have a positive body language, good eye contact, wear neat and clean clothes. 

During the interview be confident about your answers and be true and loyal to interview panel. Don’t hide your weaknesses and accept your week areas in front of interview panel. Good communication skills are essential for success in any interview, so work on your communication skills also. Interview panel may ask the candidate to write something or to draw anything, so well prepare with your stationary items as well.

Make Your Resume Like This  Check Now!

All the best for your upcoming interviews. Best of luck. 

CAMPUS -INTERVIEW TIPS 20:58 No comments Read More

Simple Workflow Service - Amazon Adding One Enterprise Brick At Time

Yesterday, Amazon announced a new orchestration service called Simple Workflow Service. I would encourage you to read the announcement on Werner's blog where he explains the need, rationale, and architecture. The people I spoke to had mixed reactions. One set of people described this as a great idea and were excited that the developers can now focus on writing domain-specific code as opposed to writing plumbing code to orchestrate their actual code. The other set of people felt that this service creates a new cloud lock-in making it difficult for the developers to switch from one cloud to another as well as being able to interoperate at the orchestration level. 
I believe this is a brilliant idea for a variety of reasons. Orchestration has always been painful. Ask the developers who have been involved in managing task execution across a cluster that required them to code for load balancing, handling exceptions, restarting hung processes, tracking progress etc. This is not a core competency the most developers have but they do end up writing such code due to lack of better alternative. The frameworks such as WS-BPEL were not designed to run in cloud-like environments and there has been no single standard REST orchestration framework out there that people could use.

From a vendor's perspective, I admire Amazon's ability to keep innovating via such services that differentiate them as a leading cloud vendor. As computing becomes more and more commodity, competing based on price alone isn't a good idea. If you're a cloud vendor you need to go above and beyond the traditional IaaS attributes even though you excel in all of them. I also see PaaS eventually bleeding into IaaS as IaaS continues to become a commodity. As far as PaaS goes, federated or otherwise, we're barely scratching the surface.

I don't see this service as a cloud lock-in but it certainly makes EC2 more attractive and sticky. I would be concerned if Amazon were to force the developers to use their SWS for orchestration. This is their version of how they think orchestration should be done and the developers can opt in if they want. And kudos to them to think beyond their cloud. The folks who worry about cloud lock-ins also talk about Amazon not following the standards. I believe that we should not create standards for the sake of creating standards. I am a believer in first showing that something works and later, if there's enough interest, figure out a way to standardize it. All these talks about standard-first even before you write that first line of code doesn't make any sense.

It's yet to be seen how this service turns out, but this is a huge step forward for getting more enterprise software customers onboard. Orchestration is one of the most chronic problems of enterprise software and with the challenges of a hybrid landscape to be able to orchestrate across on-premise and cloud-based solutions, this service is certainly a step in the right direction. Right Scale has been using a Ruby workflow Ruote for their workflow needs and now they orchestrate these workflows using SWS  to achieve fault tolerance and concurrency. As you can see, Amazon has opened up a gold mine for start-ups. The back-end execution has always been challenging. Now, there is an opportunity to write your own enterprise grade workflow engine or scheduler that runs in the cloud. 

CAMPUS -INTERVIEW TIPS 20:26 No comments Read More

Simple Workflow Service - Amazon Adding One Enterprise Brick At Time

Yesterday, Amazon announced a new orchestration service called Simple Workflow Service. I would encourage you to read the announcement on Werner's blog where he explains the need, rationale, and architecture. The people I spoke to had mixed reactions. One set of people described this as a great idea and were excited that the developers can now focus on writing domain-specific code as opposed to writing plumbing code to orchestrate their actual code. The other set of people felt that this service creates a new cloud lock-in making it difficult for the developers to switch from one cloud to another as well as being able to interoperate at the orchestration level.

I believe this is a brilliant idea for a variety of reasons. Orchestration has always been painful. Ask the developers who have been involved in managing task execution across a cluster that required them to code for load balancing, handling exceptions, restarting hung processes, tracking progress etc. This is not a core competency the most developers have but they do end up writing such code due to lack of better alternative. The frameworks such as WS-BPEL were not designed to run in cloud-like environments and there has been no single standard REST orchestration framework out there that people could use.

From a vendor's perspective, I admire Amazon's ability to keep innovating via such services that differentiate them as a leading cloud vendor. As computing becomes more and more commodity, competing based on price alone isn't a good idea. If you're a cloud vendor you need to go above and beyond the traditional IaaS attributes even though you excel in all of them. I also see PaaS eventually bleeding into IaaS as IaaS continues to become a commodity. As far as PaaS goes, federated or otherwise, we're barely scratching the surface.

I don't see this service as a cloud lock-in but it certainly makes EC2 more attractive and sticky. I would be concerned if Amazon were to force the developers to use their SWS for orchestration. This is their version of how they think orchestration should be done and the developers can opt in if they want. And kudos to them to think beyond their cloud. The folks who worry about cloud lock-ins also talk about Amazon not following the standards. I believe that we should not create standards for the sake of creating standards. I am a believer in first showing that something works and later, if there's enough interest, figure out a way to standardize it. All these talks about standard-first even before you write that first line of code doesn't make any sense.

It's yet to be seen how this service turns out, but this is a huge step forward for getting more enterprise software customers onboard. Orchestration is one of the most chronic problems of enterprise software and with the challenges of a hybrid landscape to be able to orchestrate across on-premise and cloud-based solutions, this service is certainly a step in the right direction. Right Scale has been using a Ruby workflow Ruote for their workflow needs and now they orchestrate these workflows using SWS  to achieve fault tolerance and concurrency. As you can see, Amazon has opened up a gold mine for start-ups. The back-end execution has always been challenging. Now, there is an opportunity to write your own enterprise grade workflow engine or scheduler that runs in the cloud. 

CAMPUS -INTERVIEW TIPS 20:24 No comments Read More

Campus BUZZ!!!

This Site is dedicated to all the students,and people who are looking for jobs and also for those who are willing to study further(GRE and all)
Job in a good company after graduation is one of the basic need of a student.
But,this site will also be helpful to all those who are jobless
or who are planning to change there company for a better job!!!


But,it does not ends here.What about those who are willing to study further.
Yes,there is a lot of materials for GRE test for all those who are willing to study further.


Here, you will get all kind of resources you require for yur placement and GRE test!!!
Check regulary for Updates and new materials...


Here are placement papers of Top companies(latest updates on 25th,november 2006)
if you want a paper for a particular company,then post a comment.


placement Papers and Interview Questions


Accenture latest paper New


Adobe Latest Paper


CSC Paper 2006 New


Cisco -2006


FlextronicsNew


Google Placement Paper

Hp 2006 paper

IBM paper 1


IBM paper 2


INFOSYS Paper -1 INFOSYS paper- 2 INFOSYS paper-3


Larsen & Turbo New


Satyam Paper-1


TCS -1(2006) TCS-2(2006) TCS-3(2006)


More placement Papers and Interview Questions


INTERVIEW RESOURCES::::
Story Of a Successful TCSer


Microsoft interview


how-to-answer-64-toughest-interview-questions


Resources for GRE::::

Gre questions and materials

CAMPUS -INTERVIEW TIPS 11:49 No comments Read More

Interview Questions

1. Tell me about yourself

Keep your answer short and focused on your professional life. This is not the time to bring up relationships, childhood experiences, family etc. A brief history of education, career and special interests is what is called for here. End it with why you are interested in this particular job

2. Why are you applying for this particular job?

Show interest and demonstrate that you have researched the job and know what you are getting into. Bring up evidence from past work/studies that support your interest in this role and any skills you have acquired in preparation for the role. You can say something like 'I would like to work for a leader in innovative network and telecommunications solutions and my college degree in computatational mathematics has given me a solid background for this role. Mention the value -added you can bring to the job.

3. What do you know about our company?

Indicate what you have learnt from your research activities -from their

annual reports, news papers, word of mouth, other employees etc.

Use this to flatter them and show that you have done your homework.

. What makes you qualified for this particular job?

Again, explain that you are very interested in the job and demonstrate what it is about your past experiences, education and qualifications that makes you ideal for the job. Show enthusiasm and support your answers with evidence wherever you can (eg. my summer internship at Citibank gave me broad exposure to the area of equity analysis and I think I can apply many of the tools I learnt there in this job). Elaborate on all the past experiences and skill sets that make you suitable for the job. In cases where your past experience is not directly relevant, you can still find elements of it that can be useful. Play up team skills, computer skills, leadership roles, specific courses and independent research activities that can be useful to the job at hand to show your initiative even where you don't have directly relevant job experience.

5. What can you do for us that someone else can't?

Demonstrate key strengths, skills and personal characteristics.

6. Why should we hire you?

See 3. Because you have all the experience/ traits/ credentials demonstrated in 3 and in addition to being qualified, you are enthusiastic, intelligent, hardworking, flexible and willing to learn. Also mention any key relationships you may have that may assist you in the job.

7. What do you look for in a job?

Be honest. Also mention keywords such as challenging, steep learning curve, good work culture, demanding, rewarding, opportunities for advancement and growth, team environment, opportunity to build and maintain client relationships etc.

8. Why are you looking to make a career change?

Mention your interests and make sure you bring up all skills/ experience however insignificant that can support your move in this new direction. It is quite common in this day and age to make a career switch. You need however to show that you have very carefully thought about the change, have a strong interest in the new career and can use some of your previous skills/ education/ relationships to make that move. 

9. Why did you leave your last job?

Do NOT use this as an opportunity to badmouth past employers or peers or talk about a failure of any sort. Any of these answers are acceptable: you were looking for a new challenge, your learning curve had flattened out in the previous job and you were looking for a new learning opportunity, the company or department were restructuring, you were ready to start something new after achieving your career goals at the previous company etc.

CAMPUS -INTERVIEW TIPS 11:48 No comments Read More

Group Discussion Tips

Group Discussion Tips

1. Always be the initiator and concluder of the GD then being a participant.

2. But if you are particaipant always try to be the most vianl/key participant.

3. put points firmly and always try to get others support too.

4. if you find that the discussion os going offttrack then never loose an oppurtunity to bring it back to straem this is the best point to score max.

CONTINUE..

5. try to keep latest information on the topic.

6. be very polite , people may try to provoke you to to get more points but try to keep cool.

7. most important don't wait for your turn to speak when discussion is on. inturrupt politely if you want to put forward your points.

8. last but not the least keep atab on the time given for discussion. score points by wrapping up the discussion if you feel that the discussion is heating but the time is going to be over.

9. during conclusion, do end with the conclusion note. that shows your leadership quality.


Best scoring points are:

1. initiation of discussion,

2.always keeping/trying tokeep discussion on track

3. conclusion on time

4. your capability to keep your cool and listen as well as putting your points.

Group Discussion Do's and Don'ts

Be as natural as possible. Do not try and be someone you are not. Be yourself.

A group discussion is your chance to be more vocal. The evaluator wants to hear you speak.

Take time to organize your thoughts. Think of what you are going to say.

Seek clarification if you have any doubts regarding the subject.

Don't start speaking until you have clearly understood and analyzed the subject.
Work out various strategies to help you make an entry: initiate the discussion or agree with someone else's point and then move onto express your views.

Opening the discussion is not the only way of gaining attention and recognition. If you do not give valuable insights during the discussion, all your efforts of initiating the discussion will be in vain.

Your body language says a lot about you - your gestures and mannerisms are more likely to reflect your attitude than what you say.

Language skills are important only to the effect as to how you get your points across clearly and fluently.

Be assertive not dominating; try to maintain a balanced tone in your discussion and analysis.

Don't lose your cool if anyone says anything you object to. The key is to stay objective: Don't take the discussion personally.

Always be polite: Try to avoid using extreme phrases like: 'I strongly object' or 'I disagree'. Instead try phrases like: 'I would like to share my views on...' or 'One difference between your point and mine...' or "I beg to differ with you" Ch etanaS

Brush up on your leadership skills; motivate the other members of the team to speak (this surely does not mean that the only thing that you do in the GD is to say "let us hear what the young lady with the blue scarf has to say," or "Raghu, let us hear your views" - Essentially be subtle), and listen to their views. Be receptive to others' opinions and do not be abrasive or aggressive.

If you have a group of like-minded friends, you can have a mock group discussion where you can learn from each other through giving and receiving feedback.

Apart from the above points, the panel will also judge team members for their alertness and presence of mind, problem-solving abilities, ability to work as a team without alienating certain members, and creativity

I gave more tips in the presentation which was listed in the Placements Resources page.

Thanks,

all the best

CAMPUS -INTERVIEW TIPS 11:45 No comments Read More