Skip to content

shannonlowder.com

Menu
  • About
  • Biml Interrogator Demo
  • Latest Posts
Menu

Custom Resume, or Generic?

Posted on December 21, 2010February 9, 2011 by slowder

In my last career article, I talked about balancing the truth and salesmanship.  I wanted to try to explain how you can be honest, and at the same time make the case that you should be the one a hiring manager chooses to hire.  Today, I’d like to go back a bit further in the hiring process.

The Resume.

I’ve had great success in tailoring my resume for a specific job posting.  I believe the reason it works well for me is I’ve had a broad range of experiences, and many job postings are looking for a person with a specific skill set.  If I included all my skills, they may get the impression I am unfocused.  Or worse, they may consider my resume to be fake.

When I see a job posting I’m interested in, I pull it up in one window, and my resume in the other.  I look at the job posting, I look that the job description, and figure out what type of person they’re looking for.

Are they looking for a database administrator?

Are they looking for a database developer?

What are they looking for?  Once you’ve figured that out, you can look at your resume and see if there’s and skills you have listed on your resume that don’t apply in any way.  I’ve helped many people tailor a resume for a job and I’ve seen some interesting information to include on a resume.

On one resume for a database administrator role, someone included the types of laptops they had worked on.  You have to ask yourself, would the hiring manager need to know that in order to hire you?  If you can’t argue that they might want to know… remove it.

Next, I’ll look at the specific technologies they’re asking me to have.  They’ll usually mention specific versions of SQL Server, or specific technologies like SSIS, SSRS.  I Look through my  resume and see where I used those technologies.  Every where I can mention the specific version they’re looking for I make sure I mention it by name.

For example, if in my generic resume I have:

  • Developed a solution to move data from one database system to another.

And in the job posting mentions they want someone who has experience with SQL 2000 and 2005, I want to use those terms as much as possible.  In my previous example, I was migrating data from a SQL 2005 to a sql 2008 server.  As a result, I’ve gotten a better response by rewriting my resume to say:

  • Developed a SSIS solution to move data from SQL 2005 to SQL 2008.

By including the specifics in my bullet points, I don’t have to include a technology block at the top of my resume. You know the one I’m talking about, a table of all the technologies you’ve ever touched.  By including the technologies in-line, the hiring manager can see where you’ve used the technology, and they can see how you have the specific technologies that they’re looking for.

Now I’d like to make something completely clear.  I do not advocate including technologies you haven’t used and aren’t familiar with.  But if they are asking for a version you haven’t yet used, let’s say they want 2008R2, and you only have 2008.  Mention the fact you’ve mastered (or nearly mastered) 2008, and in the cover letter discuss the similarities between the version you know, and the version they want you to know.  This is the point where it goes back to salesmanship.

Tailoring your resume for the job can put you over the top.  It can help you by making it quicker for the hiring manager to read your resume.  It can give the hiring manager more useful information about you.  A well customized resume can mean the difference between getting an interview offer, and simply having your resume discarded.  Don’t let your resume stand in your way.  Make it work for you!

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Recent Posts

  • A New File Interrogator
  • Using Generative AI in Data Engineering
  • Getting started with Microsoft Fabric
  • Docker-based Spark
  • Network Infrastructure Updates

Recent Comments

  1. slowder on Data Engineering for Databricks
  2. Alex Ott on Data Engineering for Databricks

Archives

  • July 2023
  • June 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • November 2022
  • October 2022
  • October 2018
  • August 2018
  • May 2018
  • February 2018
  • January 2018
  • November 2017
  • October 2017
  • September 2017
  • August 2017
  • June 2017
  • March 2017
  • February 2014
  • January 2014
  • December 2013
  • November 2013
  • October 2013
  • August 2013
  • July 2013
  • June 2013
  • February 2013
  • January 2013
  • August 2012
  • June 2012
  • May 2012
  • April 2012
  • March 2012
  • February 2012
  • January 2012
  • December 2011
  • November 2011
  • October 2011
  • September 2011
  • August 2011
  • July 2011
  • June 2011
  • May 2011
  • April 2011
  • March 2011
  • February 2011
  • January 2011
  • December 2010
  • November 2010
  • October 2010
  • September 2010
  • August 2010
  • July 2010
  • June 2010
  • May 2010
  • April 2010
  • March 2010
  • January 2010
  • December 2009
  • November 2009
  • October 2009
  • September 2009
  • August 2009
  • July 2009
  • June 2009
  • May 2009
  • April 2009
  • March 2009
  • February 2009
  • January 2009
  • December 2008
  • November 2008
  • October 2008
  • September 2008
  • August 2008
  • July 2008
  • June 2008
  • May 2008
  • April 2008
  • March 2008
  • February 2008
  • January 2008
  • November 2007
  • October 2007
  • September 2007
  • August 2007
  • July 2007
  • June 2007
  • May 2007
  • April 2007
  • March 2007
  • February 2007
  • January 2007
  • December 2006
  • November 2006
  • October 2006
  • September 2006
  • August 2006
  • July 2006
  • June 2006
  • May 2006
  • April 2006
  • March 2006
  • February 2006
  • January 2006
  • December 2005
  • November 2005
  • October 2005
  • September 2005
  • August 2005
  • July 2005
  • June 2005
  • May 2005
  • April 2005
  • March 2005
  • February 2005
  • January 2005
  • November 2004
  • September 2004
  • August 2004
  • July 2004
  • April 2004
  • March 2004
  • June 2002

Categories

  • Career Development
  • Data Engineering
  • Data Science
  • Infrastructure
  • Microsoft SQL
  • Modern Data Estate
  • Personal
  • Random Technology
  • uncategorized
© 2025 shannonlowder.com | Powered by Minimalist Blog WordPress Theme