List of Hot Careers for the Next 10 Years

• Sales and Marketing
• Financial Services
• Security Services
• Merchandising
• Advertising Professionals
• Market Researchers
• Real Estate Jobs
• Teaching jobs
• Entertainment Jobs such as actors, musicians, dancers
• Writers including Technical writers, Newspaper writers, reporters
• Doctors
• Surgeons
• Physicians
• Health-care Jobs such as nursing, medical technicians, therapists, lab technicians, radiology technicians
• Information Technology jobs such as Computer Systems Analysts, Computer Engineers, Web Developers and Network Engineers
• Network Support Technicians
• WEB Specialists
• Data Base Administrator
• Lawyers
• Intellectual Property Attorney
• Occupational Therapist
• Biological Scientists
• Applications Engineer
• Product Development Manager
• Technical Support Manager

Comments (0) | View (2445)

1. Healthcare
The health care sector is in great need of people currently and according to job market analysts, the demand for personnel in this sector will continue to increase in the coming years. You can consider becoming a Physician assistant or a physical therapist or a nurse. The average salary for all of these professions lies between $60000 to $70000 a year. To become a physician assistant, you need to have a bachelor's degree along with a two year training program especially designed for physician assistants. To become a physical therapist you require a master degree level program on physical therapy and you need to obtain a license by passing an exam. To become a nurse, you need to have completed a three year nursing diploma or a four year bachelor degree in nursing (Bachelor of Science in Nursing), followed by passing the nursing exam. Besides the educational qualifications, a person should possess people skills and should be compassionate to succeed and make a career in these hospital jobs.

2. InformationTechnology
IT jobs such as software developers, software testers, technical writers, etc. definitely qualify for high salary careers 2011. Despite the recession, there has been a continued surge in the demand for IT people. On an average, an IT professional with a few years of experience can look forward to make approximately $90000 in a year. To become a software engineer, you need a bachelor's degree in computer science. To become a network system analyst, you either need a bachelor's degree in computer science or a liberal arts degree. In some cases, a two year associate degree is all you need to enter this profession, which is today counted among the top careers in 2011.

3. Business and Finance
There is a lot of scope of growth in this sector in terms of employment. Recession has fueled the demand for accountants and auditors, who manage a company's accounts and yearly income statements. Financial analysts and financial planners who advice a business on taking the right decisions so that profits can be made, are in great demand too. Experienced financial planners can expect to make around $ 100000 per year in the coming months. Other business jobs such as sales manager, human resources manager, market research professionals are not only considered best careers for 2011, but they are also predicted to be hot careers for the next 10 years.

4. Education
Teaching jobs, whether in school or in college will be one of the best careers for 2011. After all, recession or no recession, there will always be a demand for quality teachers. To become a teacher, you will require a four year bachelor's degree in elementary/secondary education. A bachelor's degree has to be followed by a one year certificate course in teacher's training. To become a teacher you will need to obtain a license to teach, from the state education department. If you plan on becoming a professor, you need to have completed your PHD. Teaching jobs, in comparison to other jobs, have lesser work timings. The salaries are competitive while the stress levels are less, as a teacher gets a number of holidays throughout the year. All these pluses make jobs in the education sector one of the best careers 2011. 

5. Media/Communication
With the tremendous increase in traffic on the Internet, there will be a great demand for people such as content writers, bloggers and those who maintain websites. Advertising professionals, video game designers, actors, editors, graphic designers and other media jobs are today among the top careers in America. So, you can consider making a career in media by entering any of these professions. 

This was in short about the best careers 2011. Jobs in any of these sectors will provide you with the right kind of security and salary in the coming future. See where your interest lies and then acquire the qualifications and experience required to enter the field of your choice. Best of luck!

Comments (1) | View (2510)

Group Discussion Etiquette

Many of the problems that arise in group discussion result from members who do not have discussion skills. Being able to properly participate in a discussion group is similar to reading. If you have a lot of experience with discussions, it is likely that you will do well in a discussion group.

During a discussion, it is important for members to always stay on topic. It is bad etiquette to raise issues that are not related to the subject of the discussion. When members raise issues that are off topic, they can waste time and prevent the group from achieving a certain goal. Most group discussions will have a time limit. The group will have little time to waste talking about topics that are not relevant to the subject. Because of this, it is always important to make sure any questions or statements you make are related to the topic. Another good form of etiquette in group discussions is to ask open-ended questions instead of closed-ended questions.

