Archive for the 'career advice' Category

Creating Great Job Docs

I would like to thank Dana Bright from Career Services who came and talked to us last week about job application documents. Creating these documents–affectionately known as resumes and cover letters–are difficult for students and professionals alike. The talk helped to add clarity around this ever evolving topic.

Before I relay the highlights from the discussion, let me first stress that the items listed below are the norm. That said, there will be outlying situations that are not accounted for in these statements. The items below, like Dana mentioned, are the safe bet.

I have broken down the information into 2 sections Cover letters and Resumes. Inside the Resume section there is information regarding government and industry resumes.


Cover letters should be prepared for every job you apply to. Below are some items to keep in mind while creating them:

  • Limit to 1 page.
  • A four paragraph cover letters should:
    • Introduce yourself to the hiring manager
    • Argue why you’d be a good fit for the job
    • Fill in places your resume cannot describe
    • Further explain other aspects of your resume
  • Consult for more detail.


First and foremost, there is a big difference between the documents needed to apply to government jobs and those needed for industry jobs. As a result, the two are addressed separately below.

Government Job Resumes

The government requires a standardized and highly specific resume. Therefore, using the resume builder found at to create a resume is the best option. When using the resume builder, the questions should be answered in their entirety, including the sections that are not often required in industry resumes, like hobbies, coursework, or information about High School experiences.

Industry job Resumes

There were a number of recommendations pertaining to industry resumes. For the sake of brevity (and reference) I use bullet points to cover the items. The list is further sorted into the broad categories: generalities, content, and design.


  • Resumes should be clean looking and professional.
  • Use 1 page unless you have 10 years or experience.
  • List your strongest assets first. For students, that usually means education is the first section.
  • Tailor the resume to the job application, make sure to address all of the requirements fully.
  • Ensure that each job listed has a job title, employer, date, and location. Do not use summer, fall, or other seasons. Instead list the start and ending months.
  • Do not overly use keywords (e.g., creating a list of skills just to use keywords), simply employ the keywords naturally in the description of your job duties.
  • Use present tense for current jobs and past tense for previous jobs.
  • Eliminate the objective, it takes up real estate and is not helpful.
  • Streamline the resume to cover only the sections and material that represent you well. Remove hobbies, personal interests, previous colleges, and odd jobs if they do not pertain to the job you are applying to.
  • Remove bullet points for obvious jobs.  For example there is no need to describe duties for cashier or waitress, unless the duties are atypical.
  • Google resumes from your field and model the good ones.
  • Do not include non-professional links (e.g., Facebook or Twitter). But do include professional links like LinkedIn and your portfolio. Add links these links at the top of your resume with your contact information.


  • Show your expertise, don’t just tell it.
  • Do not embellish or lie.
  • Stick to job duties that demonstrate strong transferable skills.
  • Remove HS and your HS experiences from your resume unless they are directly applicable to the job (e.g., you led the accountants club for 2yrs in HS and you the job you are applying to is an accountant). The only exception is Eagle Scouts.
  • List accomplishments over mundane tasks. For example, instead of “I answered the phones” say something like “Responsible for…”
  • Avoid listing nebulous unsupported claims in a list of skills (e.g,. good communicator, trustworthy), instead show these attributes through examples from your job duties. For example, you might you would list public speaking to demonstrate your confidence in communicating.
  • Remove “I” or “me” and stick with action verbs.
  • List any proficiency with foreign languages in a skills section. In that case, use the modifiers of basic, intermediate, fluency, or native speaker to describe your aptitude in the language.
  • Remove hobbies unless they directly relate to the job. For example, you would keep your guitar playing if you were applying for radio station work.
  • Provide a “relevant courses” section if they help to demonstrate your fit for the job.  In it do not include general education, instead list the 3 or 4 courses that are completely relevant to the job. When doing so include the course name (without the catalog number) and any tailored highlights that relate to the job
  • List your cumulative GPA ONLY if it is above 3.0. Do not include your major GPA or substitute it for cumulative. The major GPA can be misleading and can cause confusion once your transcript is reviewed.
  • Include a summary or profile statement at the top of the resume, if you need to explain some transition. In this case, the statement should be your elevator pitch where you pick 3 or 4 of your top assets. Include a few words that support the need for the statement (e.g., “seeking to transition into”).
