Business Analyst Handbook

To Win that Tech Job, Know the Contest

It's the first morning of your new job.  You have shaken some hands and filled out some forms.  You find a place for the supplies you brought; the half-box of paper clips, the scissors and the yellow tablets all go in the top drawer of the desk you now use.

You won use of that desk in a contest.  Any time two or more people want the same thing, there has to be a contest.  Think of the other competitors now, checking their email for new opportunities, maybe choosing the right wardrobe for yet another interview.  No one wins them all, but why were you chosen in this particular contest?  If you are not certain of the answer, your job search probably took longer than those who know why and how to win competitive interviews.

You may have heard that job hunting is a matter of right-fit.  That right-fit is determined by just a few people, based on the limited evidence of your resume plus a few interviews.

To make yourself right-fit for your next opportunity, first understand the nature of the contest.  To get insight on the contest, do a little analysis of the published requirements.  You can use these 20 right-fit qualities.  Match these against any written job requirements you may have received via email from a recruiter, or you found on an online job board. 

Consider each of the qualities.  Circle the number of any which are prominent - clear and/or near the top of the list - of job requirements.  Put a check mark beside any qualities that seem most essential to the described job.

1. The requirements describe specific tools (brand names of software, databases, report writers) and possibly even version numbers.
2. The ability to work under pressure and to meet strict deadlines is emphasized.
3. You must be able to work as a team member.
4. Presentation skills, interaction with upper management, or leading JAD sessions are essential to the job.
5. A flexible schedule and frequent overtime are likely to be required.
6. You must have exceptional verbal and written communication skills.
7. You will represent the company in client meetings, and must present a good image.
8. The requirements specify more than five years of proven technical skills.
9. You must have demonstrated ability to take risks and produce positive results.
10. The successful candidate must be willing to travel and/or to work evenings, nights and weekend hours.
11. Proven experience with stated methodologies, strategies and/or processes will be essential.
12. You must often work independently to accomplish a goal.
13. Show ability to adapt to changes in business processes and goals.
14. Critical skills include team leadership and/or achieving consensus on any issues which arise.
15. Given limited resources, you must be able to quickly arrive at a technical solution.
16. You must be able to influence others who have varying opinions.
17. Professional appearance and/or outgoing personality are essential.
18. You must have proven results in delivering multiple and varied work products.
19. You will be accountable for achieving business goals.
20. This is an entry-level opportunity to develop substantial technical skills.

Now look back at the circles and check marks.  Choose the top three or four items.  These reveal the nature of the contest.  Match the numbers to those in the list below.

When you know the type of contest, you can more effectively prepare.  Prepare well to increase your chances of winning!