An open-ended question is one that does not require a specific answer. It is a question that is designed to get the group thinking. The only time a closed-ended question should be raised is if the group has specific information that they need to learn. Open-ended questions are important because they allow the other members to think. If the question is related to a problem, the members may be able to come up with a number of different solutions. If one member interrupts another while they are speaking, this is an example of bad etiquette. You should never do this. It is rude, and it can lead to conflict between you and the person that was interrupted.

It is important for everyone to get their point across. If you have a disagreement or concern with a statement that is being made by someone else, wait until they are finished speaking before you talk. Most group discussions require members to raise their hands before asking a question or making a statement, and this is something you will want to follow. If you disagree with a statement or idea that has been presented by someone else, it is important for you to say it in a polite manner. In a group discussion, it is important to avoid conflict, as this can stop the group from being able to successfully reach an objective.

For example, an example of bad etiquette is saying something like "that idea will never work" or " your idea doesn't make any sense." These are statements that can be damaging to the member you are addressing them to. You will want to avoid this. A good alternative to these two statements are "that idea raises some serious issues" or "I see your point, but there are a number of problems that may arise." These two statements are examples of good etiquette, and you will want to use them if you wish to succeed. There is nothing wrong with not being in agreement with what a person says. However, you will want to let them know this in a polite manner, and you should have good reasons for holding your opinion.

It is also bad etiquette to put down the ideas that have been presented by another person. During the meeting, all ideas should be considered, and no one should be ridiculed because of an idea they have. Their are a number of good reason for this.

Comments (0) | View (2655)

Technical Interview Tip 1: Interviews are tough. There is no question about it. At once, interviews can make or break the confidence of the interviewee in himself. Even though you may not give the interviewee the job, a good interview can make him feel powerful. Keeping this in mind, as important as it is for the interviewee to arrive on time, it is even more important for the interviewers to be present and ready. The feelings of self doubt and anxiousness that the interviewee feels are heightened with each passing second that the interview does not start. Further, make sure that when you do eventually start the interview, a formal apology is made to the interviewee from all members of the team who are going to interview him.

Although my greeting is reciprocated, I get the feeling that there is something wrong. The long haired one is looking at me with curiosity and the other guy is simply looking angry. Infact, he is pursuing his lips and trying hardest to show that he means business by looking grim. I try to break the ice by mentioning that I have met the long haired guy before. This makes the grim guy even grimer and my heart makes a flip turn wondering what I did wrong. Without further adieu, we proceed to the interview room.

Technical Interview Tip 2: The initial contact with the interviewers makes a big impact on the way the interviewee feels about the situation at hand. The interviewee needs to be made comfortable and relaxed. This might sound corny, but a smile goes a long way in making the interviewee feel comfortable about the interview and the people he had been dreading about meeting since it was scheduled. He should be able to see that these are guys (or gals) like him after all! Even the most confident and technically sound candidates feel nervous about the social situation that is created. Don't make it harder on them by being grim or aloof. Smile!

The interview room is like a Doctor's surgery. There is a big desk with a big chair in a corner and a small chair adjacent to it, where a Doctor would ask the patient to take a deep breath before he puts the needle in. I feel like taking a deep breath myself as I am told to sit in the small chair. The grim guy takes the Doctor's chair and the long haired guy takes a chair in the far corner and immediately opens up a laptop, as if he is the cigarette smoking man from an episode of the X-Files. Here to purely observe!

Technical Interview Tip 3: Environment and surroundings are important if you don't want the interviewee to sweat. Literally! Although, in a sense, the interviewee is like the proverbial goldfish in fish bowl, don't make him feel as if he is about to be gobbled up by the cat. You can observe but don't make him watch his back. It is important to make sure that all interviewers are in the line of sight of the interviewee, so that he knows who to address while answering your questions. Make sure that the interviewee is in a comfortable seat, not too high or low than your seats.

The grim guy takes a badly scrawled piece of paper out of his pocket and studies it for a few seconds. He picks it up, brings it closer to his face, as if to decipher his own writing, and then puts it down and stares intently at me. I show a nervous smile. It is then that he speaks for the first time. "So what do you think is the effect of making an inner class static?"

Technical Interview Tips 4 and 5: Each technical interview must start with an introduction of the process. The interviewers must have a blueprint of what they want to ask the interviewee and in what order. Further, this process must be explained to the interviewee so that he understands and is comfortable with it. The due diligence and structure that you take in writing your code should be shown in the interview process as well (assuming that you are a developer yourself).