Comments for specific majors
  • If you are a humanities major, eliminate a skills section and incorporate those items in your list of job duties or courses.
  • If you have a government security clearance, it should be listed on your resume. Try to place it near the top. A summary is a good place to include your clearances.


  • Do not use Word templates, they are a tremendous pain in the long run. Stick to a resume without without tables or boxes. Starting from scratch with a fresh new document is your best option.
  • Use an all black serif font, no color.
  • Make your name and other headings no larger than 14pt bold and text between 11pt or 12pt at most.
  • Maintain 1″ margins with single spacing
  • Use a serif font (i.e., Tahoma, Calibri);  it comes across as more formal. Note, there is some flexibility in fonts as sans serif becomes more popular.
  • Send the resume as a PDF, if possible. PDFs will retain your formatting and Word may not.
  • Do not use a full line at the top, it separates information on the page too much.

Should anything in this long list be unclear, I’m sure Dana would welcome any questions you might have about this material.



FSBO: Selling Yourself with a Free Personal Website


Things are looking up for tech writers. The Bureau of Labor and Statistics predicts an above average growth trend for technical communicator positions nationally. Despite the good news, many of us still face a competitive and often frustrating job hunt. We mine through job postings, submit cover letters and resumes, attend job fairs, and meet with college career counselors. Yet, we still cannot land that dream job. What’s missing? How can we get a competitive edge?

More and more people are discussing the benefits of having a personal website while searching for a job. Forbes staff writer Jacquelyn Smith believes that personal websites are now crucial resources for the job hunter. She finds that a majority of “hiring managers are more impressed by a candidate’s personal website than any other personal branding tool.” Yet, only a small minority of job hunters actually has one. Considering this increased interest by hiring professionals, job seeking technical communicators, always mindful of their audience, should give hiring personnel what they want.

WWWThe personal website becomes a single dwelling that houses all the relevant information necessary to evaluate the prospective employee. Smith provides a list and explanation of the necessary requirements to promote your qualifications, which includes both traditional forms, like resume and writings samples, and more innovative forms, like links to blogs and multimedia. Including links to your works published online gives employers a sense of your capacity to write in multiple genres.

For the tech writer, the personal website becomes an online portfolio. Portable and easily updated, the online portfolio provides human resources personnel an opportunity to review functional examples of your work prior to an interview. Tom Johnson suggests including a “quick reference guide, a user guide, online help file, video tutorial, newsletter article, release note, magazine article, and any other format you can think of.” Experienced tech writers can be discriminating in what to place on the site. Students with limited samples should put what they have available and create samples of other genres. Examples should highlight your diverse skills and demonstrate your ability to communicate persuasively in a sophisticated, relevant, and technically savvy manner.

If you remain reluctant, thinking that perhaps it is too expensive to launch this innovative job hunt tool … DON’T.

A personal website designed to market yourself as technical communicator par excellence does not require a domain name or expensive hosting. Rather, you can easily create a personal website through various do-it-yourself website builders at no cost. Beautifullife offers a comparison of the top fifteen free website builders and their basic features. Among those making the list, I personally reviewed Wix, Doodlekit, and Moonfruit and found each user-friendly, requiring no coding knowledge whatsoever. All three provide user support to set up and maintain the website. Wix and Moonfruit offer video tutorials, as well as help forums to assist users in the website development. Doodlekit offers a more limited help page through a support forum. Each of these website builders provides various template designs to create the job hunter’s professional online image and to house the owner’s sample work and credential information. Wix, however, offers the most variation and sophistication in its gratis offerings.

