Different Types of Interview Questions
Interview questions are designed to rate the skills and personality of a job applicant. There are different types of interview questions which aim to measure the qualifications of an applicant. Learn more on the different types of interview questions.
Companies use is a question of the interview setting tools to analyze the company needs a certain position of the candidate quality. These issues are specifically designed to complete large amounts of data obtained from the applicant know whether he qualified for the job. Interview questions have also been used to verify the applicant's curriculum vitae or resume of the information.
Interview prepared to interview, he asked all applicants to set. He will compare to his answers, and from there to measure who are the most qualified applicants. This is the human resources department who is usually prepared these issues. They have developed a set of standards for the answer, it is difficult to measure the qualifications of each applicant.
Interview questions depends on the company's preferences and needs. There is no standard or model of such problems. Basically, there are questions when interviewing job seekers at the interview may encounter different types. Interview these types of problems their respective candidates of different quality targets.
Credential Authentication Questions
This type of interview question aims to gather enough information on the applicant's previous background. Common question includes "How long have you worked at the company?"
Work Experience Questions
These types of questions aim to evaluate a job applicants' working experience with previous employers. It raises questions related to duties and responsibilities performed with the previous work.
Work Competency Questions
The most frequently asked questions of this type include,
Opinion Questions
In some cases, interviewers would raise opinion questions to see how an applicant responds to certain scenarios. The interviewer usually provides an example scenario wherein he will ask questions like "If you encountered this problem, what would you do? What are your strategies?" In this type of question, the interviewer may ask the applicant on his or her strength and weaknesses.
Dumb Questions
Some interviewers use dumb questions just to test the applicant's ability to think instantly. This type of question does not have any right or wrong answers. Some of the common questions used are "What is the color which represents your personality?" "If you were given a chance, what animal do you like to be, and why?"
Mathematical Questions
Mathematical questions are basically given in order to measure the mental quickness of the applicant. It also evaluates the ability of formulating mathematical procedure. It also measures how alert an applicant is in mental thought processes.
Case Questions
Case questions are assessed on the problem-solving skills of an applicant in certain situations. Examples of the questions used include
Behavioral Questions
This type of question is usually used by many companies. Most companies give greater importance on the behavior of its applicants rather than the skills because they believe that an applicant with good behavior can be trained in terms of skills. It is basically designed to predict the future behavior of an applicant by basing it with its past behaviors. Questions used with the interview include "Give specific experiences of how you have handled such situations. What are the specific steps you have implemented in order to finish the task?"
As a job applicant, it is best to be well prepared before any job interview. As much as possible, review the contents of your resume. When undergoing an interview, you must have self confidence and answer questions in a relaxed manner.
Different Types of Directives in Dot Net
@Page directive:
Defines page-specific attributes used by the ASP.NET page parser and compiler. Can be included only in .aspx files and also define the page language used just like c#,VB etc.
@ Control: Defines control-specific attributes used by the ASP.NET page parser and compiler. Can be included only in. Ascx files.This Directive also the view state of the page.
@ Import: import explicitly control a namespace into a page or a user. The Import directive can not be more than one namespace attribute. Multiple namespaces, use multiple @ Import Import directives.Its help when importing files.
@ Implements: Indicates that implements the current page or user control of the specified. NET Framework interface.
@Register:
And naming space and in a custom server control syntax.We simple symbolic class name of the alias Associates can register with the Register directive is also user-controlled help.
@ Assembly: Links an assembly to the current page when writing, making all the band classes and interfaces available for use on the page.
@ OutputCache: Declarative controls the output caching policies of an ASP.NET page or a user control contained in a page
@ Reference: Declaratively indicates that another user control or page source file should be compiled and linked dynamically at the page stating this Directive.
To learn about Web Services Interview Questions visit dotnetquestion.info
Be Prepared For Any Interview Question
Things can go really against you despite your thorough preparation for a just a couple of ‘types' of interview questions. However, it is possible to ignore or forget the other types of possible interview questions. This brings us to different ‘types' of interview questions, along with traditional questions or questions pertaining to your core skills.
Types Of Interview Questions
If you are able to predict the types of questions may go up to the interview is important. Let's try to categorize them into three types:
1. ‘Out of the box' questions and hardcore questions are the traditionally asked ones that cannot be readily anticipated. They may or may not be related to the job at hand, and are designed to see how well you can ‘think on your feet'.
2. Questions That Test Behavior And Problem Solving Abilities. These aim to find how you have conducted yourself in difficult situations and how will you do if the situation were to repeat itself. Interviewers always want to test you for unexpected and accidental circumstances.
3. Lastly, There Are Illegal Questions which are sometimes cleverly framed. These are aimed to find out your nationality, religious or ethnic background, marital status, etc. Illegal questions are not always intentional, but sometimes they are. The world isn't fair, and you may as well know this going in.
Sample Questions
Let's look at some samples from two categories:
Traditional Questions/Behavioral Questions
1. Tell us about yourself. In my humble opinion, the most overused and overworked, and unfortunately the most likely first question in any interview. This question can be manifested in any form. As there is no right or wrong answer to this, this is an open-ended question, most often used by inexperienced interviewers. However, if this question does come up (and you should assume that it will), then stick to answering strictly in business terms; NEVER volunteer personal information.
2. Why do you want to join us? This is another question belonging to the same category as the earlier one but usually follows it. As such, it is routinely predictable and you should have your answer ready. You need to list the benefits of your joining them from both points of view (the employer's first, then yours).
3. How would you describe yourself? Adopt a realistic approach towards this question and use adjectives like ‘honest', ‘hard working', etc., instead of the overused/ambiguous answers like ‘courageous' or ‘results-oriented'.
4. ‘Describe a situation which demanded working overtime' (or any variations on this question). If you have been in the corporate world for any length of time, you should have encountered this scenario. This question is devised only to see how you will possibly conduct yourself, as the new employer is probably anticipating similar situations happening should you be hired.
5. ‘Tell me about a decision that you made which was a bad one'. This may well be a hypothetical question. But if you had had made a bad decision, a ‘positive you' will explain this in a structured mixture of truth, admission, failure analysis and so on. In other words, logically turn a potential negative answer into a positive one - avoid making yourself look incompetent at all costs.
Let's take a look at some possible illegal questions. Employers know that they do not believe, ask them, but (a lot anyway, and some in different variations, in order not) to overtly illegal:
Illegal Questions
Six. Their religion, or prevent you from working weekends? (Overtly illegal question)
7. Do you plan to have children? (your marital status, or perhaps to reveal your sexual orientation), designed
8. When / Where were you born? (A search for your age or race smart way)
9. Your last name sounds unusual, do you come from? (Designed to show your ethnic background)
As a job seeker, you will invariable come across all types of interview questions. There are as many different types of questions as there are interviewers. It pays to be aware of the many types of questions that you will encounter - doing so will ensure that you handle such questions with confidence.
Introduction to Node Types in XML
To make XML as complete and as efficient as possible, it can contain various types of nodes. The categories or possible types of nodes are identified by an enumeration named XmlNodeType. If you use an XmlTextReader object to scan a file, when calling Read(), the class has a property named NodeType that allows you to identify the node that was read. NodeType is a read-only property of type XmlNodeType and it is declared as follows:
public override XmlNodeType NodeType { get; }
Therefore, when calling the XmlTextReader.Read() method, you can continuously check the value of the XmlTextReader.NodeType property to find out what type of node was just read, and then you can take an appropriate action.
Elements Fundamentals
Introduction
An element in an XML document is an object that begins with a start-tag, may contain a value, and may terminate with an end-tag. Based on this, the combination of a start-tag, the value, and the end-tag is called an element. An element can be more than that but for now, we will consider that an element is primarily characterized by a name and possibly a value.
To support XML elements, the System.Xml namespace provides the XmlElement class. XmlElement is based on a class named XmlLinkedNode that itself is based on XmlNode. To access an XML element, you can declare a variable of type XmlElement but the main purpose of this class is to get an element from a DOM object. For this reason, the XmlElement class doesn't have a constructor you can use. Instead, and as we will learn, the other classes have methods that produce an XmlElement element you can manipulate as necessary.
In the previous lesson, we saw that every XML file must have a root and we mentioned that you could call the XmlDocument.DocumentElement property to access it. This property is of type XmlElement and, to access it, you can declare an XmlElement variable and assign it this property. Here is an example:
using System;
using System.IO;
using System.Xml;
namespace VideoCollection1
{
class Program
{
static int Main(string[] args)
{
string strFilename = "Videos.xml";
XmlDocument xmlDoc = new XmlDocument();
if (File.Exists(strFilename))
{
xmlDoc.Load(strFilename);
XmlElement elm = xmlDoc.DocumentElement;
Console.WriteLine("{0}", elm);
}
else
Console.WriteLine("The file {0} could not be located",
strFilename);
Console.WriteLine();
return 0;
}
}
}
This would produce:
System.Xml.XmlElement
Press any key to continue . . .
An XML element is represented in the XmlNodeType enumeration as the Element member. When using the Read() method of an XmlTextReader object, to find out if the item being read is an element, you can check whether the member of the current XmlNodeType is Element. Here is an example:
using System;
using System.IO;
using System.Xml;
namespace VideoCollection1
{
class Program
{
static int Main(string[] args)
{
string strFilename = "Videos.xml";
XmlDocument xmlDoc = new XmlDocument();
if (File.Exists(strFilename))
{
XmlTextReader rdrXml = new XmlTextReader(strFilename);
do {
switch (rdrXml.NodeType)
{
case XmlNodeType.Element:
break;
}
}while (rdrXml.Read());
}
else
Console.WriteLine("The file {0} could not be located",
strFilename);
Console.WriteLine();
return 0;
}
}
}