A technical interview must never start with the toughest question on your list. In fact, it should not start with a technical question at all. Start your interview by asking the interviewee about what he is currently doing, or the last job that he did. This is the easiest question for the interviewee to answer and it has two advantages. First, the interviewee gets comfortable with the whole interview process because talking about their current job/recent assignment comes easily. Second, it gives you material to query the interviewee about the technical side of this current job. An innocuous question like "So tell me about what you are doing, or have done in the past using what technologies" can uncover a smogorsboard of questions for you to query the interviewee with.

My mind stumbles, falters and jumps around trying to pierce together "static" and "inner classes". But it goes blank and I fail to come up with an answer. The interview hasn't started well and I literally start to sweat. Seeing my discomfort, the grim guy says "Would you like to know the answer to that?". I say yes, and am treated to a monologue. Before he is finished, the long haired guy questions me on the "architecture of the last application that I worked on". I relax and think that this is something I know, and start promisingly. Before I have finished my second sentence though, the long haired guy asks me "to be specific and not work on generalizations". I start again, fearing that I have not understood him correctly. An architecture is an architecture right? I try again, only to notice that neither of the interviewers are looking at me, one is playing with the laptop and the other is scanning my shoes. Anyways, I scrap through that, and am handed back to the grim guy, who pursues the dreaded list again and reels off a series of bland theoretical technical questions.

Technical Interview Tip 6 and 7: Although debatable, it is perhaps a bad idea to ask theoretical questions in a technical interview. What are you actually looking for in a candidate? His ability to answer questions which require him to remember every nuance and specifics of a language or his experience, ability and diligence in coming up with solutions to problems? Language fundamentals, are really just that, fundamentals, which can be crammed up or looked up when the need arises. You can have written tests to assess the ability of a developer or ask him to prove his credentials by taking a certification exam. But asking him to remember the signature of a particular method is liking putting you back in prep school to recite the 50 states. Not a good idea.

A fundamental aspect of the interview process is helping the interviewee to become confident enough in his own abilities to be able to showcase those abilities. Although this is not something that the interviewers are obliged to do, it is something that they can help with. Encouraging the interviewee with direct eye contact and a nod when you think that the interviewee answered something correctly will make the interviewee more confident and in control of the situation.

At this stage I know that the interview is not going very well. I am hoping that by the time we get to my code submission, which I had submitted a couple of days earlier, I may have a better chance, as I am confident in my solution. However, it only gets worse. The long haired guy brings the laptop on the desk and I see my code on the screen. He questions me on the style, the indentation, the choice of variable names and finally on the solution. He disagrees with me on all the aspects and tells me that my code does not adhere to their coding standards (CheckStyle) and that it would suffer "a heart attack" if evaluated against it. Further, he tells me that the solution can easily be modified to make it future proof.

Technical Interview Tip 8: Code reviews are an excellent way of evaluating potential candidates and their coding skills. However these reviews should be looked at in context of the problem that they solve and the approach of the interviewee to solving it, and not on their style and coding standards. Most organizations these days use automatic standardization tools that can inculcate newcomers to the organizations coding standards. Remember that whatever coding standards are followed within your organization may not necessarily be the norm outside it. Evaluating an interviewee on the style of their code is like judging people by what they wear. It has its place, but not in a technical interview. And with a good candidate, you can always give it the queer eye.

When evaluating the code review remember the parameters within which the interviewee had to solve the code review. Did the terms of reference ask the interviewee to make sure that the solution should be future proof? Did it ask him to solve the problem as a showcase to his coding skills or his analytical skills? Should the interviewee second guess your expectations? Remember, a solution should be made as simple as possible, but no simpler. Evaluate this code against this paradigm.

It is almost the end of the interview process and I am exhausted by it. I know that it hasn't gone well. In a final act of self preservation, I ask the interviewers to ask me more questions as I know I can do better. I also tell them that this was a very different interview process for me as I am normally not asked these types of theoretical questions in an interview. The grim one, now with a smile on his face, informs me that although they have no more questions, they have a reason for such questions. "We are called to solve some of the world's toughest problems and therefore have to make sure that we hire the best. There have been so many cases where we were called after other software firms had given up".

Technical Interview Tip 9: Pride is good. Self-Adultation is not. While you are proud of hiring the best candidates, do not make it the sole reason for attracting candidates and worse, of rejecting candidates. Many a company have lost good candidates because of indulgence of form over substance. Praise your achievements, but perhaps the candidate already knows that and therefore the reason why he is in front of you. It is not the time to shout it out, but to be humble and to seek deserving participants in the search for future glory.