ITEMS	TYPE OF CONTEST	HOW TO PREPARE AND WIN
1 and 11	Game Show	Mention your matching technical skills early and repeatedly on your resume.  Work them into a brief "elevator speech".  Bring a portfolio that proves your skills and knowledge.  Be prepared for technical questions in the interview.
2 and 12	Race	Your resume should highlight any projects you completed within strict time and dollar budgets.  Prepare yourself to describe a few in brief and always positive stories.  At the interview, show energy and determination.
3 and 13	Scavenger Hunt	Include team projects on your resume.  Be ready to describe your individual contribution to collaborative school and work projects.  At face-to-face interviews, listen and specifically respond to the interviewer's questions.  Keep the discussion focused, but friendly.
4 and 14	Run for Office	Let your resume show your interest in leadership.  Feature projects in which you held a critical role in achieving success.  Include one or two of these in your "elevator speech".  Be ready with the firm but not crushing handshake, smiles and eye contact through the critical first minutes of any interview.  Offer a handshake and friendly farewell at the end as well.  Ask for the job.
5 and 15	Battle	Your resume must prominently show work delivered on time and within specifications.  Describe the positive results as well - especially any expenses saved and revenue earned.  Give the compelling reasons for each time you were promoted.  Bring ample copies of a concise, well-organized portfolio to the interview.  Take the initiative in leading your interviewers through it.
6 and 16	Debate	In your resume, document any occasions where you identified a solution, and then participated with others in its delivery.  Be prepared for standard interview questions ("Why should I hire you?"; "How would your friends describe you?") and for technical questions as well.  In the interview, keep answers brief and maintain a friendly, confident appearance.
7 and 17	Pageant	Without overlooking content, check your resume for aesthetics like clean fonts and balanced white space.  Visit the company website and have good knowledge of their business.  Dress for success at the interview, consistent with the way managers would present to a new client.  Be ready with relevant questions so the conversation never falls to awkward silence.
8 and 18	Weightlifting	Your resume should reveal growth, both technically and in responsibility.  Prominently list matching experience with required tools and techniques.  Include specific version numbers and state your level of expertise.  Be prepared to explain any gaps or direction changes.  Also be prepared for technical questions.
9 and 19	Texas Hold 'Em	Each time your resume mentions a project, it should also list quantitative results.  In your "elevator speech", include an example of how your controlled risk produced a win for your previous employer.  Prepare for the interview by learning as much as possible about the organization and its current projects.  Be confident, concise and friendly.
10 and 20	Auction	Emphasize the value you place on achieving goals.  Your resume should highlight each new experience that added to your skill set.  In the interview, answer questions promptly and ask for feedback.  Show sincere interest in the company and its goals.

You can prepare for any or all 10 contests, but pay most attention to the details of those which match the job requirements.

Be the right fit. Win the job!

Business Analysis and getting dressed: a worn-out metaphor

BA’s!  As you prep for that next interview, dress carefully.  Just as a book can be read by its cover, employers can judge Business Analysts by their clothing. You disagree?  Consider any of these button-down solid similes:

1. Product is more important than process.   No one cares which arm first goes into which sleeve; just don’t mix them up (that could be uncomfortable).  Likewise, your methodology will attract less management interest than the thorough, accurate functional requirements that you list.
   
2. Some things are more essential than others.  Wear shoes to your interview, but that lapel pin? – maybe/maybe not.  And when you get the job, your planning and scripting of User Acceptance Tests will bear more weight than that Smoke Test, which maybe doesn’t need a 50-page document.
   
3. What you do depends on where you are going.  Headed to the beach?  Yeah, business casual would be overkill.  Deploying a new reservation system for a billion-dollar hotel chain?  You may need to churn out level 1 and level 2 support docs first.
   
4. Ultimately, someone notices if you aren’t careful.  Dang!, that shirt or blouse is buttoned wrong.  Shoot!, didn’t think that a Service-Level Agreement would be necessary with the good folks hosting our databases.
   
5. You get to make a lot of choices.  Solid or pin-stripe; charcoal or navy:  all are good.  Page numbers left, right or center?  Don’t stress on the decision.
6. One choice impacts the next.  Oh-oh; now you’ve done it.  You’ve captured attention with those plaids and stripes.  Well, try redirecting their gaze over to that test plan, where every approved new function has become a tested new function.
   
7. It takes resources.  You won’t get the job if all of your professional attire is in the wash.  Users won’t like the solution you designed unless you write-up data and business rule requirements along with those functional requirements.  Depending on scope and complexity, you may need to consult a Data Architect or DBA… maybe both.
8. Check the weather before you begin.  Don’t let Interview Day become a Bad Hair Day, for want of an umbrella.  If the Coders all use UML and Object-Oriented Programming, you may have to churn out a Use Case or two, along with that wireframe mock-up.
9. A second set of eyes is good.  I hate it when asked, “Did your mother dress you funny today?” or when a helpful hand fusses with my shirt collar just as the meeting begins.  It is no less awkward to explain why so many requirements were missed in this release.
   
10. Don’t dawdle or you’ll be late.  If you believe “there is always room for improvement”, also remember that “time marches on”.  Get to the interview on time, and deliver that product on schedule.