One notable absence from Beautifullife’s listing, which reviewers note, is Google Sites. Google Sites allows those Google Gmail account holders to create multiple, individual websites – something the other three sites do not allow without a charge. Google SitesMore streamlined than Wix, Doodlekit, or Moonfruit, Google Sites can still generate an aesthetically pleasing self-marketing website through its dozens of templates. Like other website builders, Google Sites offers step-by-step instructions and includes links to video tutorials on YouTube. Easy to use and effective for creating an individual’s basic personal website, Google Sites may serve all the functions you need. One downside of Google Sites, however, is the limitation of situating images on the pages. For the job hunter wanting to include images on the personal website, Wix, Doodlekit, and Moonfruit allow greater maneuverability.

Using one of these free website builders not only saves you money, but it also allows you to emphasize your technical communication skills through creative and effective design. Technical communicators, more than most other professionals, benefit from this novel means of presentation because the website itself becomes an example of their work and, if done effectively, should make the sale.

-Val Mullaley

Learning the Language of the Web

Entering the world of technical writing can be an extremely intimidating task. People whose primary skills include a sharp eye for grammar and intuition for style are often startled at how many seemingly unrelated skills they may have to know to land a job. The emphasis on “may” is important—since there are a diverse number of ways that documents can be authored and published now, the task of deciding what you should learn to make your resume stand out becomes daunting. There is plenty of advice out there on what technical skills you should learn as a beginning tech writer, with suggestions ranging from XML to programming and database languages. While these are great things to know, the shift toward using wikis and other forms of web-based documentation leads me to think that, for a technical writer who is totally uncertain what kind of job they’re going to end up in, knowing the basics of coding websites is a safe bet. Even if you end up having to author on a different platform, you can impress potential employers by demonstrating your willingness to acquire technical skills.

Luckily, there are an abundance of resources available for learning how to build and maintain websites. Below, I’ve listed what I have found to be the most useful to learn and where I have had success learning these skills.

The Fundamental Web Languages

This is not a comprehensive list of the coding skills you might have to acquire as a technical communicator. However, given the increasing focus on web-based documentation, it’s good to at least have a passing familiarity of these essential web languages. Keep in mind that unless you advertise yourself as a tech writer AND web developer, you’re not reasonably going to be expected to be able to build a website from the ground up.


Hypertext Markup Language (HTML) can be thought of as the skeleton of a website. It provides the basic structure of a site’s content and is capable of determining to a large degree how it will look. If you choose a single language to add to your toolkit, this is the one to go with. Even if you’re not working with web-based documentation, you will probably encounter HTML if you author any sort of browser-based help system. It may also ease the process if you find yourself having to learn another popular markup language: XML.


Cascading Style Sheets (CSS) are used to dictate the formatting of pages written in markup languages like HTML. This is the preferred way to apply a consistent style to websites, as one page of CSS can be linked to all HTML documents on a site. Changes to style and formatting can then be applied by changing one document instead of hundreds. If you think you might be working with web-based documentation, learning this language will probably save you from hours of mind-numbing labor.


JavaScript is a scripting language that is often used when a website needs to interact with a user for information or when it needs the browser to perform a specific function. You probably won’t need this too much as a technical communicator, and the few scripts you might need (like one to open all links on a page in a new window, for instance) are easy to find after a quick Google search. However, it’s useful to know the basics to get a good idea whether the code you’ve found online is likely to work for your purpose or not. Also, JavaScript is a good starting point if you decide that you really like coding things and want to learn other programming languages.

Where to Learn Them

All of the sites recommended below have lessons covering all of the above languages (and more!). Each site is going to have its strengths and weaknesses and will cater to a different learning style, so it’s good to check them all out and see which ones have lessons that you might be able to get the most out of.



