IT Resume - IT Experience Section

IT Resume - IT Experience Section

The experience section is made up of headings, statements of responsibility and statements of achievement.

The Heading - this should include at minimum:

Name of the Company you worked for
Location of the Company (City, ST) - Sometimes Country or Province
Your Job Title
Dates of Employment

Optionally, you could include multiple titles if applicable and also include a description of your company, which is highly recommended. It is acceptable to use only the year as the date and eliminate months. This is an effective way of hiding gaps in employment. If your work history is consistent then it is recommended to use months. If you have a number of jobs that lasted less than 1 year, it will be difficult to eliminate months without confusing the reader.

Statements of Responsibility - Much like the headline statement in the introduction and summary, you will want to build an opening statement that identifies the overall scope of your responsibilities. The following statements then support the opening statement and provide further details regarding your key duties. Example:

"Develop and implement financial software in support of company's flagship product. Coordinate with accounting staff to define requirements. Design software architecture. Develop software code using C, C++ and Java. Manage projects for implementation of applications. Train staff members on software utilization and provide ongoing software support."

For hands on IT professionals, you can also list key technologies that you worked with in the position, especially if those technologies are critical for obtaining your next job.

Achievements - After developing statements of responsibility, you should now document a few achievements. Your achievements are what set you apart from your competition. They help differentiate your resume from other applicants and they demonstrate that you have been successful in previous positions.

Ideally, statements of achievements should be written in the form of ACTION - RESULT. State the action, then state the positive result. If possible, try to quantify your results. Example:

* Developed application for accounting and reporting system that automated posting to the General Journal, saving $5 million in annual paper expense while increasing overall productivity.
Achievements don't always have to be in the form of action result. Other achievements can document awards, completion of training, promotions, or prominent roles (such as being selected as chair member of emerging technologies). Also, you can build statements to simply highlight key technologies or areas of technology.

Formatting duties and achievements can be done in several ways. The preferred style is to build a paragraph of duties and then bullet point the achievements below. This style really allows you to separate the 2 types of statements and helps to highlight the achievements.

Tips for developing your experience section:

1. Experience should be written in reverse-chronological format (most current job positions first). For the most part, order of items in the experience section reflect order of importance to the reader. The heading is necessary to identify critical job information. Then it is important to state your scope of work. Then highlight achievements. The order of statements within the paragraph of responsibilities should also be determined by importance. Therefore, build the opening statement and follow that statement with the next most important responsibility. Follow the same logic when listing statements of achievement.

2.. Try to start statements with action verbs (design, develop, implement, deploy, create, lead, manage, coordinate). Avoid using the same action verbs within each job, but if that is not possible, at least avoid using the same action verb in consecutive statements. Develop this, develop that, develop this, develop that.... its poor writing, reflects laziness and shows a lack of creativity. Also try to avoid the two dreaded vanilla statements (Duties included..... and Responsible for.....).

3. Make statements detailed, but don't go overboard. Brief and detailed is ideal. Even if you have 1 bullet point, don't be afraid to break it down into multiple sentences.

4. Avoid using first person pronouns (I, me, my). Also avoid using too many articles (a, an, the). The resume is not a novel or publication. Statements are meant to be quick and descriptive. This strategy really helps maintain attention of readers who quickly scan the resume. Imagine the statement above filled with articles and first person pronouns.

"I developed an application for the accounting and the reporting system that automated the posting to the General Journal, saving $5 million in annual paper expense while I increased the overall productivity."

5. Length is a matter of judgment. It really depends on how much experience you have, the level of detail involved in your job, and volume of achievements. But.... it would be highly recommended that you limit yourself to 5-10 statements of responsibility and 2-8 statements of achievement. As you start building descriptions of previous work history, you should start cutting back the level of detail. Each job should be progressively shorter as the you work your way from current to previous positions.

6. Consider dropping experience past 20 years and you should even consider just listing the headings (without descriptions) for "old" experience, especially if it has limited value.

This job is in technology, so it should be listed. But, why waste the space to build up a description of this job? For one, the job duration was only 1 year. For two, the job is not even within the field of Software Engineering. It's only significance is documenting career progression and overall length of IT experience. Most people do not have a career that is this straightforward, so the decision is much more difficult. Just ask yourself this --- "how much of an impact will this job have on my ability to market myself for a new position?" It just makes no sense to build up lengthy descriptions of previous somewhat insignificant jobs while cutting information from very significant current positions.

IT Resume - IT Skills Section

IT Resume - IT Skills Section

