Monday, April 12, 2010

Live Project Training

Live Project Training


Welcome to world of challenges.....
Get live project training with aptitude preparation.
Learn Software Cycles, Designs and Methodologies.....
The technologies available are  .NET, JAVA, J2EE, PHP

Write us @ swati.kulkarni@f1solutions.in
or contact on 9673991000

Avoid the Top 10 Interview Mistakes



The best way to avoid the most common and dangerous interview mistakes is to think ahead and decide not to make them... Read on for a whistle-stop tour of the top ten interview clangers!

1. Lying
Although it's tempting, it doesn't work. By all means gloss over the unflattering things. But out-right fibbing NEVER pays.

Mark Twain said: "If you tell the truth, you never have to remember anything." Think about it. They will catch you out later.

2. Slating your current company or boss
Fed up with your current job and would give anything to leave because they've treated you badly? Your job interview is NOT the time to seek revenge. Bear in mind that the interviewer will be listening to your answers and thinking about what it would be like to work with you. Ask yourself: do you like working with people who constantly criticise others? Isn't it a bit wearing? The trouble is that the interviewer draws massive conclusions from your answers. So your throwaway comment about your boss or employer may be interpreted to be your "standard" way of thinking. It makes you look bad, not your employer.

3. Being Rude
If you find you were accidentally rude, then apologise calmly and genuinely. Then leave it behind you and get on with the rest of the interview. If you dwell on it, it will affect your performance. What's "rude"? Well, that depends on your audience. As a rule of thumb, avoid cracking jokes about potentially sensitive topics and beware of being too "pally" with the interviewer: polite and friendly is enough. After all, you're not in the pub with them. So stay professional. Also bear in mind that everyone you meet could be involved in the selection process. So blanking the receptionist or talking down to the junior members of staff could cost you the job.

4. Complaining
Ok, so your train journey might have been a nightmare and maybe you thought the tube would never arrive, or the tailbacks on the motorway were endless. But your interviewer doesn't want to know that!
Complaining, even in jest, is not a recommended icebreaker. It may be completely harmless, or it might simply make the interviewer switch off. Don't let complaining set the tone for the interview!

5. Talking about people you don't get on with at work
These days, it's common to be asked how you deal with conflict. Companies realise the importance of interpersonal relationships in the working environment. So if they ask you about difficult people or situations, make sure you hold back from character assassination and blaming others for problems because it won't do you any favours! If you accidentally do "break" this rule, apologise and explain what you "really" meant.

6. Not Being Prepared
Re-read the relevant version of your CV and the job advert, just before the interview. You'd be surprised how many people can't remember what they wrote on their CV. And if you remember what type of person the job advert was looking for, it's easier to demonstrate that you have those qualities.
Make sure you've brought with you anything you were asked for. It's fine to bring a note-pad and pen, but make sure they're tidy. It's even ok to bring notes with you; particularly if you have any questions you want to ask. It shows you're taking the job application seriously. Ill-prepared candidates rarely get job offers.

7. Appearing to be too nervous, or too confident
If you appear too nervous they'll think you're not confident enough to do the job. However, appearing too confident will make them think you won't fit into the team. If interview nerves are an issue for you, it's worth getting practical help from a professional, such as an interview coach.


8. Making a weak first impression
Unfortunately, no matter how hard the interviewer tries, a lot of "don't want to hire them" decisions are made in the first few minutes of contact. If you make a strong first impression, the interviewer will be more inclined to overlook "imperfections" in your answers.

9. Not having researched the company

As a general rule, the more famous the brand, the more they will expect you to have done your homework. Researching the company shows you're serious about the job.


10. Putting your foot in it and not noticing
Yes, we know, you didn't mean to put your foot in it. But it doesn't really matter what you intended. What counts is how the other person reacts. So what can you do? Be prepared to simply say "sorry, that's not what I meant!" This requires you to actually be paying attention to the interviewer, rather than your own thoughts and feelings. Once you've apologised, leave it there, take a deep breath to help you relax and move on with the job interview

Friday, April 9, 2010

Most Popular OOP Questions

Q:    State the significance of public, private, protected, default modifiers both singly and in combination and state the effect of package relationships on declared items qualified by these modifiers.
A:    public : Public class is visible in other packages, field is visible everywhere (class must be public too)
private : Private variables or methods may be used only by an instance of the same class that declares the variable or method, A private feature may only be accessed by the class that owns the feature.
protected : Is available to all classes in the same package and also available to all subclasses of the class that owns the protected feature.This access is provided even to subclasses that reside in a different package from the class that owns the protected feature.
default :What you get by default ie, without any access modifier (ie, public private or protected).It means that it is visible to all within a particular package.

