Common mistakes by Interviewer

Now-a-days am conducting few interviews for our organization. While sitting in the other side of the table, I've visualized why most of the interviews fail with me. But when conducting these interviews, most of the candidates are attending with self confidence that they are suitable for the mentioned role and attend without preparation.

When people do some real preparation, they tend to fail due to lack of awareness at the interviewer towards interviewing techniques. Having failed in many interviews, I've learned that the interviews fail because of the following...

• Reflection (or) Mirroring: The interviewer tends to see self within the candidate. The interviewer starts to compare self with the candidate and evaluate. This evaluation is totally personal. The yard stick for measuring the candidature is not generalized, but influenced.
  

  
   

• Template (or) Checklist: The interviewer has a template of a questionnaire. The interviewer measures the candidate with respect to the list of standard questions that are available within the checklist. Of course, this checklist would vary from different roles, but majorly depend on the predefined set. There the outcome is majorly with standard FAQs. The yard stick here helps to some extent but not in all means.
  

  
   

• Unprepared: This type of the interview always starts with, "Tell me about you". If this is the first question, I would ask them as, "What is the fun in submitting the profile before the interview". The only reason is that they are lazy to understand the candidate, and tend to ask questions as the interview progresses. These kinds of interviews are not in the control of interviewers but in the control of the candidates. If the candidate is smart enough to understand this situation, they will make use of this situation and sell themselves.
  

  
   

By any chance if I miss any, please let me know.

Security & Silverlight

Yes, am mentioning about Security at Silverlight applications. Well, most of the developers think that Security is not the feature of the application. and they claim that it is the responsibility of the framework on which they are developing, be it as .net or java or any other. Thus, they don’t even worry about why security should be the core of any application and it should be given prime attention.

Microsoft has an initiative towards security with in any software development life cycle. This initiative is known as SDL, Security Development Lifecycle. Their definition of SDL is neatly designed as displayed.

And also they have released a security guidance document for writing and deploying Silverlight Application. The document can be downloaded from this link. The TOC is some thing like this

Threat Modeling and the Security Development Lifecycle

Background of Web Security

Same-Origin Policy

Cross-Site Scripting Attacks

Cross-Site Request Forgeries (CSRF)

A CSRF Mitigation: Nonces

Silverlight and Web Security

Changes from version 1.0 to version 2.0

How Silverlight Works

XAML

XAPs.

The Silverlight Sandbox

EnableHtmlAccess

ExternalCallersFromCrossDomain

Silverlight Networking

Cross-Domain Policy Files

How to Maximize Safety of Cross-Domain Access

Trusting Third-Party Domains

LANs and Security Zones

Internet Explorer and the XDomainRequest Object

Sockets

FAQ

How can I safely display a Silverlight ad on my Web site?

Is it safe to load arbitrary XAML in my Web page?

Is it safe to load arbitrary XAML from managed code?

Is it safe to display arbitrary media in XAML?

Is it safe to allow users to upload arbitrary XAPs to my Web site?

How can I tell if a file is a Silverlight application?

Is it safe to render XAML or run XAPs on my server?

How can I make sure my XAP is loaded only from a specific domain?

Is it safe to hide secrets in my XAP?

Does the PasswordBox control protect the password in memory?

Where can I find documentation for these features and APIs?