Skip to main content

Who is Qualified to Interview new Hire ?

This article is very specific to IT Industry.

 1. Focus 
We all focus on how to find the best hire and if we don't have qualified people to find them then we never gonna find good people.


2. Problem
I believe not everyone is qualified for this job. "Non-Qualified" people are not qualified only in interviewing new hires and they might be good for what they were brought in. So what is the impact of having Non-Qualified people in an interview process ?
  1. They will add no value to it
  2. They will waste their and someone else time
  3. If there are more non-qualified people in the process they will certainly end-up with one more
  4. In a democratic process their bad vote weaken's a good one
  5. Their contribution most of the time will be negative*

3. So why Non-Qualified people are part of the process ?
  1. Management takes this too casually 
  2. Too busy
  3. Don't realize the high cost of hiring and firing *

4. How to spot Non-Qualified People ?
  1. Often they take things personally and screw conversation
  2. No respect for people's works
  3. They like to disprove person rather understanding his skill level
  4. Not honest, and will not hire better then them


4. How to find Qualified People ?
  1. They should be good listener and honest otherwise they shouldn't get a solo ride
  2. Any person part of the interview should have a clear role defined and document what purpose it serves and review this document over time
  3. Manager or Director who requires new hire should be part of all interactions with the finalist, since ultimately he/she is responsible*
  4. Any person part of the interview should provide a written report that should be referred in future if you start disliking the candidate
  5. No Solo interview assignment should be given to any person until most senior and qualified member (Manager or Director) approve and judge his ability in half a dozen interviews.






Comments

Popular posts from this blog

JPA 2 new feature @ElementCollection explained

@ElementCollection is new annotation introduced in JPA 2.0, This will help us get rid of One-Many and Many-One shitty syntax.

Example 1: Stores list of Strings in an Entity

@Entity
public class Users implements Serializable {

    private static final long serialVersionUID = 1L;
    @Id
    @GeneratedValue(strategy = GenerationType.AUTO)
    private Long id;
@ElementCollection
    private List<String> certifications = new ArrayList<String>();

    public Long getId() {
        return id;
    }

    public void setId(Long id) {
        this.id = id;
    }

    public List<String> getCertifications() {
        return certifications;
    }

    public void setCertifications(List<String> certifications) {
        this.certifications = certifications;
    }
..
}

        Users u = new Users();
        u.getCertifications().add("Sun Certified Java Programmer");
        em.persist(u);

Generated Tables

   Users
Column --> ID
    Row             1

Users_CERTIFICATIONS

Validating CSV Files

What is CsvValidator ?
  A Java framework which validates any CSV files something similar to XML validation using XSD.

Why should I use this ?
  You don't have to use this and in fact its easy to write something your own and also checkout its source code for reference.

Why did I write this ?
  Some of our projects integrate with third party application which exchanges information in CSV files so I thought of writing a generic validator which can be hooked in multiple projects or can be used by QA for integration testing.

What is the license clause ?
GNU GPL v2

Are there any JUnit test cases for me checkout ?
 Yes, source

How to integrate in my existing project ?

Just add the Jar which can be downloaded from here CsvValidator.jar and you are good.

Instantiate CsvValidator constructor which takes these 3 arguements

         // filename is the the file to be validated and here is a sample         // list - defines all the fields in the above csv file ( a field has index, type, isOptional, rege…

ArrayList vs LinkedList vs HashSet Performance Comparision

ConclusionsInserting & Reading sequentially from Collection prefer LinkedList/ArrayListInserting & Reading/Deleting by Search/equals from Collection prefer HashSetInserting, ArrayList & LinkedList performs best while HashSet takes double the timeReading, HashSet performs best while ArrayList & LinkedList are marginally lessDeleting, HashSet performs 10 times better than ArrayList & ArrayList performs 4 times better than LinkedList. LinkedList is slow because of sequencial search Bottom line : unless you are not going to iterate using for(Integer i : list ) then prefer HashSet
Inserting/Reading/Deleting integer's from zero till countJDK7Collectionactioncounttime msArrayListInsert1000/1LinkedListInsert1000/1HashSetInsert1000/1ArrayListInsert100005LinkedListInsert100004HashSetInsert100007ArrayListInsert10000011LinkedListInsert10000011HashSetInsert10000021ArrayListGet/Read1000LinkedListGet/Read1000HashSetGet/Read1000ArrayListGet/Read100004LinkedListGet/Read100003Has…