Tech-Savvy Workers Increasingly Common in Non-IT Roles (betanews.com)

An anonymous reader shares an article: IT professionals are becoming an increasingly common presence outside of the traditional IT departments, new research has found. According to CompTIA, it seems executives are calling for specialized skills, faster reflexes and more teamwork in their workers. According to the report, a fifth (21 percent) of CFOs say they have a dedicated tech role in their department. Those roles include business scientists, analysts, and software developers. There are also hybrid positions -- in part technical, but also focused on the business itself. "This isn't a case of rogue IT running rampant or CIOs and their teams becoming obsolete," says Carolyn April, senior director, industry analysis, CompTIA. "Rather, it signals that a tech-savvier workforce is populating business units and job roles."

Comments

Hybrid professional career was great

[rbrander]

I got an engineering degree and certification, then was tossed out of work by a major recession. I went back for a CompSci degree and managed a low-level job in the then-new field of PC support, won a promotion to IT "coordinator" (manager w/o staff, because they were all rented on a project basis from the IT department) with the Waterworks for several years.
Then Waterworks remembered my engineering degree after 100 reminders and took me in as a construction-planning engineer, but I found my IT skills were key to the engineering job. I handled the drafting and GIS systems, was a lead on the project to bring in the new work-order system, was developing small solutions (tiny web apps, fancy VBA spreadsheets, etc) practically ever day. Heck, just knowing real SQL rather than trying to coax complex reports out of Business Objects was a vital skill for construction and maintenance management. It wound up being the last 20 years of my 30-year career.
I can't recommend this career strategy enough; it's more interesting than either IT or the base profession alone, and more secure than either, too. The hardest thing in IT is getting across the real user needs to the developers - and an IT-savvy member of the customers is always going to be the guy that's either handling the IT specifications, and usually the IT project management from the user side; or just throws their hands up at the IT bureaucracy and develops the solution themselves. (Some of my "small solutions" would up taking weeks of time and growing over years into >1000 lines-of-code; hated to do it, but IT bureaucracy would have taken even longer.)
So I tell people interested in IT careers to first become a nurse, accountant, engineer, technician, even lawyer - any profession that USES a lot of IT. Then add in IT, and you are practically guaranteed an interesting and lucrative career.

Tech Savvy?

[acoustix]

Is this what we're calling people who are security nightmares for organizations now? The script kiddie who thought it would be fun to store data in Excel/Access files outside of company control and outside of the ERP? They thought it would be cool to store vital company data in multiple spots, so none of it matched and meant that all of the reports conflicted with each other. Is that what we mean by tech savvy?

Cool. Let me know how that works out for you cause I'm done cleaning up those messes.

COO: Hey did you know that Andy has a really cool report that shows our operational KPIs?
Me: Really? How's he doing it?
COO: I don't know but it's really nice.
Me: [goes to employee] Andy, how are you getting those reports for management?
Andy: Oh, I just setup a little Excel/Access/DB over here on this site and then I copy/paste some stuff into from application ___ and then manually fill in some of the other info as I get it.
Me: Oh, so you're violating company policy by storing that data separately and even outside of company control?
Andy: Yeah, I guess so.
Me: Well, I'd like to run a consistency check on the data against our DB. Can you get me a data dump?
Andy: Sure.
Me: [runs checks against production data]
Me: Hey COO, most of the data in Andy's reports are crap. There are serious data integrity issues. You shouldn't base any decisions on those reports.
COO: what? You need to fix this.
Me: No, I already provide the reports as you have requested. Those reports are based on the actual data in the system. Not something copied half-assed by a kid with no DB experience.