May 22, 2013 By John Hargaden Comments are Off
There you are, late one evening, rushing to update your CV so you can respond to a hot job opportunity. But the moment your fingers touch the keyboard, your brain serves up the question that bedevils every job seeker.
Should your CV be one page or two?
If you ask three people, you get four different answers. And when you query Google, it only gets worse. But you still need to send out that CV tonight, so the last thing you have time for is a philosophical debate. So if you are a typical professional working in an urban job market, use this rule of thumb:
– If you are under 30, you should probably keep it to one page.
– If you have had more than three substantive jobs (typically around eight or 10 years of post-grad experience), you can choose to go to two pages, but you don’t have to.
– You should avoid going to three pages, no matter how much experience you have.
Why this rule?
Most recruiters and hiring managers skim CVs looking for relevant experience, quickly sorting irrelevant people into a “No” pile. You only have 5 or 10 seconds to make your first impression, so be sure your relevant experience is prominent on the first page of your CV (ideally on the top half of the page). Once you’ve been selected for more consideration, the rest of your CV and your cover letter will be reviewed with more scrutiny. So page two of your CV will eventually be read — but only after you get sorted into the “Yes” pile.
Here are a few more things to keep in mind:
– Accomplishment bullets are easier to skim than paragraphs, so use them. And be sure your most relevant accomplishments are listed first.
– Use a chronological format, not a functional format. The vast majority of people involved in the hiring process detest functional CVs. Most job seekers use functional CVs to explain employment gaps or career changes, but both issues are better explained in person.
– Don’t use a tiny font to jam more stuff onto page one. Instead edit ruthlessly to eliminate irrelevant detail. Use a normal font. Leave lots of white space. Humans have to be able to read your CV, and if those humans are over 40 years old, small fonts are the kiss of death.
– If you have more than 20 years of experience, your descriptions of jobs should get progressively shorter as time goes by. Nobody cares what you did before 1995. Just give each job a line or two. And you should probably leave off the 1970s entirely. Everyone considers your recent experience to be far more relevant than the distant past. You don’t need three pages.
This article was adapted from the “How Many Pages Should Your Resume Be?” article which appeared in the Washington Business Journal, Jan 14th 2013.
http://www.bizjournals.com/washington/blog/2013/01/guest-blog-how-many-pages-should-your.html
Comments are closed.
Cookie | Duration | Description |
---|---|---|
wpfront-notification-bar-landingpage | session | This cookie is set by WPFront Notification Bar WordPress plugin. The cookie is used to determine whether the visitors have decded o show or hide any current notification bars on the website. |
Cookie | Duration | Description |
---|---|---|
__utma | 2 years | This cookie is set by Google Analytics and is used to distinguish users and sessions. The cookie is created when the JavaScript library executes and there are no existing __utma cookies. The cookie is updated every time data is sent to Google Analytics. |
__utmb | 30 minutes | The cookie is set by Google Analytics. The cookie is used to determine new sessions/visits. The cookie is created when the JavaScript library executes and there are no existing __utma cookies. The cookie is updated every time data is sent to Google Analytics. |
__utmc | session | The cookie is set by Google Analytics and is deleted when the user closes the browser. The cookie is not used by ga.js. The cookie is used to enable interoperability with urchin.js which is an older version of Google analytics and used in conjunction with the __utmb cookie to determine new sessions/visits. |
__utmt | 10 minutes | The cookie is set by Google Analytics and is used to throttle request rate. |
__utmv | 2 years | This cookie is set by Google Analytics. The cookie is used to store visitor-level custom variable data and is updated every time data is sent to Google Analytics. |
__utmz | 6 months | This cookie is set by Google analytics and is used to store the traffic source or campaign through which the visitor reached your site. |
Cookie | Duration | Description |
---|---|---|
CONSENT | 16 years 4 months 5 days 14 hours 3 minutes | These cookies are set via embedded youtube-videos. They register anonymous statistical data on for example how many times the video is displayed and what settings are used for playback.No sensitive data is collected unless you log in to your google account, in that case your choices are linked with your account, for example if you click “like” on a video. |
Cookie | Duration | Description |
---|---|---|
IDE | 1 year 24 days | Used by Google DoubleClick and stores information about how the user uses the website and any other advertisement before visiting the website. This is used to present users with ads that are relevant to them according to the user profile. |
test_cookie | 15 minutes | This cookie is set by doubleclick.net. The purpose of the cookie is to determine if the user's browser supports cookies. |
VISITOR_INFO1_LIVE | 5 months 27 days | This cookie is set by Youtube. Used to track the information of the embedded YouTube videos on a website. |
YSC | session | This cookies is set by Youtube and is used to track the views of embedded videos. |
yt-remote-connected-devices | never | These cookies are set via embedded youtube-videos. |
yt-remote-device-id | never | These cookies are set via embedded youtube-videos. |
yt.innertube::nextId | never | These cookies are set via embedded youtube-videos. |
yt.innertube::requests | never | These cookies are set via embedded youtube-videos. |
Cookie | Duration | Description | |
---|---|---|---|
2ebb1802fb | session |
| |
383aeadb58 | session | Used by Zoho forms on form submission | |
663a60c55d | session | Identifies the visitor across devices and visits, in order to optimize the chat-box function on the website | |
6e4b8efee4 | session | No description available. | |
cmsetraining-_zldp | 2 years | This cookie identifies the unique visitors for the website | |
cmsetraining-_zldt | 1 day | This cookie identifies unique visits for a visitor in the website | |
cookielawinfo-checkbox-functional | 1 year | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". | |
crmcsr | session |
| |
e188bc05fe | session | No description available. | |
gclid | 1 month | Google Click ID (GCLID) is a parameter passed in the URL with ad clicks, to identify the campaign and other attributes of the click associated with the ad for ad tracking and campaign attribution | |
iamcsr | session | Ensures visitor browsing-security by preventing cross-site request forgery. | |
store_notice[notice id] | session | Allows customers to dismiss the Store Notice. | |
tk_ai | session | Stores a randomly-generated anonymous ID. This is only used within the dashboard ( /wp-admin ) area and is used for usage tracking, if enabled. | |
woocommerce_cart_hash | session | Helps WooCommerce determine when cart contents/data changes. | |
woocommerce_dismissed_suggestions__[context] | 1 month | Count of suggestion dismissals, if enabled. | |
woocommerce_items_in_cart | session | Helps WooCommerce determine when cart contents/data changes. | |
woocommerce_recently_viewed | session | Powers the Recent Viewed Products widget. | |
woocommerce_snooze_suggestions__[suggestion] | 2 days | Allows dashboard users to dismiss Marketplace suggestions, if enabled. | |
wp_woocommerce_session_ | 2 days | Contains a unique code for each customer so that it knows where to find the cart data in the database for each customer. | |
_zcsr_tmp | session |
|