Slashdot Mirror


The Stigma of a Tech Support Background

An anonymous reader writes "Since the last semester of college I've been working as a first line tech support agent. At first it was just a way to earn some extra money; then it became a way to scrape by until I could find myself a real job. By now (almost two years in), it's beginning to feel like a curse. The problem I'm having is that no matter how many jobs I apply for, and no matter how well-written my applications are, I can't seem to get further than the first interview. For some reason it seems a lot of employers will completely overlook my degree in computer engineering, the fact that I can show them several personal projects that I've worked on, and that I can show them that I clearly possess the skills they are looking for. I've had several employers tell me to my face, and in rejection letters, that my 'professional background' isn't what they're looking for even when they've clearly stated that they're looking for recent graduates. In fact, a few have even told me that they decided against hiring me simply because I've worked in tech support at a call center for the last two years. I'm wondering if others have experienced similar problems and if there are any good ways to get employers to realize that my experience from tech support is actually a good thing and not a sign of incompetence."

8 of 613 comments (clear)

  1. Two years in the first line? by ccguy · · Score: 5, Interesting

    first line tech support agent

    No offense intended, but at least the tech support people I talk to on the phone just follow a script (which make you follow), so to me first line support means 'a hurdle I need to pass asap'. Last time I needed "support" they asked me to reboot my computer, then press the windows key, move the mouse to 'run', then type c-m-d then press enter, then type in the black box 'i-p-c-o-n-f-i-g', etc. This was my telco and the problem was I didn't have service. The woman on the phone said they only supported Windows and because I said I had linux she wouldn't open a ticket. I had to fake replacing the linux computer with a windows one ("luckily" I had a work laptop around) before having a ticket open.

    Now, I'm not saying this is your case. But it's hard to believe that these kind of people are any good when it comes to computers. [I'm not saying they're stupid]

    Two years doing that - looks like they just can't find a better job. If they didn't find another job elsewhere and they didn't get promoted in their absolutely low level job...well, it doesn't scream 'talent', does it?

    I've had several employers tell me to my face [...] that my 'professional background' isn't what they're looking for

    You obviously had a chance to ask for more details, did you?

    Anyway...this is what I'd think if I was interviewing you, but I might be completely wrong. I'd like to think you would have a fair chance to change my mind, though.

    1. Re:Two years in the first line? by element-o.p. · · Score: 3, Interesting

      Possibly, but at a previous job, I noticed that the company was far more likely to hire sys admins from outside the company -- or at least from other departments within the company -- than from their own Tech Support group. I thought this was rather bizarre because the Tech Support staff had some very bright people, and because many of the Tech Support people understood how those particular systems worked, by virtue of having spent a year or two (or more) troubleshooting them on the phone with customers.

      Not that I was complaining, mind you -- I got hired directly into the sys admin staff even if there were people in Tech Support who probably would not have had the learning curve I had at first...

      --
      MCSE? No, sir...I don't do Windows. Yes, I am an idealist. What's your point?
    2. Re:Two years in the first line? by couchslug · · Score: 4, Interesting

      Good caveats. I did 26 years in the Air Force, (which has been aptly called "college with a crew cut!) and I met MANY people there who bailed from all the other services (except Coast Guard!). Did the usual (Germany, Korea, 2-something years sandbox deployments, etc) and would do it again in a heartbeat. Aircraft maintenance was great techy fun (Avionics/Engines/Crew Chief on OV-10/F-4/F-16 A/B/C/D).

      Retiring debt-free before age 50 is nice too. I'll be doing the "professional student" thing for a few years (after Aug.'09 when my VEAP-victim self is eligible). Lots of my friends went with related careers after retirement (tech rep, AMT, Lockheed mod team) and are doing nicely. I don't have to work (yay for retiring where it's cheap) so I'll go to school for fun.

      --
      "This post is an artistic work of fiction and falsehood. Only a fool would take anything posted here as fact."
  2. I feel your pain... by SylvesterTheCat · · Score: 4, Interesting

    ...and, unfortunately, I have no useful advice to offer.

    I worked tech support at a (then) Fortune 100 pc "assembler" and seller, including as a member of their corporate tech support group. After I took a job on the company's web team, I was laid off, went back to school full time and got a master's in comp sci.

    I tried to find a job developing embedded systems, preferably in defense industry. I had / have a security clearance, decent grades, significant work experience... and finally after 18 months, one offer from a small company which I quickly took. Nine months later, they laid off 40% of their engineering department...

    I never had anybody figuratively "turn up their nose" at my tech support experience. I think they just looked at it as non-specific work experience, i.e. "could hold a job for extended period of time without getting fired."

    Since then, I've found very well paying work that is still in the IT industry, but really isn't what I had hoped to find.

    Now I am in my early 40s and prospects of finding the kind of work I was interested in (and still am) are quickly fading.

    I am trying to find satisfaction for my itch in personal projects.

    I don't know what it is, but there must be something that I have been lacking or failed to show / demonstrate in interviews.

    For what it is worth, I wish you well in your search.

  3. If you think tech support is bad, try having none by CrazyJim1 · · Score: 3, Interesting

    I can't find a job because I have no experience. That is pretty bad when you first leave college, but after several years companies feel you're unemployable because no one hired you. My only hope for making any income is to create my own profitable software projects.

  4. Re:How to get hired in Tech by scribblej · · Score: 4, Interesting

    Let me add something, since the OP did mention his personal projects.

    It's possible you just suck. Yes, your projects may compile and run, and do what you want, and your experience in school may have left you feeling like the head of your class. It's still possible to be bad at what you do.

    That's not saying you are inevitably going to be a shitty programmer your whole life. Really, really being good at what you are doing takes a lot of effort.

    Anecdotally, my first real programming job interview was with Jellyvision, who were making the (at the time) totally popular game "You Don't Know Jack." I had a long interview with their hiring people and they loved me. I came back the next day and spent all day interviewing with their programmers and design teams and hanging out at the office, which was pretty nice. They all thought I was great. Then I came back in for a third day; the third day I was to bring in a CD of my own code, explain it all, and participate in a code review of what I'd written. They never talked to me again after that, and I know why -- my code SUCKED. I mean, really, really bad. I found some of it on an old disk a year ago and was /horrified./

    I'm better now. I'm not great, but I'm way better.

  5. Re:just lie, make stuff up by techno-vampire · · Score: 3, Interesting
    its called fudging a resume. masters of fudge go a long way.

    I used to have a friend who was a master of fudge. He was great at making up qualifications for jobs he wanted, and after a few years, he'd amassed a long list of jobs he'd gotten that way. The only problem was, he'd lost them all for the same reason: they kept finding out he'd lied to them and fired his sorry little ass. Once, he got a job as a trainee for tech support at an ISP; he didn't last until lunch on his first day.

    --
    Good, inexpensive web hosting
  6. Re:Lack of Advancement, Lack of Experience by nebular · · Score: 3, Interesting

    That also depends on the call centre

    I worked tech support for Apple, I was front line on the phone, I did that for 2 years.

    There was no real advancment for a technical person. The reason? Outsourcing. I worked, not for Apple, but for Minacs Inc. Mincas is not a computer company, they are a call centre company. So the promotion line was up to team leader and manager positions, which are just classic non-tech manager jobs: employee evaluations, quota targets, avg phone times, etc... Anyone with a degree in anything technical or scientific would be going in the wrong direction there. You could maybe get a job with the IT dept, if they were ever hireing and then you'd have to get them to hire someone off the call floor.
    since we weren't Apple, we didn't have every dept. Tier 2 was in California, in fact we only had front line agents, so the only place I could got was to a management position that was usually filled with people who spent more of their day manipulating the call tracking system to make them look better on paper than the people who actually did their jobs well. Yeah the people who just hang up on you are the ones who are put in charge.

    The jobs are good money for when you need it. But it can be hard to get out of it when it can take months to find a job in your actual field and sometimes a promotion at a particular company isn't actually beneficial.