RT @PBSMediaShift: In search of the perfect skillset for a programmer/journalist
I'd solicit Megan Taylor for her resume, if that wasn't such an embarrasing thing to ask for these days. That's what LinkedIn is for.
Ms. Taylor (I don't know her personally, so I'll default to formal) is the the type of candidate that would play well with the other kiddies in my own corporate sandbox. That being, a PR department that mixes business with social media. It's hard to find folks that know web, journalism and communications, those that are solid writers, designers and developers and can actually think, well you know, strategically.
Her resume lists the following skillsets:
AP Style and news editing, HTML, XHTML, XML, CSS, Flash and ActionScript, beginning PHP, JavaScript, AJAX, content management and online community management, audio/video editing, Adobe applications, Windows, Mac OS, Microsoft Office, Final Cut Pro, fluent in Spanish
I used to laugh heartily at resumes that laundry-listed talents like this, moreso when I would read job postings for triple-majors that "must know three dozen programming languages, usability, information architecture, art and architecture, landscape architecture, gardening, needle-point and can bowl a perfect 300 game." Then again, a four-year college degree these days is the new high school diploma...
More on Ms. Taylor and why she caught my eye. She's interned for Quinn and The Miami Herald, as well as blogs for Poynter and PBS. Not too shabby. Her latest blog post entitled "In Search of the Perfect Skillset for a Programmer/Journalist" really hits home. I, too, am one of those oddball, cross-bred communicators that can both code and copywrite while standing on my head. What a rush. It's what got me started in PR, doing freelance web and at one time, teaching both. I owe my (near) success to my chosen career path, and when I'm not knee-deep in budget or crying over my lost Facebook account, I have a moment to myself to blog.
"In Search of" highlights practitioners of what Ms. Taylor refers to as "computer-assisted reporting" or CAR. In short, CAR is a relatively new concept, seemingly driven by investigative online reporting and the proliferation of citizen journalists who can tweet train wrecks faster than your average multinational media conglomerate. The post further explains that CAR types (I'll call 'em that) should have a fair amount of front-end design, LAMP stacking and geomapping under their belt, and throw on some Flash and Final Cut Pro to boot. Oh, and lest we forget: content management, publishing, editing, writing and the basic tenets of credible and ethical journalism. (I'll assume she implied that last part.)
The upside to CAR, from my point of view, is that you would most likely be the smartest and most capable member of the newsroom/startup/coffee shop. You know that much. The downside? You probably won't get paid that much. It discourages me to think that an entry-level CAR type, even with glowing references and a stellar portfolio, may only fetch $40K-60K/year. Maybe less. Just five year ago, that number would be double. And we didn't have fancy web frameworks or a plethora of Web 2.0 widgets at our disposal (read: to learn and try not to break).
I'd be curious to learn more about CAR and whether PR types (like me) should be mindful. Even more intriguing, what your run-of-the-mill CAR type makes in a year, or per blog post, etc.
And Ms. Taylor, if you're reading: love the resume. How do you feel about Grand Rapids?



Comments [4]