The first important thing to note about W3Schools is that it is not actually affiliated with the World Wide Web Consortium (W3C). W3Schools has been criticized for misleading people into thinking otherwise, but many still cite W3Schools as a great source for beginners and a good reference to have around if you forget which tags you need to use in your document. Just don’t give them money for their useless certificates.



For people like me who already have to motivate themselves to do things by thinking of their self-improvement in terms of game mechanics (+5 JavaScript skill, Erin levels up!), the recent trend of gamification has produced a number of invaluable learning resources. Codecademy is a great site for anybody who wants to feel like they are being rewarded at each step of the process of learning to code. Users are awarded badges for completing interactive lessons in HTML/CSS, JavaScript, and a small collection of other languages. While the information is not as comprehensive as it is on other sites, having the opportunity to practice exercises within the browser in a well-designed environment and being rewarded with colorful badges may motivate you to accomplish more than if you were staring at a wall of instructions.

Image is amazing for a tech writer who needs to quickly build their software and web skills. Not only can you access video tutorials on HTML, CSS, and JavaScript, you can learn about Adobe Creative Suite, Microsoft Office, social media marketing, enhancing usability…there are thousands of courses, so the list goes on. Unfortunately, full access to the site requires a membership fee (although it’s totally worth it if you can manage it). Some of the videos are available for free on the site and on YouTube. Here’s a basic video about why HTML is like a sandwich.

If the prospect of learning all of these things is still somewhat intimidating, remember that for all of the diverse situations you might find yourself in as a technical communicator, you’re still more than likely going to be working at a computer that has access to the internet. You absolutely do not have to memorize every HTML tag that exists. As long as you familiarize yourself with the principles of each language, you should be able to do some research and find some code that will accomplish what you want it to.

I hope this guide helps some beginning technical writers know where to start. Feel free to post in the comments if you have any additional resources that you have found helpful—or if you want to brag about all of the badges you’ve racked up on Codecademy.

—Erin Gowdy

What is at Stake in Social Networking? Your Job.

A decade ago, I lost my job at a company I had been at for a number of years because of a questionable post I made online that indicated I had not so friendly feelings for “the ole boss lady.”

Back in 2007, a couple of reporters from The Columbus Dispatch surveyed a number of Ohio teacher’s profiles and also provided snippets of their posts and descriptions.  In a side bar, they also recounted the tale of 4 teachers who had been “reprimanded, resigned, or lost their licenses because of email, IM, chat, online gaming, text, blogs or postings involving students” (Maranto and Baron 36-37).

Recently, the National Labor Relations Board reviewed 129 cases involving social media in someway, where they have found that the crux of the legal issue resulted with an employer unlawfully discharging or reprimanding an employee on the grounds of social networking misuse.

Here are the two links to the archived articles from The Columbus Dispatch and the U.S. Chamber of Commerce’s Survey:

U.S. Chamber of Commerce, A Survey of Social Media Issues Before the NLRB: issues-nlrb

Consider also that a year ago, while I was working for a background screening company, I learned it was not uncommon for human resource managers to search the web for additional background information on potential candidates.  They were trying to discover what their extracurricular activities included: the results ran the gamut, from drunken sprees and skinny dipping to squeaky clean photos at fund raising events or weddings.

So what is at stake in social networking?  The quick answer is obviously reputation.  Another answer?  Your job.

My company chose to terminate my employment because of the potential readers in my network, citing that it would reflect poorly on them to have someone like me on their payroll.  Someone like me?  Who exactly am I to them?  A dissident?  A slacker?  Possibly.  The possible interpretation by others was a very real threat and potentially damaging to their reputation as an employer.  Thanks to my ruminations on “the ole boss lady,” I wrote my way to the unemployment office.

Two things were happening here: 1) My virtual identity was no longer a free agent and 2) the information on my chosen social networking site was no longer just an update among friends.  It was public domain and my employer was monitoring the site.

