Tuesday, November 8, 2011

Don't stop believing...

For my wife's birthday we bid on, and won a Starwood moment, using Starwood Preferred Guest (SPG) starpoints.  The "moment" we won, was to see Journey in concert in Mountain View, California, which is their home town.  This is the equivalent of seeing Soundgarden in Seattle or seeing Boston in Boston (lol). 

Even though not all of the original members of Journey are with the band (Steve Perry has moved on and Arnel Pineda is the new front man), Journey still sounds awesome.

We began our day getting up at 8 AM and throwing our bag in the car, headed to Seatac airport, and checked in for our flight.  We upgraded our seats to first class for the way down.  We flew Virgin America. 

If you haven't been on a Virgin flight you should try it.  The inside of the plane feels like you're entering a swank lounge like 'The Sky Bar'.  The interior panels are all white (not the oatmeal color of most aircraft), the seats are white and black leather, and hidden mood lighting gives the inside a pink and purple glow as 'chillout' lounge music permeates the air.   Our flight took off at 11:00 am and on the way we enjoyed a couple drinks, a movie and a light lunch.

We arrived in SFO at 2:45, took a tram to our rental car and started driving down to the W Silicon Valley.  The drive took about 20 minutes, and took us past the new headquarters of Facebook (whose sign is just a big "like" thumbs up icon).  We checked in and were upgraded to their suite, where they brought Cindy some birthday cake.

We had to be at the stadium before 6:00 PM so after a few bites of cake and ice cream, we jumped in the shower and got ready to go. 

Mountain View's Shoreline Amphitheatre is just past the main campus of Google, so we saw that too.  We called our representative from the SPG moment at the Stadium and asked where to park.  He directed us to a VIP parking section and brought us our tickets and credentials to meet the band.  The Amphitheatre has several open air bars inside and many booths with carnival/fair food and booths from sponsors and companies. 

We had a Philly cheese steak sandwich which wasn't quite worth $10.00 ...but what can you expect from a booth outside a concert.

Our credentials said 6:30, so we got to a place behind the About.Me bar where we would be escorted to meet the band.  Our escort showed up a t 6:20 and led us back-stage down a flight of stairs.  At the foot of the stairs was a line for photos with the band, and a wine maker and an artist who designed a huge magnum wine label commemorating the tour.  The wine was from Williams Selyem and I met Bob Cabral, the Director of Winemaking and General Manager of the winery.  The picture of me is with the artist who did the label but he didn't have a business card, perhaps I can get his name from Bob.

Then we got our picture with the band.

After the photos, we found ourselves at the About.Me bar (about dot me).  If you haven't checked out about.me and you're into social media, you should.  It's a place where you can consolidate links to all of the places people can follow you, and they'll even give you some free business cards if you create a site.  The bar had a professional photographer and backdrop, and was running a promotion to upgrade your seats to their special 'box seats' if you created an about.me account.  - We did, you can check us out:  http://about.me/kenmizell and http://about.me/cindymizell