The IT Skills section is something that you may not see in non-IT resumes, but is almost absolutely necessary in the technical resume, with exception of executives or high level managers who may choose to leave this section out.

For hands-on IT professionals this is critical. For example lets look at a software engineer. There is a major difference between the type of jobs available for a software developer OOAD engineers, database developers and firmware developers are all very different jobs using different technologies. We need to make that clear to employers that you possess a knowledge of specific technologies.

The goal is to develop a detailed outline of your technical skills and break it down into subcategories. This will make it easier for the reader to pick up the specific skills they are looking for.

A good general breakdown would include 5 categories of skills sets: Operating Systems, Hardware, Software, Networking and Programming Languages. A basic example of an IT Resume Technical Skills Section:

Systems: Windows (2000, 2003), UNIX, Linux

Hardware: Servers, Hubs, Routers, Switches, PC's

Software: MS Office Suite, MS SQL Server, Visio

Networking: TCP/IP, DNS, DHCP, WINS, Ethernet, Token Ring

Languages: Visual Basic, C, C++, HTML, JavaScript

Of course the subheadings that you choose should reflect the key areas of your field. Often times, network engineers will not have a languages section and software engineers won't have a networking section.

Also, its a good idea to break down the IT skills section into more than just 5 subsections. I have seen this done effectively with up to 10 subsections, although I think going above 10 is overdoing it. For example, a specialized software engineer could build an IT skills section using these subcategories: Programming Languages, Operating Environments, Hardware,

API's/Frameworks, Databases, Development Utilities and Applications.

Tips for building the IT Skills Section

1. Be reasonable about the subcategories and don't build so many that you have only 1 or 2 skill sets listed in the subcategory. For one, it tends to make you look weak in that category. For two, it tends to take up too much space and may be forcing you to cut quality information from other portions of the resume.

2. Be reasonable about what you are listing. I have seen resumes with an entire page full of technical skills. This is counterproductive as it makes it extremely difficult for the reader to find what they are looking for. Stick the key technologies and eliminate skills sets that are either insignificant or so old that no one uses the technology anymore. That's not to say that you should eliminate ALL legacy technologies as sometimes they may be beneficial if the company is planning to migrate to a newer technology. Use logic and your better judgment to decide. 25-30% of the page is an ideal length for the IT skills section.

3. There are multiple options for formatting the IT skills section. The style above is popular and takes up less room. You can also list the headings on top and the skills below. Use the style that you prefer

IT Resume-Summary

IT Resume Writing Guide outlines the concept of building a summary.

In this section we will go over the types of statements that can be used in the IT Resume Summary; provide examples of statements that can be used in the IT Resume Summary; and describe how the summary can be used to quickly grab the readers attention and help promote the reader to call you for a job interview.

IT Resume - Summary

The summary will follow the introductory statement. The summary will consist of anywhere from 3 to 10 supporting statements that provide more details about your experience and/or training. These statements should reflect key areas that you feel are strong requirements for the job position. The statements should be compelling, detailed, yet easy to follow.

Let us take a look at some statements that we may want to include in our example:

Over 20 years of experience developing software for large multi-national financial organizations, credit card corporations and banking institutions.

The above statement would further document your experience by identifying your years of experience and industry expertise.

Sun Java 2 Certified professional with deep understanding of object-oriented design and extensive experience building software in C++ and Java.

The above statement would highlight a key certification and highlight your areas of expertise within your field.

Proven ability to lead and motivate high performance teams.

This would be considered a statement of personal strength. In this statement you are informing the reader that you can lead teams and you have had success doing so in the past.

History of building software systems with improved functionality and productivity, consistently meeting critical requirements.

This is a good example of a strong closing statement that documents that you have achieved success in your field in previous positions.

Format - Generally, there a number of ways to format the summary, but in this guide we will talk about 2 formats, general format and executive format. First the general format, which tends to be less formal and easier to read.

A results-driven Developer with demonstrated success in the design, development and deployment of large-scale enterprise applications for the financial industry.

Over 20 years of experience developing software for large multi-national financial organizations, credit card corporations and banking institutions.

Sun Java 2 Certified professional with deep understanding of object-oriented analysis and design with extensive experience building software in C++ and Java.

Proven ability to lead and motivate high performance teams.

History of building software systems with improved functionality and productivity, consistently meeting critical requirements.

Secondly, the executive format, which is commonly used by professionals targeting leadership positions. In this format, the summary statements will follow the headline in a paragraph.