That revelation seems so obvious.  So why do people continue to risk their reputation by posting questionable or inappropriate material?  There is no easy or fast answer – people make mistakes, but I suggest the very structure of the site we find ourselves on influences our attitudes about the things we post.  When we sign up for Facebook, it asks a host of categorical questions in order to network you to others like you.  What music do you like?  What books do you read?  Where do you live?  All of these personal questions, lull the applicant into forgetting that this site is public, public, public – but once you have 200 plus friends, who can remember if their old boss or coworker is a “friend?”

What all of this boils down to is intention.  Did I intend to mar the corporate image of my company and disrespect my boss or did I intend to sound cool to my friends?  As a student, as a teacher, as a technical communicator, it is important to keep in mind your purpose and your audience– just as you would when you are speaking or writing at school, in the classroom as a teacher, or at work in a corporate environment.  What’s critical here is not only your self image displayed online, but also the many social spheres your image is tied to.  For instance, many corporations now have social media policy that asks you to be yourself, but to be mindful that you are also a company representative.

As a teacher, the online world can be perilous.  On one hand, networking with students can be a fantastic opportunity to become a virtual representative of and for the interactive classroom.  On the other, it could simultaneously undercut ethos and authority, opening the possibility of seeing students as “friends.”  The online world may behave differently, with its fast moving bits and clips, but the reputation you build for yourself through dialogue is the same – keep it clean, positive, and professional – and your social network won’t get you into trouble.  Post like your mom is reading every word you type.

On the flip-side, even if you do have a horrible interview because human resources found some pictures of you doing a keg stand in college, there’s probably still a friend on Facebook that can help you find a lead elsewhere.

Want a refresher?  Check out this Toshiba sponsored YouTube clip for Do’s and Don’ts of social networking.

Rachel C.

Journalism, Tech Comm, and the Skills in Between

As a broadcast news major in undergrad, I never thought I’d be in a technical communication program. But if there’s one thing you learn about Huntsville, Alabama: The technology field is a major industry here in the Rocket City, and the more technical skills you possess, the more marketable you are in this town. But with a degree in broadcast journalism, the most I knew about technical communication was how to communicate and operate a video camera….Or so I thought. But as a technical communication student, I’m learning that I have more skills that translate to technical communication than I thought.

If you too are a journalist attempting to break into the field, identify what skills you possess, and how to apply them to technical communication. Here are some overlapping skills that both journalists and technical communicators have, according to a blog post by Scott Nesbitt entitled: “Tech Writing and Journalism: Yes, There are Parallels” on the DMN Communications blog.



According Nesbitt, “Writing is a key factor in technical communication and journalism. You don’t need to be a great stylist to be an effective technical writer or journalist, though. You need to be able to write clearly and write tightly.”

Basically, write concisely. If you’re an editorial journalist who writes for print media, this may be a little bit of an adjustment. But if you’ve ever written for television news, this is right up your alley. Use the simplest form of words to make your audience understand. Assume that no one knows what you are talking about unless you explain it to them because in most cases, they really won’t understand.



This is a skill you probably didn’t even know you would need as a technical communicator. But interviewing can play a just as big, if not bigger, role in technical communication as writing can. As Nesbitt puts it, “ …you need to know how to ask the right questions, and not be afraid to ask dumb ones. On top of that, you’ll need to know how to gently draw answers out of reluctant interviewees and to spot tangents that are worth following during an interview.”

As a technical writer, you will have to interview the technical professionals in your organization, so that the information that you are distributing to the user is correct and most efficient. You won’t know this information if you don’t ask the technical professional. And you have to be sure that the questions you’re asking will provide the information that users need to know.



Journalists are known for finding the information we need to obtain, whether it’s handed to them on a silver platter by very cooperative forces, or if they have to dig around and investigate for themselves. According to Nesbitt, researching “ can take many forms: looking at design documents, reading up on subjects like virtualization, or even going over documentation for products that are similar to the ones we’re writing about.