We ordered a couple of lemon drops there and then headed to our seats.  On the way into the stadium we passed by the About.Me box seats and walked even CLOSER to the stage (I guess we didn't need an upgrade).   Our seats were next to a guy who had been a roadie for Journey (and several other bands) in the 1980's.  He told us a few interesting stories before the lights went out and the first band started. 

The concert began with Night Ranger. 

What was great about this whole concert, with Night Ranger, then Foreigner, and finally Journey, was that we knew the words to almost every song they played.  They were all songs from our high school days, and skating parties.  Songs like "Sister Christian" and "Urgent" and "Don't Stop Believing".

Night Ranger finished their set and Foreigner started.  During the Foreigner concert the singer walked into the crowd and stopped about 3 rows directly in front of us.  Cindy got a few great pictures of him. 


By the end of their set our drinks were empty.  So I headed out to the About.Me bar to get a couple more  between Foreigner and Journey.  When I arrived, Joel Hoekstra was getting his picture taken for an about.me page.  I got a video of him checking out his picture. 


I headed back to our seats and we sang along to the Journey songs.  Giant beach balls bounced throughout the crowd, some ending up on the stage and being punted by the band back into the crowd.  I was amazed at the new singer.  Pineda sounds just like Steve Perry.  Every song sounded just how you remembered it.

It was a great night.  We got in the rental and headed back to the W and had a couple more lemon drops before heading up to our suite.  The next day we had a late checkout and headed back to the airport.  We were home by 5:00 Sunday night.

Wednesday, October 5, 2011

What's wrong with the iPhone [Integer] [Optional modifier]?

Humans are funny animals.

For weeks many iPhanatics have been awaiting the launch of the next thing from Apple. But even on twitter you can hear the echoes of people's disappointed, (some even angry) facebook posts; that apple didn't launch the iPhone 5 but instead launched the iPhone 4s.

So what's in a name?

I'm reminded of a TED talk by a former ad man Rory Sutherland where he talks about intangible value or subjective value.

Advertising adds value to a product by changing our perception, rather than the product itself. Rory Sutherland makes the daring assertion that a change in perceived value can be just as satisfying as what we consider “real” value -- and his conclusion has interesting consequences for how we look at life.
- TED

In this case it seems that a change in perception about the value (via the label) can be just as dissatisfying as if someone just gave you back your old iPhone and called it new.

People with iPhone (previous) were all anticipating the iPhone 5 because they wanted things like:
* a better camera (well actually the best camera available on a phone)
* a new lens
* video image stabilization
* face recognition
* quicker access to the camera (from the lock screen) so you don't miss shots
* two antenna types so you can go from CDMA to GSM networks seamlessly
- and get off at&t
* a faster processer (you know what make it a dual core processer)
* a newer, faster operating system
* 7 times faster graphics on the screen
* 2 times faster browsing (processor load time - not network time)
* some wow factor feature that my android friends can't have
- (like siri - the ability to tell your phone to 'wake me up at 5:35' or 'remind me to get milk when I'm near a grocery store')
* and 200 other new things

The iPhone 4s has all of these things... but it has a smaller integer than they wanted in its name.

Sad.

I still want one.

I was an iPhone first generation owner but switched to Android last year (for a bigger screen and better camera - and to get away from at&t). I was waiting for the iPhone 5 so I could have an iPhone that could work on another network besides at&t, like sprint... Oh, wait... the 4s does have that.

-legal disclaimer: I own several shares of apple stock in my sharebuilder account - but that's not why I wrote this post. I wrote it because of the whining. :)

Sunday, June 26, 2011

Social Media and the Limelight

This has been burning in the back of my mind since I dove into the deep end of the twitter pool earlier this year, ...or should I say, tried to learn to drink from a fire hose?!?

I've been a Rush fan since I was in high school, (The band, not the fat, conservative, radio talk show host... though my dad listens to him a lot). One song in particular has been playing in the back of my mind as I'm learning about #socialmedia and marketing. The song is Limelight. Its lyrics are so fitting to the times today that it makes me wonder if Geddy Lee, Neil Peart, and Alex Lifeson were actually seeing into the future when they wrote the song in 1981.

Here's the lyrics in their entirety:
************************************

Living on a lighted stage
Approaches the unreal
For those who think and feel
In touch with some reality
Beyond the gilded cage.

Cast in this unlikely role,
Ill-equipped to act,
With insufficient tact,
One must put up barriers
To keep oneself intact.

Living in the Limelight,
The universal dream
For those who wish to seem.
Those who wish to be
Must put aside the alienation,
Get on with the fascination,
The real relation,
The underlying theme.

Living in a fisheye lens,
Caught in the camera eye.
I have no heart to lie,
I can't pretend a stranger
Is a long-awaited friend.

All the world's indeed a stage,
And we are merely players,
Performers and portrayers,
Each another's audience
Outside the gilded cage.

*********************************
Here they are with my commentary:

Living on a lighted stage
Approaches the unreal
For those who think and feel
In touch with some reality
Beyond the gilded cage.

Cast in this unlikely role,
Ill-equipped to act,
With insufficient tact,
One must put up barriers
To keep oneself intact.

This is how I felt as I 'decided' to learn 'social media and marketing'. At first I began blindly following back everyone that followed me (including spammers). I notice that a lot of people do have 'insufficient tact' especially on EmpireAveue with the "BUY ME" posts and on twitter with the "Buy my product" tweets, but its prevalent on facebook and LinkedIn as well .


Living in the Limelight,
The universal dream
For those who wish to seem.
Those who wish to be
Must put aside the alienation,
Get on with the fascination,
The real relation,
The underlying theme.

'The universal dream'of having; a high Klout score, a high stock price on EmpireAvenue, people reading your blog, people following you back, ...people actually LISTENING to what you have to say. And it appears that 'Those who wish to be' really must get on with 'The real relation'. You must actually listen to those you follow, relate, engage, and add value. You must engage in a way to develop actual friendships. It isn't enough to 'seem' the part, to truly learn social media and marketing, you must 'be' that which you are attempting to study. You must actually listen to your customers, and attempt to listen to the world.

Living in a fisheye lens,
Caught in the camera eye.
I have no heart to lie,
I can't pretend a stranger
Is a long-awaited friend.

This lyric makes me think of the LinkedIn LION (LinkedIn Open Networker), those who will connect with anyone whether they know them or not. On twitter it seems more acceptable to follow, and have followers who you don't really know, but to me, LinkedIn and facebook, are reserved for those who I've actually had real interaction with prior to the social networking site. Facebook is like my living room in my home. LinkedIn is like my office at work. I don't have the general public walking through them. 'I can't pretend a stranger is a long-awaited friend.' As Jeffrey Gitomer says "All things being equal, people like to buy from friends." ...and "All things being not-so-equal, ...people STILL like to buy from friends." I have made some real friends by beginning this learning experiment. I hope to make more. When I am caught in the camera eye, I have no heart to lie, I truly want to meet more people and help those I can, and make genuine friends.


All the world's indeed a stage,
And we are merely players,
Performers and portrayers,
Each another's audience
Outside the gilded cage.

Ok, Shakespeare started this... but Rush finished it. It seems very apropos. I cannot possibly have enough thoughts everyday to keep an audience engaged (even if I did, I wouldn’t have time to blog about them and still do my job). I have to promote those new 'friends' who have good ideas as well. I have to rely on friends. Each another's audience... I share my audience and their content, and some of my audience members are those on stage. We each take a moment in the limelight from time to time, and together, we gain understanding, we make each other better (likes, follow Friday, shares, etc.) @bradyjosephson has this down

Thank you in advance for making me better. I'm still listening.

Friday, June 17, 2011

Welcome to EmpireAvenue

Hi all.
I started investigating EmpireAvenue last week as a measurement tool of influence on social media.

To connect my blog I must verify I'm actually ME by posting this key into my latest post {EAV_BLOG_VER:481ea537e5c9f389} .

EmpireAvenue uses a stock market model to set the 'price' of individuals based on their activity in social media sites and based on the demand for their 'stock' in the market. Unlike Klout which uses a formula to calculate a score, EmpireAvenue follows a more free market model. It isn't perfect, however, in EA you can actually use real money to buy more 'eaves' (their virtual currency) and pad your account or make more investments, so you can game the system to an extent, though I don't imagine many people will be willing to trade real dollars for a trumpped up score (but I may be wrong).

If you want to invest in me my stock symbol is KENM and I trade on the socialmedia exchange at www.empireavenue.com

Happy Trading!

Thursday, May 26, 2011

Interviewing 101 - for Candidates

GOALS OF THE INTERVIEW

Goals of the Candidate (you):
• To gather information about the job and the organization.
• To determine whether the job is suitable (inline with your values, interests, and abilities)
• To find out whether you want it.
• To communicate important information about yourself.
• To favorably impress the employer.

Goals of the Interviewer:
• To promote the organization and attract the best possible candidate.
• To gather information about the candidate.
• To assess how well the candidate's qualifications match the job requirements.
• To determine whether the candidate will fit in with the organization and the staff.

PREPARATION FOR THE INTERVIEW
1. RESEARCH THE ORGANIZATION
Find out some basic information about the organization before you go for the interview. You will be in a better position to ask intelligent questions and you will impress the interviewer with your initiative and your knowledge of the organization.

2. RESEARCH THE JOB
Employers often list more qualifications in the job posting than can realistically be met by most potential candidates. Frequently, this is done as a pre-screening device in order to reduce the number of inept applicants. You should not allow this to discourage you or prevent you from pursuing the position.

As you are looking for the ideal job, employers are looking for the ideal employee. Analyze the job description and match your experiences, skills, interests, and abilities to the job. You may find that some of the qualifications are less essential than others. Emphasize your strong points to minimize the effect of possible limited experience.

Talk with people who have worked in similar positions in that organization or in other companies. Read about the specific job category in the career literature. As a result of your research, you will have gained information about the nature of the job, the level of education and/or training necessary, future potential, and other pertinent details. Also check out http://www.glassdoor.com for reviews on employers.

3. PREPARE AND ANTICIPATE QUESTIONS
Anticipate questions that may be asked of you in an interview. Prepare answers beforehand to some of the more difficult or sensitive questions. This does not mean memorizing responses or writing a script. It does mean planning the points you want to make. Also, prepare questions you would like to ask the employer, or learn to "piggyback" questions during an interview.
For example, if an interviewer asks, "How are your skills with Microsoft Word?" You might want to ask, "Which version of Word is in use? Let the interviewer answer questions throughout the interview! It will give them the feeling that they are in a conversation, rather than just quizzing you. It also serves to elevate yourself to a peer level - in their eyes! Also sometimes interviewers ask purposefully vague questions to see if you jump to conclusions or if you clarify things before answering.
4. PRACTICE GOOD COMMUNICATION SKILLS
It is important that you use good communication skills during the interview. Practice with a friend, with a career counselor, or by videotaping a mock interview. Work on the following communication skills:
• make and maintain comfortable eye contact.
• present yourself in a positive and confident manner
• offer a firm handshake
• speak clearly and effectively
• be concise and get to the point
• avoid non-professional slang terms/ jargon. (Example: Cool, Awesome, Sweet, any cursing)
• listen attentively, you have two ears and one mouth, use them in that order
• avoiding the use of unnecessary verbal and non-verbal distractions
5. DRESS APPROPRIATELY
Dress professionally for the interview. Remember that you don't get a second chance to make a first impression. Your appearance should be neat and clean, pressed and polished. Conservative business attire is appropriate for most settings.
6. BE PUNCTUAL
Be on time for the interview. Plan to arrive about fifteen minutes early. Check in with the interviewer or the secretary about five to ten minutes prior to your scheduled appointment. Use your waiting time to check your appearance, review the questions and answers you prepared, and read any company literature that may be on display. Take advantage of this time to get a feel for the work environment by observing the surroundings and interactions among staff.
THE STAGES OF THE INTERVIEW
Regardless of the style of the interviewer, the interview will progress through four basic stages: the introduction, sharing general information, narrowing the focus, and the closing.
Introduction -- begins with small talk initiated by the interviewer. The interviewer may ask a few casual questions or make some general remarks. The purpose is to put you at ease, establish rapport, and find a comfortable level of communication.
Sharing general information -- starts when the interviewer shifts from small talk to general information about you, the organization, and the position. You may be asked to review your background, interests, and goals. The interviewer will discuss the organization and its goals. This will test your listening and speaking skills as well as give you additional information on which to base intelligent questions.
Narrowing the focus -- occurs when the interviewer begins concentrating on the job and how you might fit in. You have the opportunity to expand upon your skills and to demonstrate how they apply to the job requirements. Your efforts in researching the job and the organization will pay off at this point.
Closing – This happens when the interviewer begins summarizing what has been said and clarifying certain aspects of the interview. It is crucial that you express your interest in the position at this time. It is also important that you review the points you've made especially about how you are uniquely qualified for the position. If you have relevant skills or experience that you have not yet shared, do it now. The employer will probably explain how and when the next contact will be made and may end with, "Do you have any other questions?"
Try to save at least one of your questions for the end so that you wrap-up the interview on a positive note, leaving an enthusiastic impression. The questions you ask here tell the interviewer a lot about your intelligence, and your interest level in the position. Make sure you think of some good ones.
TYPES OF INTERVIEWS
BASED ON PURPOSE
SCREENING INTERVIEW -- used to quickly and efficiently eliminate unqualified or overpriced candidates. Conducted by professional interviewers, recruiters, or personnel representatives seeking information regarding educational and experiential background using a highly structured question and answer format.
SELECTION INTERVIEW -- used after some type of screening process. Usually conducted by a professional practitioner who will be the candidate's supervisor. It is generally less formal and less structured than the screening interview. Questions tend to be open-ended with subsequent questions based upon candidate's responses to previous questions.
BASED ON FORMAT
ONE ON ONE -- usual interview procedure. Screening and selection interviews usually include one interviewer and one candidate. At times, a second company representative may join in or candidate may have a series of interviews that involve several meetings with different people within the organization, one at a time.
SEARCH COMMITTEE OR BOARD INTERVIEW -- group consists of many interviewers and one candidate. Used by business and industry for selection of high level corporate officers. Typical of a selection committee search in higher education.
GROUP INTERVIEW -- group consists of many candidates and one or more interviewers. Frequently used as a screening procedure by smaller companies and by graduate and professional schools. Used to assess leadership skills and ability to work in groups.

BASED ON STYLE
QUESTION AND ANSWER OR DIRECTED INTERVIEW -- highly structured; interviewer comes prepared with list of questions. Used by recruiters and professional interviewers to seek facts. Generally is format for screening interviews.
OPEN-ENDED OR NON DIRECTIVE INTERVIEW -- generally informal and less structured. Used by professional practitioners to assess candidate's skills, experience, and personality attributes. This is the usual format for selection interviews.
STRESS INTERVIEW -- staged to determine how candidate will perform under stress. It may be typified by long periods of silence, challenges to candidate's opinions, or a series of interruptions.
HANDLING DIFFICULT QUESTIONS
What questions do you dread being asked in an interview? Some of the more commonly asked dreaded questions include:
"What are your strengths and weaknesses?"
"Where do you see yourself in five years?"
"Why should I hire you?"
"Why do you want to work here?"
When you think about it, they are all legitimate questions. You may not have done sufficient soul searching or strategizing to handle them well, but each presents you with an opportunity to sell yourself.
It is helpful to look first at why they ask the questions and then to strategize a response.
"What are your strengths and weaknesses?"
The employer may be assessing how well you know yourself and how honest and open you are. You have an opportunity to showcase your strengths and also to reveal a not too serious weakness. It is best if you demonstrate how you are working to improve your stated weakness. For example, you might say, "My computer experience is somewhat limited. However, I recently took a week long training program on using the MAC and I'm looking forward to building on the skills I learned."
"Where do you see yourself in five years?"
They want to know if you are ambitious. If you find it hard to look five years out, try this: "Five years seems like a long time. I can see myself as a programmer analyst in two years. Five years from now, I might be a software developer or a systems analyst. I won't know which direction I want to take until I've been in the field for awhile."
"Why should I hire you?"
Here's where they find out how well you understand their needs and how confident you are of your qualifications for the position. How about a response like this one? "I think you should hire me because I have the skills you need in this marketing support position. My technical skills exactly match the requirements as I've been using your software in my Co-op job. And my interpersonal skills are strong as a result of my student government experience."
"Why do you want to work here?"
This is where the employer finds out how much you know about their organization. You want to convey your interest in contributing to their mission or in being part of an important project they've been awarded. For example: "I've read about your contract to develop tax accounting software for the federal government and I want to be part of the action..."
Then, there are those questions that you hope no one asks but they inevitably do -- important questions that demand a well-prepared response from you. For example, if your resume doesn't show continuous employment, you should expect to be asked for an explanation. What positive results came out of your decision not to work? An upbeat way to explain might be, "That's correct, I did not work in 1988. I was nearing the end of my degree program at Northeastern. I realized that if I attended school full time I could complete my bachelor's degree in one year, rather than working and taking three years to finish. I feel I made the right decision: when I went back to work, I was offered a salary considerably higher than my previous earnings."
Perhaps you were laid off last year, so you dread being asked why you left your last job. You want to frame your explanation in a way that dispels any shame or guilt you may be harboring. "I was one of 180 people laid off last September when XYZ Corporation went through a major downsizing."
What if you were fired for some reason? This can be very worrisome to the job seeker. "To be honest with you, I just didn't fit into the organization. Finally, my supervisor and I decided it was best for me to leave. While this was a devastating experience, I feel I'm ready to begin again."
These examples show honest, straight forward responses that will be acceptable to an employer. The important thing is for you to come to terms with the issue, see the positive side, and demonstrate that you are eager to move on in your career.
ETHICAL ISSUES
It’s illegal for employers to ask questions of a personal nature prior to employment. Whether you are married or single, have children, or belong to a certain religious group should have no bearing on your ability to do the job. However, this does not mean that you won't be asked illegal questions. Many interviewers have had little training and don't realize that they are asking improper questions; other interviewers know and ask anyway to see how you handle uncomfortable situations.
Please refer to your local authorities for information on the legal and illegal aspects of the following questions: name, age, national origin, race/color, citizenship, disability, and criminal record.
In Washington state: http://www.hum.wa.gov/documents/empflier.pdf
Also, you need to be aware of the regulations for drug testing, as they vary from state to state. You need to decide ahead of time how you feel about this serious issue. In most cases, the decision not to be tested will eliminate you from consideration for the job.
SALARY NEGOTIATIONS AND RESPONDING TO THE JOB OFFER
Salary negotiations often make candidates uncomfortable, and rightfully so, as this is one of the trickiest parts of interviewing. Normally, a good and competent recruiter will handle these negotiations for you. But, if you're out interviewing on your own, these are a few suggestions on how to manage this topic may eliminate some of the discomfort.
First of all, if the topic comes up too early in the interviewing process, it is advisable to postpone the discussion. For example, you could say, "I would be happy to discuss my salary requirements, but I feel I need to know more about the position first. Could you tell me about…" The idea here is to buy some time. Remember, you want to know first if you like each other - then you can find out if you can afford each other. Also, the more you know about the job, the better you will be able to pinpoint what it is worth in today's market.
Secondly, if you are in the final round of interviewing and you are asked about your salary expectations, it is appropriate to clarify, "Are you prepared to make me an offer?" Try to get the interviewer to commit to you as the preferred candidate. Your negotiating position will be greatly enhanced if you establish that you are their first choice.
Lastly, there comes a time when the negotiation can't be delayed any longer. Ideally, you know a lot about the position and how it compares in the market because you've done your homework, and you are the front running candidate. You are still likely to do better in the process if you aren't the first one to name a figure. You may be able to ask what they have in mind or what they have budgeted. If they tell you, for example, that the position is rated at $32,000 to $36,000, you can then say why you think you deserve to receive the higher end of the scale, based on your knowledge and experience.

Interviewing 101 - for Hiring managers

Interviewing 101

Why do we interview? What are we looking for? How do we find out if a candidate is worth hiring?

The basic goal of the whole interview process is to answer a binary question: Should we hire this person, yes or no? the secondary goal if the answer is YES, is to make sure that the candidate feels that our company is right for them.

There are two main questions that need to be answered:
Is this candidate the right person for the job? And if yes; Can we afford this candidate?

Is this candidate the right person for the job?
I like to think that besides looking for someone who can fill the need we have, we are also looking for someone with a set traits that are hard to learn or difficult to train. Why? If they are lacking some of these “hard to teach” skills then you will have a difficult time getting them to perform as you need them to (conversely if they are lacking some skills that are easy to teach and the candidate is “teachable” then you don’t need to interview for them – you can teach them later.)

So what skills or traits are hard to teach but necessary for a good hire?
I’ll list a few that I look for but this list can grow and change as our needs change so think of this as a guideline not a rule.
I Look for:
Smart – Intelligence
Teachable – Trainable
Driven – Goal Oriented – Successful
Integrity
Customer Focus
Passionate – (about their field or their business focus)
Fit – Personality
Communication – skills and style
Experience level – in the needed area

I feel that if a candidate has all of these then I can easily add in anything that is missing through training.

Smarts – this is a hard trait to test for in an interview directly. Most of the time I try to infer this from their responses to many of my questions. Overall did they seem smart? When my questions were vague, was the candidate able to infer the correct meaning? Did they ask the right clarifying questions?
One line of questioning that may help discern this is to ask them what they would do to accomplish a seemingly impossible task, like redesign a Java UI into .Net in a week. If they can come up with an answer of how they would tackle this seemingly impossible task then I would reduce the timeframe to the ridiculous “what if it had to be done in one day?” “One hour?” The Candidate should be able to demonstrate here that you are looking for them to prioritize, ask for help, come up with a contingency plan, and basically demonstrate how they would deal with the reality of the situation. Or ask them “What’s the most important thing you have learned in the last six months? What new skills, knowledge or experience have you gained?”

Teachable – This trait is very important because if they have it and are lacking in some other area you have a chance to turn an OK hire into a great hire.

This is easier to test for in an interview if you have a long time with the individual or if you have two interviewers coordinate the questions a little bit. An example might be:
1. Have the first interviewer to describe a system or an architecture that the candidate might be working on if they were hired. Draw a detailed drawing on the white board and explain each system early-on in the interview. You might use this drawing to ask other problem solving or trouble shooting questions throughout your interview. (Make sure the second interviewer knows ahead of time what system you will be describing and how you will be drawing and explaining it)
2. When the second interviewer comes in, have them erase the white board and ask the candidate to draw and explain the same system. If the candidate can remember and explain the system well, then you know that they are teachable. They were able to learn a new complex system in an hour or so. You can ask clarifying questions about the system like “what does this part do? Why is it important?” This will help you decide whether or not they actually learned something new.
An alternate approach might be to ask them when was the last time they had to learn a totally new system or technology. How long did it take them to learn it? Did they master this new system or are they still a novice? Or, ask them to tell you about the last time they asked someone for feedback. What did they do with that information?

Driven – you may be able to just infer this from the candidate’s mannerisms but some people can be more reserved. To test for this trait you might ask what professional accomplishments they are particularly proud of. A goal oriented individual should be able to tell you what goals they accomplished at their last place of employment. If they haven’t accomplished any then they are either not driven enough or they don’t set attainable goals. Either is a sign that this candidate may not be a top performer if hired.

Integrity – This is another hard to test for trait, but you can test for whether or not the candidate will stand by their convictions. A lack of integrity is easier to spot then the presence of it. If a candidate seems wishy-washy with their answers or seems to be telling you only what they think “you want to hear”. You may ask them a misleading question like “Don’t you think it’s better if (something counterintuitive that is not really better here)?” and when they agree then you can ask them why. Then you can tell them that you disagree, and see if they change their tune or stick by their conviction. Another question that could help with customer service as well is “Tell me about the last time you broke the rules to serve a customer in need.” This measures their judgment and flexibility.

Customer Focus – In our business as a solutions provider we need to be concerned that all of the people who represent us to our clients have an attitude of good customer service. Does this person naturally make you feel at ease or do you feel uncomfortable talking to them? Is their style of communication open and inviting? Can they see things from different points of view? Can they empathize? All of these traits are necessary when we want to continue our business relationships with our clients.

Passionate – This trait is important for retention purposes. Even if the person you are about hire is great at exactly what you need them to do, if they are not passionate about the industry, the technology, or some aspect of what they are doing they will eventually get bored and start looking for work elsewhere. It is important to ensure that the investment of time we are putting into finding good candidates is not wasted by hiring people who will not remain challenged and interested enough to stay with us.

So how do you test for this trait? I like to ask the candidate “what’s your dream job like?” or “Tell me what makes you get up in the morning and go to work?” you are trying to find something that tells you that the candidate wants to be in the line of work that they are in, something that says they are passionate about it and will remain interested in it.

Fit and Personality – how does this person fit into our company culture? Is there level of professionalism within our expected range? Do they seem like they would get along well with the teams and people with whom they would be interacting most? You can trust your gut a little bit here by asking yourself how comfortable you feel while talking with the candidate, but you can also ask some questions to find out more.

I like to ask a candidate to describe a situation at work where they knew they were right about something but that someone else was sure that they were wrong, then I ask them to tell me what the end result was and how the disagreement ended. I am looking for how reasonable the candidate was in seeking a resolution to the issue. Did they try communicating directly with the opposing party first? Did they explain their position and more importantly did they listen to the other party’s position? If that didn’t result in a resolution, did they escalate it through the proper channels or did they take passive aggressive measures? A good follow up question if you are still unsure about this is to ask the candidate to “Tell me about a time when you thought you were right and then later found out you were wrong.” Same evaluation principles apply.

Communication skills – This is a tough one but can be very important if neglected. You might have the smartest person in the world in front of you but if you can’t effectively communicate the ideas of our business or of a customer’s problem, then the solution they may provide might not really solve it. This is also a very important skill if the candidate will be in a client/customer facing position such as a team lead, PM, BA, or account manager. Here I like to ask the candidate to describe some complex process or system that lies within an area of our mutual expertise (so I will know if they got it right) and I ask them to explain it to me as if I were a 10 year old child with no technical background knowledge.

For testers or network admins I might ask them to explain how the internet works… “How does my computer know to show me the Disney home page when I type www.disney.com in to my browser address bar and hit return? What happens behind the scenes?” If the candidate can explain a complex subject accurately in simple to understand terms then I feel comfortable that they can teach others what they’ve learned, and communicate ideas successfully.

I also look for what I call a high “Get it” factor. If I’m starting to explain something in a question and I can sense that the candidate just “Gets it” and they do this repeatedly throughout the interview on many different subjects then this is another indicator of their communication skills (and smarts) on the intake side. Remember communication goes both ways.

Experience level – This will be different for each position. If we are looking for a DBA then the candidate should be able to write a complex SQL join. If we are looking for a .Net developer then they should be able to write a method or function to solve a problem. I expect each candidate to demonstrate at least one skill that they claim to be “experienced” in where that experience is the reason for me calling them to the interview. Here are some example questions for different disciplines:

1. Tester: I may ask a tester to test a pop can. If I did, I would be looking for them to come up with an exhaustive list of tests and to start grouping them in to categories such as: Functional testing, Performance and Load testing, Security testing, UI and Marketing, Limits testing, ad-hoc break-it cases, etc. I would expect a tester to keep coming up with more tests until I told them to stop as there are limitless things that could be done to a pop can if one had the time.
2. Developer: Write me a function that takes in an array of numbers and returns out the two numbers with the highest and second highest values of all the numbers in the array. Please don’t use any predefined sorting methods that may already exist, I want to see how you would solve the problem without those methods.
3. SDET: I would ask them the developer question above, and then ask them to test their own function and show me the actual array data sets that they would use and tell me what kind of test each was intended to accomplish.

Can we afford this candidate?
Obviously if the interview isn’t going well then you don’t need to ask this. But if it is, then we need to find out if the candidate is affordable. Make sure that someone in the loop (and only one person needs to ask this) asks the candidate, “What would you need to make in order to take this position”?
Legal Ramifications:
So what should you never ask in an interview? There are certain types of questions that you should never ask in an interview that may seem like perfectly normal questions that you might ask a co-worker or friend. Legally we should avoid any question that would identify the candidate as being part of a protected class. Here is a list of protected classes as they pertain to employment law (according to the state of Washington http://www.hum.wa.gov/documents/empflier.pdf).
• Race
• Creed
• Color
• National origin
• Sex
• Sexual orientation, including gender identity
• Age (40 and over)
• HIV/AIDS or Hepatitis C status
• The presence of any sensory or physical disability
• The use of a service animal for a disability (like a seeing eye dog)
• Pregnancy or maternity
• Retaliation for opposing an unfair practice
• Retaliation for filing a whistleblower complaint with the state auditor
• Retaliation for filing a nursing home abuse complaint

EMPLOYMENT AGENCIES MAY NOT DISCRIMINATE SOLELY ON THE BASIS OF A PROTECTED CLASS.
FOR EXAMPLE, AN EMPLOYMENT AGENCY MAY NOT:
• Discriminate in classification or referrals for employment;
• Print or circulate any discriminatory statement, advertisement, or publication; or
• Use discriminatory employment application forms, or inquiries made in connection with prospective
employment.


There are several types of questions that an employer is legally prohibited from asking in a job interview. For example, an employer may not seek medical information regarding an applicant, at least not before the applicant has received a conditional job offer. Questions that seek inappropriate medical information include: Are you disabled? How many sick days did you take last year? Have you ever made a workers' compensation claim? and Will you require any form of physical accommodation for this job? An employer may, however, describe the duties of a job to an applicant and ask if the applicant can perform those duties, either with or without reasonable accommodation. In addition, if the applicant clearly has a physical disability that would seem to prevent the applicant from performing the relevant job duties, the employer may ask how the employee proposes to perform them.
In addition to medical inquiries, an employer may not ask an applicant about his or her race, national origin, or religion, or about his or her family status or plans, such as whether a female applicant has or plans to have children.
Often, state anti-discrimination laws also prohibit an employer from inquiring about whether an applicant is in a protected class, such as whether he or she is over age forty or a minority group member.
An employer typically may ask an applicant if he or she has ever been convicted of a crime. Asking whether an applicant has been arrested, however, may violate anti-discrimination laws, because the Equal Employment Opportunity Commission has stated that minority group members tend to be disproportionately targeted for arrest, and whether someone has been arrested is not an indication that he or she has actually committed a crime. As a result, an employer who asks applicants whether they have been arrested, and then excludes those who have, may be engaged in discriminatory hiring practices against minority applicants.
Finally, an employer is also prohibited from asking an applicant whether he or she has participated in a strike in the past or performed union organization activities.
“ taken from: http://www.kempnerlaw.com/FAQ.shtml?ss=fln-faq-question.xsl



The Process of conducting an interview loop

Who should be involved?
Make sure that the hiring manager or lead who has the position to fill is on the loop. They know better than anyone else what they need this person to potentially do. They should also be the one scheduling the interview. Aside from them you should have at between 1 and 3 additional interviewers whose disciplines are inline with the position or who have tangential disciplines (people with whom the candidate may end up working closely with as a customer or a provider of information). If interviewing a Tester then perhaps you should have the test manager or lead and another highly technical tester as well as potentially a developer, PM, or BA.

How do you schedule an interview?
First have in mind a group of potential interviewers that is larger than you need because some of them may be busy. Find a few different times during the week when some of those people can be available. When calling the candidate be professional and make sure they have time to talk before going farther.
“Hi, this is calling from about a position, is now a good time to talk?” If not ask them when you should call back. If they say yes, let the candidate know how you heard of them and ask if they would be interested in interviewing. If they say yes, offer them a choice of 2 or 3 possible interview times based on the times when your group of interviewers is most likely to be available. Make sure to let the candidate know how long they can expect the interviews to take.

Once you have an agreed upon time, use Outlook to schedule the interview and make sure to invite the conference room you need, as well as the other interviewers. In your invite lay out the schedule for the interviewers so that they know who goes first and who follows who. It looks unprofessional to the candidate if you have to chase people around wondering if there are additional interviewers or not.

The morning of the interview day:
Send an email to everyone on the loop reminding them of the schedule and include the interview feedback template.
“Today we are interviewing , for a position in the conference room.
2:00 – Ken
2:30 – Joe
3:00 – Paul
3:30 – Debra
Please use the following feedback template and let the other interviewers know how the candidate did.

The Hand off and interview feedback:
After you are done interviewing the candidate and if there are additional interviewers, ask the candidate if they would like something to drink or if they need to use the restroom. If so show them and let them know that you will meet them back in the conference room in a few minutes. If not then you can let them wait in the conference room.

Make sure that you cannot be heard by the candidate when handing off to the next interviewer. Let them know what areas you covered and what areas you didn’t cover enough. Let the next interviewer know if there are areas you would like them to focus on. Make sure to comment about the candidates observed strengths and weaknesses. After updating the next interviewer walk them back to the conference room and introduce them to the candidate. (Ask the next interviewer ahead of time if they want their title known by the candidate).

When you head back to your desk make sure to send out an email to everyone who is on the interview loop with your feedback about the candidate so that everyone knows what the next interviewer now knows.

Interview feedback template:
Here is an email template that I like to use.

Interview Feedback for:
Position:
Recommendation:

Strengths:

Weaknesses:

Smarts: How smart was the candidate? When you hinted at things in your questions did they pick up on them? Did they ask you the right questions when there was missing information in your question? When you explain a technical problem do they “get it”?

Fit: How were the candidate’s interpersonal skills? How well did they communicate their ideas? How do they handle conflict? Do they appear to have integrity? Do they have a high level of professionalism? How well could they handle multiple concurrent projects or irregular hours? Will they do “what it takes” to get the job done?

Customer focus: Can they empathize, can they see things from different points of view? Does this person naturally make you feel at ease or do you feel uncomfortable talking to them? Is their style of communication open and inviting? Could you see this person representing us to our customers?

Drive: Is the candidate goal oriented? Are their accomplishments noteworthy? Are they passionate about technology or business? Will they do what it takes to get the job done? How do they measure their professional success?

Technical: - (this should vary based on the position): example SDET question:
Can they write a function to solve a problem in pseudo code? When asked to test their own function, are they able to find flaws in their design? Are their tests exhaustive?

Overall: (Use only one of the following questions and delete the rest.)
Test specific: How well can the candidate test? Do they have a “break-it” mentality? Could they come up with an exhaustive list of test cases given only a function header and a comment about what the function is supposed to do? Would you feel comfortable handing them your project and asking them to test it?
OR
Dev specific: How well can the candidate code? Do they plan ahead for scalability and performance? How well do they understand the principles of object oriented design? Do they prefer to sit down and start coding or do more upfront analysis? How do they approach refactoring code? What is their experience with test-driven development? Do they naturally comment their code so that future enhancements are easier for another party? Would you let this person code a feature of your project with little guidance?
OR
PM specific: How well can the candidate manage a schedule? How well can they handle a project that is already in jeopardy (issues, risks, roadblocks)? What do they do to mitigate risk? Can they clearly define the critera by which a projects success is measured? Could they explain something complex and technical in simple and understandable terms? Would you let this person run one of your projects?
OR
BA specific: Did the candidate ask the right qualifying questions? Were they analytical? Could they find the root problem when given a vague or misleading problem statement? Would you let this person gather requirements for one of your projects?
OR
BI Reporting specific: Do they have experience doing enterprise scale reporting or just smaller companies? What scope are they comfortable with? Do they test their own SQL, how good is their SQL? Can they communicate in the user’s language instead of in tables and joins? Do they understand their audience? Are their reports clean, and pretty do they have a good feel for aesthetics? Are they tied to a particular tool set or are they tool agnostic? Would you feel comfortable letting this person design a BO Universe that you were going to use for reporting? Would you let this person write a report for the CEO of one of our customers as well as a low level manager?
OR
DBA specific: Could the candidate write a SPROC or a Trigger? Can they design a normalized data structure from an unorganized set of parameters and descriptions about the problem statement? Would you feel comfortable handing them one of your products and letting them manage schema changes and feature requests?

Concluding the interview:
If you are the last person on the interview loop, make sure you leave some time after your questions, and ask the candidate if they have any questions for you. This is the time when you can sell the benefits of working for your company to the candidate. If you feel that this candidate has a shot at being hired then make sure you leave them with a good impression about the company. In order for us to hire great talent, we have to like them, and they have to like us, and their compensation requirements have to be in line with our budget.

Finally:
Thank the candidate for their time and let them know that we will review the information we’ve gathered today and we will call them when we’ve made our decision. Make sure not to promise the position to the candidate at this time.

Pearls of wisdom:
Over the years I’ve heard various pearls of wisdom that I have now adopted (as I’ve either proved them to be true or at lease dis-proved their converse).
1. If you’re on the fence, it’s a “no”. If the candidate is a yes you should leave the interview thinking “we’ve gotta hire this person.”
2. Don’t hire just to fill a gap, hire for the long term benefit to the company. Once the current crisis is surmounted, a good hire will still have value to add.

Tuesday, November 16, 2010

Successful Automation Campaign

Things you must do to be successful in a long term software test automation campaign.
1. Don’t give up manual testing.
2. Get team and management “buy-in”
3. Test before you build
4. Identify low-hanging fruit
5. Make re-usable parts
6. Generate your tests, don’t write them. – Automate your automation execution processes.

Don’t give up manual testing:
Automation is great at saving time, but it is terrible at finding bugs. In fact, in order to get your automation working the first time (and get it working enough to trust it) the application usually has to be free of bugs in the area that the automated test is focused. So for new features and new functionality, you almost always need to test manually before you can create and trust automation to test your app (the exception to this is unit tests).

Automation is also not intelligent. A human can be executing a test to validate a user’s ability to create an account, and while testing, can notice a bug that has nothing to do with the test that they started, like maybe dark blue text on a black background which is hard for humans to read. Automating the same test (to verify the ability to create an account) will not result in a usability bug like this being found, unless the creator of the automated script thought to put in a validation for color contrast in the test. But the human doesn’t need to be told these things, human testers just “notice” them as “odd”, and humans can digress to chase down an interesting bug and then come back to their original test.

The moral of this section, don’t think that because you automated your BVT’s that you will catch the same number of bugs you used to catch when you did these manually. There are always undocumented tests that people don’t realize that they are running in their heads and these are hard to capture in automation, until someone catches a bug and then explicitly creates a script to search for the bad condition. Automation will buy you time so that a human can still do the higher level thinking and apply intelligent scrutiny to the application under test, without wasting time to do the mind numbing repetitive tests.

Get team and management buy-in:
To be successful in any automation campaign you need to take the initiative and start automating, but you will not be successful long term if you don’t have buy in from your team and your management.

You don’t need to be a sales person to do this, but it is selling of an idea. And selling is easier with tangible results and an ROI.

Keep a log of how long it takes to do what you do manually and repetitively for a week or month or whatever your test cycle is. Then do some preliminary napkin-math projections in a spreadsheet to see how much time (per month, or per year) you will be spending on doing these activities if you are to continue doing them manually. Build in to your model the expected growth of your test case library and expansion of your regression suite as new features become “old features” and newer features are added.

Once you have that model, follow the rest of the guidelines below to start building and using your automation for your most repetitive tasks. Keep a log of the time it takes to execute your automation, plus the time it takes to maintain your automation through several (feature changing) builds. Use the execution time plus maintenance time per testing cycle and add these into your spreadsheet to make projections side-by-side versus manual. The longer your time projection the more dramatic the savings will be.

Also keep a log of how much time it took to get the initial versions of the tests running for the first time and validated so that you can trust your results. This is the “I” investment part of the “ROI” that you will show in your spreadsheet.

Now depending on your organization you may want to put dollars next to the time savings to show the efficiency you will have created. If you can show efficiency in one area then you can sell the idea of applying the automation model to other areas.

Test before you build …Test Driven Development:
When a team has taken on an automated testing campaign, the tester’s input in the design phase is crucial to the success and timeliness of the development cycle.

Often in a development organization, testing is an afterthought. The test team is something added to the organization after prototyping the first beta application, when there’s not enough time as a developer to complete unit testing and still complete all features on time. But to deliver high quality software products a test team is not only necessary, but their involvement must be sought during the design phase of a product.

Imagine a flight from Seattle to New York departs and is slightly off course at takeoff. If the pilot examines the position early, a slight correction is needed and the error has negligible fuel impact. Early in the flight the distance between the current path and the correct path is small. If the pilot waits 3 hours into the flight to check position and heading, instead of being just a few miles off course now the flight is hundreds of miles off course. The distance between the correct path and the current path has grown over time and it will cost more fuel to traverse the distance back to the proper course. A correction later in the game is more costly.

In any discipline, once a basic foundation of design is established and features are built upon that foundation, changes to the foundation will ripple throughout the product. If the foundation is tested early on for the possibilities it may need to support, then a correction in design is less costly. An error created during the requirements phase can cost 50 to 200 times more to correct later in a project. ,

Developers, Requirements engineers, Business Analysts, Program and Project Managers, should seek the advice of testers during the earliest phases possible of any software development project. Here the tester’s role is to test the ideas presented to see if they will stand up to the unspoken assumptions of the users, and the team building the product.

Testers should be involved with the developers to help define test code to validate the components before they are combined. The tester should work side by side with the developer to write unit tests, and once the unit tests are functional and verified, they should be run before any build of the product is deployed to a test environment.

Testing early saves time.


Identify low-hanging fruit:
Identify in your application the low hanging fruit. These are the tests that are repeated most often. Of those that are repeated most often start with the ones with the least complexity of underlying information (don’t need to read from an excel spreadsheet or have data that becomes stale easily) but the most tedious steps (from a human point of view).

Automation is faster than a human when tasks are repetitive. If you are performing regression testing, then you are taking the same actions you took a day, a week, a month ago (or some measure of your cycle) to validate that existing features, which were not supposed to change; actually did not change. Automation of those actions once may mean that they can be reused for many future "regression testing" cycles. If you have a suite of tests that you run to validate that a build was successful (BVT tests), and this must be run after every build before in-depth functional testing can begin. Automation can increase the speed of execution of these tests, and free up the time that a tester would have spent conducting the same tests manually. The same can be said for “Acceptance tests”, “Regression tests” or “Performance tests”; and in some cases functional tests when the AUT is designed with the proper “automation hooks” in place.

Make re-usable parts:
Once you’ve chosen a starting point and a tool, automate several tests from start to finish and then look for common “action groups” which can be componentized. An example of this common to many web applications is “log in”. If you are testing an application where the user needs to be “logged in” for a variety of the tests, then creating a re-usable module for “log in” is smart. If your application changes – for example if the “login” button changes to a “sign-in” button – it’s much easier to modify one “login” function rather than doing a find and replace in every test that logs in to your application. Also if you know that you will need to log in as sever different user types then perhaps your login function should take a variable like “usertype” or “user name” and “password” as an override. Look for other common things to group – navigation to a certain section, or placing the application in a certain known state are also places where re-usable parts come in handy.

If you are working on a team with others who are automating various features of the same application, then communicate with them. Share your components, and use a source control system. Your whole team can benefit by standing on each other’s shoulders and not re-doing work.

Start small with the most atomic user action groups as functions, then make higher level functions that are groups of the low level functions… such as “login_and_goto_MyAccount(usertype)”. Your tests will become easier to read, and faster to write.

Generate your tests:
Once you have a substantial library of tests and re-usable parts for the “happy path(s)” of your application under test, you may want to start testing the other permutations of those tests. But maintaining several “very similar” versions of the same test can also produce a maintenance headache, especially if your library of tests is growing large. Use a system to “variablize” the common tests into a simple base test that can run with different configurations to accomplish the various validations you seek.

For example, let’s say you have a website that you are testing, and the site is available in several different languages for different countries. In each of the countries some of the features are the same and some might be different due to laws and regulations. You want to verify that what is supposed to be there in each language and country is actually there and you want to verify that what is not supposed to be there isn’t there either. In this situation it is best to have a simple base test that covers the most common path(s), language and country, and then variablize each validation point within the test to allow you to run the test with different “configurations” and still be able to validate what you expect (when what you expect changes with the configuration).

Finally use a tool (or write code) to generate the test instances you need at the time of execution from the base tests and configuration files (or configuration data if you build a database – recommended). Have your tool able to create the language file that your test tool eats and create some method of bootstrapping the automation tool so that you can look for the newly generated test and start your tool running that test… and listen for it’s results to be complete.

We’ve been successful in multiple projects using this approach and have built our own system to generate advanced permutations of our tests from simple base tests and information about the expectations in varying configurations of the application under test. We call our tool TestCentral.