A results-driven Software Developer with demonstrated success in the design, development and deployment of large-scale enterprise applications for the financial industry. Over 20 years of experience developing software for large multi-national financial organizations, credit card corporations and banking institutions. Sun Java 2 Certified professional with deep understanding of object-oriented analysis and design with extensive experience building software in C++ and Java. Proven ability to lead and motivate high performance teams. History of building software systems with improved functionality and productivity, consistently meeting critical requirements.

Technical Resume Writing

Technical Resume Writing

This site is designed to provide free helpful information on resume writing in the Information Technology industry. The site information, articles, guides, resume examples and cover letter samples have been prepared by professional resume writers that specialize in IT resume writing.

The free Technical Resume Writing Guide is designed to help you develop a professional quality technical resume. The guide includes strategies that are specific to the IT job sector, tips for hands-on IT professionals and ideas for structuring the resume. The specialized technical resume is designed to help you market yourself to employers an d generate more job interviews. General IT Resumes are for professionals in:

*Software Engineering, Programming, Software Development
*Network Engineering, Hardware Design, Network Administration
*IT Consulting, Project Management, Project Lead
*Technology Executive Management, Program Management
*Systems Analysis, Systems Design
*Technical Support, PC Tech, Help Desk
*Database Design, Database Adminstration
*Web Development, Graphic Design

In the Technical Resume Samples section you will find posted copies of professionally written technical resume examples and technical cover letter examples. You can use the examples to generate ideas on phrasing statements in the summary or body of the resume; using statements with power verbs; or even just learning the outline. You can also use the technical resume examples as a guideline for structuring your IT resume.

CV Posting Tips

Do

Short sentences are easy to scan, especially given many recruiters have just 10 seconds to read it.

Use standard typefaces such as Arial, 11 or 12 points.

Check and re-check spelling in your resume / CV Text. .

Ensure your personal details are printed by all printers ? not in the header/footer.

Dates and employment should be easily found and consistent in resume.

Lead with achievements, use active verbs and positive language.

Follow up all claims with proven examples, be quantitative as well as qualitative.

Use email addresses where referees are abroad.

Include awards or recognition received for work well done, together with professional memberships and relevant training.

Keep your CV honest and factual.

Ensure every line sells you at your best.

Prioritise relevant content in your resume.

Focus on what you have to offer the employer rather than listing what you have done.

Ask trusted colleagues and friends if this is an accurate representation of you.

Do not

Date your CV.

Put your irrelevant personal details first i.e date of birth and nationality.

Mention Salaries.

It is not necessary to put reason for leaving.

Include negative or irrelevant information.

Lie.

Use Reverse Chronological format if you have many gaps between employment.

Put education first if its 10 years out of date.

List every employer if you have been working.

Allocate the same space to all positions, prioritise the content.

Quote unsubstantiated superlatives.

Modify your CV for every application unless you have a foolproof method of remembering to whom you sent which edition.

Technical Resume or CV

The technical resume is only used in cases where mentioning particular skills or knowledge of a technical nature is particularly important, as is the case for the IT Industry. The technical resume should be very much like the chronological resume, except it must include a summary of skill, preferably at the beginning of the resume.

This type of resume is the only one that should use jargon and technological terms. If the position you are applying for requires experience in using certain equipment or having particular skills, then this is where you mention it and if possible quantify it. Generally, if a position requires a specific skill, employers will mention it on their job description or advertisement.

If you have experience in an technical area that you think is important for the position, or will give you an advantage over other applicants, then make sure you mention it. It is also very important to list your qualifications and to include any courses, training or seminars you have attended, particularly where they are requirements for the position.

Just remember that jargon and technical language should be avoided throughout the resume. The only safe place to mention it is on the summary of skills page. Often the first person that reads the resume is not a technical person, but a Recruitment Officer, you don't want to write yourself off by submitting a resume that they cannot understand, however the summary of skills allows you to use more specific technological language .

When preparing the summary of skills page, try and group items together with sub-headings so that it is easier to follow. That would make it easier for the reader to find the specific details he is looking for. Be brief and use point form whenever possible.

The rest of the resume should be constructed like the chronological resume. The sequence should be:

Personal details
Career Objective/Summary
Personal skills
Summary of skills (the technical page)
Work history (listing the most recent position first)
Referees

A very important point in both your resume and your job application letter, is to ensure you mention what the employer wants. It is amazing how many people forget to do this. They talk about this and that and totally forget to respond to the job advertisement. Always ensure that you mention achievements and quantify your skills. If you follow this guide, you will have a winning resume that will allow you to get that great job.