All in all, transitioning from journalism to being technical communication student hasn’t been as bad as I thought it would be. Sure there are some aspects of it that I never would’ve probably seen in news, such as learning computer programming, or learning the inner workings of an engineering firm, but all in all, it has been smooth sailing… so far.

-NiCarla Friend

Not Working as Intended: Bug Reports and the Over-reliance on Technology

Bug reports are probably the most hated bits of literature in the lives of software developers, but they’ll always hold a special place in my heart. Writing bug reports gave me my first taste of technical writing, and in fact led me to technical communication as a field. It also gave me my first taste of the kinds of problems that afflict technical communication as an occupation.

Bug reports offer interesting insight into the world of technical communication as a whole. For as short and simple as they are, bug reports have all the elements of good technical writing and suffer from most of the same adversities. Namely, most bug reports are bad because technical writers aren’t the ones writing them.

By nature, bug reports need to be simultaneously concise and descriptive. If you’re overly wordy, explaining every opinion you have on the software and every detail that led to the bug, down to what you were wearing and what the weather was like, no one’s going to read more than one of your reports. On the other hand, if you submit “This function is not working as intended, please fix,” I can guarantee that some developer somewhere is plotting how best to kill you. Writing a good bug report requires someone who can distill information sent in by angry users and over-tired testers and compile it into something clear, concise, and useful to be sent to hassled and harried developers. In short, it requires tech writers, and unfortunately that’s not who’s writing them.

A large part of the blame for this lies in the fact that most people don’t understand why such a specialized vocation is needed. Who would know how to explain something to developers better than other developers, right? Why would you spend money hiring a whole other person to come in and write these reports? While this mindset is certainly troubling, what I find equally worrisome, if not more so, is the over-reliance on technology to do the heavy lifting.

With the advent of cheap and powerful bug tracking software, it seems hard to justify paying someone to write bug reports. The important element that’s often being missed, however, is that these programs are excellent organizational tools made to help technical writers, not replace them. Zendesk and JIRA are wonderful, but they just can’t do the work of even a single technical communicator.

Zendesk is pretty rad, if you ever decide to check it out

Pictured above: An excellent organizational tool
Not pictured above: A technical writer

The problem arises when people believe these programs can do more than they’re actually capable of and assume they’ll do most of the work in making bug reports usable and useful, leaving the actual writing of the reports in the hands of developers who are unqualified to write good reports and busy enough with their own work anyway.

The biggest shame if this, in my eyes, is the misuse of what would otherwise be an incredibly powerful tool. Good bug tracking software, in the hands of a skilled technical writer, can allow for tracking trends in software issues, assigning bug fixes quickly and evenly across developers, and responding immediately to users’ problems. It can allow a single person to keep things running smoothly amongst developers, asset providers, and stakeholders. None of this will work, however, without the one thing that bug reporting, and in fact much of the technical communication field, is missing: a competent tech writer to tie it all together.

-Evan Taylor

Liberal Arts Meet the Hard Sciences: Combining Communication with Science

I recently read Technically Speaking: Oral Communication for Engineers, Scientists, and Technical Personnelby Harold Weiss and James McGrath Jr. The book discusses ways members of the scientific community can become better oral and written communicators. As a communication arts major, I started to look back on all my English and communications classes that I had had with any sciene majors and how the hard sciences and liberal arts had interacted together. Mixing the liberal art of communication with hard sciences such as engineering has never been an easy task from what I have seen. They tend to resist each other in the same way two magnets do when you try to push the ends with the same polarity together.

But a growing trend is the idea of these two different disciplines working together to make everyone’s lives easier.

Everyone’s got a gift for something. For some, the gift is speaking. Others can write. And then there are those that can send rockets to the moon.

Then there are the tasks that people do not have much of a gift for. Not everyone was born to sing. Some cannot write. They just do not have the words. Others do not know much if anything about thermodynamics. I myself can write and use words pretty well. But I definitely am not gifted with a talent for any type of engineering. Basic concepts I do get when explanined to me. Go beyond that and I am out of my league. Luckily for me (and all of those others not born to be engineers) there are those gifted with a talent for engineering.