Q:    What is an abstract class?
A:    Abstract class must be extended/subclassed (to be useful). It serves as a template. A class that is abstract may not be instantiated (ie, you may not call its constructor), abstract class may contain static data. Any class with an abstract method is automatically abstract itself, and must be declared as such.
A class may be declared abstract even if it has no abstract methods. This prevents it from being instantiated.

Q:    What is static in java?
A:    Static means one per class, not one for each object no matter how many instance of a class might exist. This means that you can use them without creating an instance of a class.Static methods are implicitly final, because overriding is done based on the type of the object, and static methods are attached to a class, not an object. A static method in a superclass can be shadowed by another static method in a subclass, as long as the original method was not declared final. However, you can't override a static method with a nonstatic method. In other words, you can't change a static method into an instance method in a subclass.

Q:    What is final?
A:    A final class can't be extended ie., final class may not be subclassed. A final method can't be overridden when its class is inherited. You can't change value of a final variable (is a constant).

Q:    What if the main method is declared as private?
A:    The program compiles properly but at runtime it will give "Main method not public." message.

Q:    What if the static modifier is removed from the signature of the main method?
A:    Program compiles. But at runtime throws an error "NoSuchMethodError".
    
Q:    What if I write static public void instead of public static void?
A:    Program compiles and runs properly.

Q:    What if I do not provide the String array as the argument to the method?
A:    Program compiles but throws a runtime error "NoSuchMethodError".
    
Q:    What is the first argument of the String array in main method?
A:    The String array is empty. It does not have any element. This is unlike C/C++ where the first element by default is the program name.

Q:    If I do not provide any arguments on the command line, then the String array of Main method will be empty or null?
A:    It is empty. But not null.

Q:    How can one prove that the array is not null but empty using one line of code?
A:    Print args.length. It will print 0. That means it is empty. But if it would have been null then it would have thrown a NullPointerException on attempting to print args.length.

Wednesday, April 7, 2010

7 reasons for interview failure

 1. Lack of preparation
Of all the reasons, this is the foremost one. It includes carrying improper CV, inappropriate dress code, completely unaware of interview questions and positive answers etc. By improper CV I mean, a CV which is not aligned well, or handwritten.
Walking into interview room in casual wear is also one of the key reasons for people to get rejected.
 2. Casualness
Let us cross the bridge when it comes' does not apply to interviews. One needs to be geared up 100 per cent before the interview. I have seen few candidates saying 'I will learn everything by experience. I am confident that by 'Law of average, if I attend 10 interviews, I will crack at least one'. This attitude could prove lucky for few initially, but not for everyone at all times. The interview preparation should be given due respect it deserves.
 3. Failing to understand the job role
This is a typical problem with a few of the candidates. They are completely unaware of what the job requires one to do. If a person does not understand his/ her role properly, he cannot justify his suitability for the job. If you are going through a consultant or got an interview call from the company directly, get the job description completely. In the event of responding to walk-in ads in newspaper, if you are not sure about the job description, spend some time on the Internet to know about your role.
 4. Lack of skills
I am sure most of you would have read reports published by NASSCOM, HR experts & corporate professionals that more than 70 per cent of the candidates lack in employability skills. A good qualification alone is not sufficient, but host of other skills such as good communications, interpersonal skills, analytical abilities, personality etc. are also vital. Unfortunately most of the candidates realise this very late.
 5. No proper focus
During the interview, some candidates lose out, because they are not able to convince the employer about their interest in the position applied for. If you are applying for a job in marketing, stay focused on it. Some candidates even put fields of interest as marketing, administration and accounts. Therefore, in the event of you being open to any career, prepare different types of CVs for different fields.
 6. Lack of subject knowledge
Irrespective of you being a fresher or an experienced professional, revisit your subject before going for the interview. There are many chances that you will be asked questions from your subject, more particularly, if you are applying for a career related to the course you studied.
 7. Lack of confidence
When the candidate uses too many negative words such as, 'I am not sure', 'May be I can', etc., it does portray lack of confidence to the employer. The negative gestures or negative body language plays spoilsport in your selection. Instead use words such as 'Surely', 'I can do it', 'It's challenging but I can do it' etc.