Comments (0) | View (1619)

1. What is RDBMS?

Relational Data Base Management Systems (RDBMS) are database management systems that maintain data records and indices in tables. Relationships may be created and maintained across and among the data and tables. In a relational database, relationships between data items are expressed by means of tables. Interdependencies among these tables are expressed by data values rather than by pointers. This allows a high degree of data independence. An RDBMS has the capability to recombine the data items from different files, providing powerful tools for data usage.

2. What are the properties of the Relational tables?

Relational tables have six properties:

1. Values are atomic.
2. Column values are of the same kind.
3. Each row is unique.
4. The sequence of columns is insignificant.
5. The sequence of rows is insignificant.
6. Each column must have a unique name.

3. What is Normalization?

Database normalization is a data design and organization process applied to data structures based on rules that help building relational databases. In relational database design, the process of organizing data to minimize redundancy is called normalization. Normalization usually involves dividing a database into two or more tables and defining relationships between the tables. The objective is to isolate data so that additions, deletions, and modifications of a field can be made in just one table and then propagated through the rest of the database via the defined relationships.

4. What is De-normalization?

De-normalization is the process of attempting to optimize the performance of a database by adding redundant data. It is sometimes necessary because current DBMSs implement the relational model poorly. A true relational DBMS would allow for a fully normalized database at the logical level, while providing physical storage of data that is tuned for high performance. De-normalization is a technique to move from higher to lower normal forms of database modeling in order to speed up database access.

5. What are different normalization forms?

1. 1NF: Eliminate Repeating Groups Make a separate table for each set of related attributes, and give each table a primary key. Each field contains at most one value from its attribute domain.
2. 2NF: Eliminate Redundant Data If an attribute depends on only part of a multi-valued key, remove it to a separate table.
3. 3NF: Eliminate Columns Not Dependent On Key If attributes do not contribute to a description of the key, remove them to a separate table. All attributes must be directly dependent on the primary key.
4. BCNF: Boyce-Codd Normal Form If there are non-trivial dependencies between candidate key attributes, separate them out into distinct tables.
5. 4NF: Isolate Independent Multiple Relationships No table may contain two or more 1:n or n:m relationships that are not directly related.
6. 5NF: Isolate Semantically Related Multiple Relationships There may be practical constrains on information that justify separating logically related many-to-many relationships.
7. ONF: Optimal Normal Form A model limited to only simple (elemental) facts, as expressed in Object Role Model notation.
8. DKNF: Domain-Key Normal Form A model free from all modification anomalies is said to be in DKNF.

Remember, these normalization guidelines are cumulative. For a database to be in 3NF, it must first fulfill all the criteria of a 2NF and 1NF database.

6. What is Stored Procedure?

A stored procedure is a named group of SQL statements that have been previously created and stored in the server database. Stored procedures accept input parameters so that a single procedure can be used over the network by several clients using different input data. And when the procedure is modified, all clients automatically get the new version. Stored procedures reduce network traffic and improve performance. Stored procedures can be used to help ensure the integrity of the database.

e.g. sp_helpdb, sp_renamedb, sp_depends etc.

Comments (0) | View (1636)

During phone interview

Here are the some points for successful phone interviewing. Follow these simple rules and you should achieve success in this important phase of job-hunting.

Here are some do's for phone Interviews:

• Smile always helps you in every situation. Smiling will project a positive image to the listener and will change the tone of your voice.
• Do keep a glass of water handy, in case you need to wet your mouth.
• Do know what job you are interviewing for.
• Speak slowly and enunciate clearly.
• Take your time, it is perfectly acceptable to take a moment to collect your thoughts.
• Remember your goal is to set up a face to face interview. After you thank the interviewer ask if it would be possible to meet in person.
• Do give accurate and detailed contact information in your cover letter so your interviewers can easily connect with you.
• Household members must understand the importance of phone messages in your job search.
• Use the person's title (Mr. or Ms. and their last name.) Only use a first name if they ask you to.
• When being interviewed by phone, do make sure you are in a place where you can read notes, take notes, and concentrate.
• If you cannot devote enough time to a phone interview, do suggest a specific alternate time to the recruiter.
• Give short answers.
• Do ensure that you can hear and are being clearly heard.
• Do create a strong finish to your phone interview with thoughtful questions.

Comments (0) | View (1958)

1. Preparation and confidence