Many of those gifted with engineering talents often find themselves not exactly poet laureates. That is where someone like a technical communicator who is gifted with a talent for words and writing comes in. The game is changing. It’s not enough to be a groundbreaking engineer. You have to be able to talk about it to an audience who may or may not have any knowledge of engineering in an articulate fashion. And this is not always an easy task. It can be difficult to translate technical jargon into common everyday language. Enter technical communicators. They can use their gift of writing and words to help show off the talents of a great engineer in a way that people can more easily comprehend and thus appreciate more.

Everyone has gifts and it is important to share those gifts with others. Engineers and scientists are some of the most brilliant people in the world. Many of them do work that I cannot even begin to fully comprehend. But not everyone in the world can know and appreciate this because these same brilliant engineers and scientists just do not have a gift for oral and written communication. In steps technical communicators, who have a gift of words and writing. Why not let the gifts and talents of one discipline help show off those of another? Engineers and scientists need to share their brilliant work with the masses who may or may not be engineering experts. Technical communicators can help engineers and scientists accomplish this task. The engineers and scientists get to show the world their brilliant work. Technical communicators get to use their gift and writing and words to help. And people get information presented to them in a comprehensible manner.

So in the end, the formula reads:

Engineers and Scientists brilliant work + Technical Communicators writing and words = Brilliant work that can be understood and appreciated by everyone a.k.a Happy People.

Sounds like a winning formula to me.

– Jay Cavender

Playing at Work by Heroic Technical Writing

Check out this great post from HeroicTechnicalWriting, a blog by NASA technical writer located right here in Huntsville. The post, Playing at Work, describes how play factors into the work of a technical writer:

Play can take many forms, but for me, it’s mostly a matter of rearranging ideas or words or combining them in unexpected ways. Part of the enjoyment for the writer is arranging words in just the right way to accomplish the end you want. Sometimes it’s like playing with words like blocks or Legos: the solution I’m searching for must be correct and elegant.

The post also argues that play allows technical writers to imagine the perspective of the user, kind of like “method acting for the writer”. It also offers some great comparisons between the work of technical writers and English majors. Give it a read, and check out the rest of the blog for more great insight!

Non-Technical Majors in Technical Jobs

Inside Higher Ed recently posted an article about ConAgra Food’s pro-active attempt to hire employees outside of technical majors for technical positions. The company is seeking students with strong critical thinking and leadership skills who can learn the specific technical skills necessary for IT positions. Jim Bretl, who directs the Career Center at Creighton College where ConAgra is heavily recruiting, offered his thoughts about the kind of employees ConAgra is seeking:

In a meeting about the program a few years ago, Bretl remembers Schutté saying, “I don’t just need coders and programmers, I need thinkers.”

“They want people who can analyze information, who can write and present,” Bretl says. “They’ll teach them the details of the system they have, but it doesn’t matter if the student is an English major or a philosophy major.”

A poster over at Engineering Blogs offers an interesting perspective on why English majors might be well suited for some IT jobs:

Even if you majored in a technical field, the odds are very good that 90% of what you learned in college will be obsolete within ten years.  Communication skills, on the other hand, never go out of fashion.

The discussion is highly relevant for technical writing students, who often bring valuable non-technical skills to technical positions.

$mart $tart Wage Negotiation Workshop

AAUW and the Wage Project are offering a wage negotiation workshop that helps teach students skills for negotiating a fair wage with their employer. The workshop is specifically directed towards women, as research shows that female employees are more hesitant to ask for raises at work. However, the workshop is relevant and open to men and women, and it’s free to UAH students. There are 40 available slots and plenty of open seats.

The workshop will be held from 1-4 on Friday, November 4, in the UAH Salmon Library room 111. Interested students can register through ChargerPath. Others can register here.