My writing time is often split between fiction (a very dark historical fiction of immigrants from Poland in 1915) and business advice. Each has different rules for capturing and maintaining the audience.
But there is some overlap. In fiction writing you are told to Kill your Darlings. Just because you like the way a sentence reads or the turn of phrase doesn't mean it belongs in the piece. You have to Kill your Darlings if they don't move the action along or inform the reader of important events.
The same thing is absolutely true in job search communications. While some people are tempted or worse, committed to dumping all the information about their background or skill set, it is rarely, almost never, the right thing to do.
If the information you convey is not spot on to the question you were asked or does not 'prove your point' when you describe your experience, it doesn't belong in the discussion.
More than one interview has been fouled by too much back story. I recently asked a client why he left his last job and he told me about the reporting structure, client base, hiring process and ineptitude of his boss. He finally got to the point; he left because he wanted to work in client facing applications, not back end. By the time he got there, I was done listening and more than a bit impatient. Imagine how it would have played had an employer asked.
Feel you need to fill in details about your technical skills and experience? Wait until you are asked to elaborate. Until that time answer questions with the 20,000 foot view of what you did AND the outcome. That's often all you need to capture the heart of the interviewer. Most are more concerned with WHAT you accomplished rather than HOW you accomplished.
So, Kill your Darlings unless someone asks to meet them.
Want more sage advice on networking? Go to www.jobsearchdebugged.com for a sneak peek at "Networking Debugged."
Comments