Preparation and confidence are very important tips. Good preparation always creates confidence. So the important thing to an interview is to be well prepared. In this you have to consider two things:

· You must prepare yourself practically for the interview.

· You have to gather information which is useful during the interview.

2. Checklist

While going to interview you must consider the following things:

1. You have to confirm about the time, date and location of the interview and name of interviewee where appropriate.

2. You have to plan to get there no earlier than half an hour before the interview time.

3. You must ready with your dress which is professional.

4. Concentrate on the interview at the interview.

5. If you are asked to bring certificates, references etc., get them ready before the day. Your interview letter must be with you.

6. On arrival ensure the receptionist knows you are there.

3. Be on time!

Public transport may be useless if the traffic is heavy. Always keep in mind that you never get a second chance to make a first impression. So be on time at the particular location of interview.

Also if you are there so early, you can wait nearby cafe of shop. And if you are going to be late, then best option is call them.

4. Be Prepared!

Preparation means not only preparation of your syllabus etc. but also look at the company's website and learn something about the company before you attend your interview.

5. Write down and practice possible questions!

If you collect the job interview sample questions and practice for it then it will make easy to remember when you get to the interview. Use the third person when talking about the job. Avoid sounding as though you assume the job is yours.

It is fine to ask about the package on offer and accommodation - living in and living out are particularly relevant. Do not forget to find out if the company will guarantee a resort or chalet - many will only allocate you a country. You could also try a fewer more testing questions such as how they differentiate themselves from their competitors or what they think the toughest/hardest part of the job is.

6. You never get a second chance to make a first impression!

First keep in mind that you never the second chance to make a first impression so be careful. 
Some points are here to remember:

· Smile is one of the thing which may matter in your impression. Good smile always please people.

· Dressing also an important thing. You should be in professional dress. And must be looking formal.

· Do not forget for firm handshake.

· Eye contact without glaring is showing your confidence.

7. Do not talk too much!

Always remember that communication is two-way things so give them a chance. Also don't interrupt to interviewer when he/she is talking. Give him/her full chance to talk.

One common mistake candidates make when interviewing is talking too much. It is important to listen to the question asked and answer that question. Keep your answers to two to three minutes at the most. When you limit your time, you tend to stay more focused. It is very easy to stray off the subject and ramble about things irrelevant to the job if your answer is too long.

Comments (0) | View (1542)

TCS is providing Global Internship for the students....go ahead for this one.

Through its Global Internship Program, TCS attracts undergraduate, post-graduate and PhD students from various disciplines for suitable internship programs matching their academic curriculum. The internships, ranging from eight to twenty four weeks, give the students an excellent exposure to various aspects of the Information Technology research and business. The TCS global Internship Program gives the students the jump start they need to take up challenging careers in the sector.

The purpose of TCS’ Global Internship program is to prepare the undergraduate, post-graduate and PhD students, across the globe, for a successful career ahead in Information Technology. This is enabled through on-the-job training on intellectually stimulating projects based on the curriculum.

Comments (2) | View (3846)

This is the first global index of employer attractiveness and highlights the world’s most powerful employer brands, thosecompanies that excel in talent attraction and retention. The global rankings are based on the employer preferences of students from Brazil, Canada,China, France, Germany, India, Italy, Japan, Russia, Spain, U.K., and U.S.

Comments (0) | View (3106)

Because Windows XP has to be all things to all people it has many services running that take up system resources that you will never need. Below is a list of services that can be disabled on most machines:

Alerter

Clipbook

Computer Browser

Distributed Link Tracking Client

Fast User Switching

Help and Support - (If you use Windows Help and Support leave this enabled)

Human Interface Access Devices

Indexing Service

IPSEC Services

Messenger

Netmeeting Remote Desktop Sharing (disabled for extra security)

Portable Media Serial Number

Remote Desktop Help Session Manager (disabled for extra security)

Remote Procedure Call Locator

Remote Registry (disabled for extra security)

Remote Registry Service

Secondary Logon

Routing & Remote Access (disabled for extra security)

Server

SSDP Discovery Service - (Unplug n' Pray will disable this)

Telnet

TCP/IP NetBIOS Helper

Upload Manager

Universal Plug and Play Device Host

Windows Time

Wireless Zero Configuration (Do not disable if you use a wireless network)

Workstation

To disable these services:

Go to Start and then Run and type "services.msc"

Doubleclick on the service you want to change

Change the startup type to 'Disable"

Comments (0) | View (1108)