Ask HN: Do employers care how long it took you to finish a degree?

61 points by JxGZV ↗ HN
I'm not going to finish my C.S. degree in 4 years, it's going to take me a couple of years more. I'm not able to assist to all lectures and attend all exams because I've been going through a lot of stuff lately, so I haven't been (& am not) able to pass an academic year in a year. My gpa is still good.

I'm worried about being rejected for most applications in the future due to how long it took me to finish and I don't want to come off as whiny or anything in interviews, etc when interviewers ask me (if they do) why it took me so long.

So: Do employers care how long it took you to finish a degree? How important is to employers and interviewers? Is there anything I can do to counteract it?

Thanks.

92 comments

[ 0.23 ms ] story [ 102 ms ] thread
Personally I've always been more interested in why you decided to study what you studied vs what you actually went to school for or how long it took you.
(comment deleted)
Honestly, unless you're putting the years you've attended school on your resume, I have no way of knowing how long it took you to get your degree.

I'm WAY more interested in what you can DO and what you have demonstrably DONE, so it's way more important for you to focus on side jobs, internships, and open source contributions than it is to worry about how long it will take you to get a degree.

For me, it didn't. I took NINE years to get my BA. That being said, an employer might care, but my guess would be, most do not, especially if you go on to get a masters or something else. For most any job experience counts a great deal as well.
Nope, it's never occurred to me to ask that as someone who has interviewed hundreds of people in my his career. If you don't put the dates on your resume, it's highly doubtful anyone would ask unless they could infer it from other things on your resume. One would be if you had a career, stopped it to go to school, and then started your career again. And even then, you can or should be able to easily explain it away. But what really matters is what you know.
I got my CS degree after 6.5 years, normally it's a 5 year program, but I switch from engineering at one point and messed up a semester.

No one ever cared. No one ever asked.

Graduating is what counts, not how long it takes. Your time in school is what you make of it. It's much better to take a long time and graduate, than to take the right amount of time and not graduate, so never give up just because you're late!

Only my university counselor noticed that I was taking a long time to graduate, and chastised me for taking all these exciting high level computer science classes and independent studies that I was interested in, instead of the boring low level pre-requisites required to graduate.

I finally took the required prerequisites and graduated, but unfortunately it was before "Rate My Professors", so I ended up failing and re-taking Statistics from Sergy Brin's dad, who's "awful" [1]. But those extra semesters gave me time to take some other great courses from diverse departments like Art and Hearing and Speech, which were really useful.

[1] http://www.ratemyprofessors.com/ShowRatings.jsp?tid=761872

Generally, no, employers don't care. When you list your degree just list the graduation date.

Regardless of your work history, you should list internships and projects you accomplished while in school on your resume when you are starting out anyway (unless you were already employed in the field). And if anyone asks specifically, tell them, yea I took a little extra time to finish my degree. Never lie and don't deny it just be straight about it but don't go into personal details.

When you are in college all the pressure and focus is around your GPA, graduating whether you were in the engineering school or A&S school etc. When hiring, those factors are never as important as your ability to sell yourself. For companies that focus on your GPA or how long it took you to get through school, I'd be very critical of whether they are looking for the right candidates and whether I'd want to be there. That said, there are some tech companies that have extremely competitive new grad hiring and so they use school, GPA and degree as a filter, but I've never seen length of time to attain the degree a factor.

Good luck!

They really shouldn't be asking specifically. IANAL and I don't think most age discrimination protections kick in until you're 40, but that kind of question - or asking if you were a "non-traditional" student - seems like a roundabout way of asking someone's age, and is therefore quite unprofessional.
It depends. If someone discloses to me on their resume that it took 8 years to get a bachelors, meaning they put 2000-2008 next to that line item, it's fair for me to ask about it. Besides, professional or not, you want them to ask it if they're inclined to ask it. Not because it's information for them, but because it's information for you. A candidate interviews the company as much as the company interviews them, and from my perspective as a candidate I want to know if these things matter to them and why. For instance, there are qualities I appreciate about non-traditional students - people who started college late, worked full time through, etc. I'm not trying to figure out if you're 45 or not. I'm looking for positive qualities, not trying to shake out the negative. I can distill the negatives when we talk about experience, and those have nothing to do with age or anything else.

Beyond that, when I'm interviewing someone, I know I can't or shouldn't ask certain things, and I don't want to make people uncomfortable or break any laws. So I will often casually mention that I'm married or have a kid if the opportunity arises while we make small talk. I never tie it to a follow up question either, because that's too close to the line for me. But I'm not trying to figure out your situation there either. I'm just putting it out there that I have a life outside of here, that I'm probably going to sneak out (very) early every so often, work from home sometimes to get some other non-work stuff done too, etc. and that I won't hold it against you for being a normal person either.

>Beyond that, when I'm interviewing someone, I know I can't or shouldn't ask certain things, and I don't want to make people uncomfortable or break any laws. So I will often casually mention that I'm married or have a kid if the opportunity arises while we make small talk. I never tie it to a follow up question either, because that's too close to the line for me. But I'm not trying to figure out your situation there either. I'm just putting it out there that I have a life outside of here, that I'm probably going to sneak out (very) early every so often, work from home sometimes to get some other non-work stuff done too, etc. and that I won't hold it against you for being a normal person either.

This is a strange thought process. It's illegal to ask about kids/relationship status and you apparently know that. You just attempt to fish for that information because you want them to know that _you_ personally WFH and have non-work stuff in your life? Why not just describe that work culture? Seems like you are trying to find out if they have kids or a wife, otherwise I don't understand the reasoning.

I'm not sure that I described it well in my post, but I don't try and fish for that information whatsoever. I don't ask any questions related to it, but I'm not shy about my own situation either if it comes up in conversation. These days many people are coached not to really ask about work life balance or to bring up anything that would prevent them from being a 100% dedicated, 24/7 employee, and I think that's pretty shitty. I can't really ask about their needs there in a way that makes me comfortable asking it, so if the conversation goes that way, I'll describe my own situation without any follow up questions.

Every company and every manager out there tries to sell people on their great company culture and work-life balance. I actually have one. I actively cultivate that internally and set team boundaries that promote having a life outside of here. It's important (to me) that candidates know that we actually do what we say we do in terms of work life balance.

> When you list your degree just list the graduation date.

This. I reviewed a ton of resumes, and even when I even noticed that total education time was "non-standard" (rarely), it didn't matter. It's easy as an employer to look at transcript and see if someone is slacking off or has other stuff going on. And the latter is probably a good think in terms of your commitment and drive.

It's reassuring to hear this.

I graduated in 2006, having started my Bachelor in 2000, beca8use it turns out that I have a pretty severe neurological disability. I've had much trouble finding a full-time job (one interview started screaming at me after I explained that I have a disability, but was most impressed with me up until that point) and one of my acquaintances explained that it was because I got a degree.

First, he told me that running mail/web/file servers at home show I can do it and haven't just followed an online tutorial but by doing my degree, anybody could have done my work. Then he explained that the length of time that I took to complete the degree was going to stop anybody hiring me. Later, I was told that it was fair to expect that no employer would hire me, there's no legal restriction preventing them from telling me to get lost because of my disability.

Obviously the first and last were wrong, but this is the first time I've heard an employer actually saying they don't really care how long it took to get the degree.

>(one interview started screaming at me after I explained that I have a disability, but was most impressed with me up until that point)

What the hell? Do you mind going into detail?

who said u had to finish?? its what u know. its what u can do. paper is paper
Some employers prefer candidates who have proven history of completed projects. A degree is a one massive project, completed.
Breaks for any variety of reasons are very common in University. Barring a few specific majors where competition is so heavy that a break will lower your standing, most employers won't care, and probably for legal safety, won't ask about breaks. (For example, you might get into stuff you're forbidden to ask about if you bring that up.)
Depends where you try to work. Most employers are only going to care about how sell yourself as a potential asset to their company. In the end, the only thing that matters is your ability to perform your job.

PS. I have a *friend who took 6 years to graduate with a BA in CS and now works for an awesome startup, that also employees some great programmers who never went to college.

PPS. If you're in CS create a GitHub account to act as your portfolio. Work on some projects in college; that way you have something to show the employer when they ask "So what have you done?".

> PPS. If you're in CS create a GitHub account to act as your portfolio.

this is totally unnecessary.

no reasonable engineer that is asked to interview you will look at your github, or care if you have one.

Disagree. Especially with entry level positions, it's a real nice bonus for me when I'm reviewing applicants. It gives me something to look for when there's no work experience to try to craft what this person has worked on.
> no reasonable engineer that is asked to interview you will look at your github, or care if you have one.

yeah gonna have to disagree on this. I'm an engineer and work for a BigCo Enterprisey company and while it's not necessary, if you have a GH account, it makes my job easier when I interview you. Of course if you write terrible code, then the GH account probably is not the best thing to have. But other than that, I can't see a reason why not to have one. If you have one, I definitely look at it and I consider engineers who have one higher than those that don't. Doesn't mean that I won't rate you favorably if you really know what you're talking about, but it doesn't hurt.

> But other than that, I can't see a reason why not to have one.

you are assuming that

* they want to write code outside of working hours

* they will put the same level of attention into the code they write outside of work as they do the code they write at work

* they want the code they write outside of work to be open source

failing to do any or all of these things, or doing any or all of these things, should not affect a candidates impression on you.

Of course it should.

Do you really not see the difference between being able to look at someone's code and trying to guess what it might look like via lame whiteboard implementations of basic algorithms?

I vastly prefer to see portfolio work, and when I assist in screening resumes, I always look at the people with portfolios first: they provide the most signal. How does your code look? How do you interact with others?

When I'm doing deeper interviews, I check the portfolio as well: what is the specialty and interest of the person? What are they up to? Do I want to work with this person?

At the end of the day, we're both human beings, and we have to get along at work. I don't want to be in a bad relationship. So I look at, and prefer resumes that give me the most information to this end.

Other people do it differently.

Relax. You're fine. No one cares. Just list graduation year.

In fact, I wouldn't really care of you had a degree or not. (Its a positive if you have one, but not a negative if you don't).

just put your graduation date.

in my own experience (interviewed for internship, current full time position, and a few competing positions, and have interviewed many candidates):

i did not feel like my educational experience was taken into account when interviewing.

and when my coworkers and i interview candidates, education is almost never discussed.

the only reason i suggest omitting the start date is to get past HR filters.

A few will, the majority won't. The key to not coming off as whiny is not to be whiny :)

As with any Resume/CV issue like this just practice answering the question - a couple of sentences is sufficient, and you'll be fine.

Some will, some won't. In all honesty I think you should be glad for the ones that will reject you based on that. It shows a toxic culture focused on things that aren't really important.

Much more important is where your degree is from as to whether it means anything.

You should have an answer prepared for why it took longer that is reasonable and doesn't reflect badly. I.e. "I failed classes and had to take them over." doesn't sound good. "I took a lighter class load so that I could work while going to school to lower my debt." sounds reasonable.

"Going through a lot of stuff" isn't good enough.

I dropped out of school in 2001 because my parents got divorced and I no longer had a stable home to live in and I also broke my leg and had huge medical bills, so I needed to make money and get an apartment instead.

I would call that "going through a lot of stuff." It's not good enough though? Why not?

So the way you would want to explain that to a potential employer is "I had to take a break from school due to financial problems."

The actual phrase "I was going through some stuff." is not good enough. It's an unprofessional answer. You need to be able to explain what "stuff" is in a professional way that makes sense and isn't overly dramatic. Otherwise the concern is you're going to "go through some stuff" as an employee and have excessive sick days, etc.

Yes, exactly right. Good answer :)

I mean, I would probably naturally start with "There was a lot going on," and then explain. You know, being that I am human and all, so I have emotions.

Hopefully in an interview you would actually be able to have a conversation, rather than it just being a series of questions where they write down the answer and move on. I suppose you would need to gauge the style of the interview. If it really is going to be that formal, yes, you would need to have precise response like that.

It's hard to imagine an interviewer who wouldn't automatically ask the follow up question when someone gives a vague answer.

Sometimes responding to comments it seems like I am arguing a counter-point, but really I am just continuing the same line of thought from a different view.

They will if it's clear from your resume that you took 6+ years to graduate. It's a reasonable concern for an employer, since the cause is often different from yours (namely, lack of effort).

So, as other have suggested, don't make it obvious. It's ridiculous to see the year of high school graduation on a resume anyway. Also, you don't have to list internships from your first two years.

If it does come up, or if they ask about it, do not lie. The appearance of hiding anything is a red flag. Just tell them that you were dealing with personal issues, and that they are resolved now. So, it won't affect your ability to perform the job.

Is "lack of effort" really the cause in the US? College completion rates seem to be heavily impacted by finances based on what I've heard on NPR.
In my time and place (2001-2006, Idaho) finances weren't the driver for slow graduation or delays. Frequently it related to poor scholastics and retaking things (excessive pot, excessive alcohol, excessive video games are frequent contributors). Other aspects might be: had a kid, got a job, but those usually were thing that led to dropping out.

Your typical scholastic college student in my peer group did just fine in graduating between 4 and 5 years.

N.b., a lot of the wailing over school costs is from the Ivy League and SLAC set; those prices drive up the average considerably. State universities are much, much cheaper. (Still spendy... but often an order of magnitude cheaper).

> N.b., a lot of the wailing over school costs is from the Ivy League and SLAC set; those prices drive up the average considerably.

Not really; there's not enough schools or slots in that set to drive up the average much.

> State universities are much, much cheaper. (Still spendy... but often an order of magnitude cheaper).

Both State universities and non-elite private universities have gotten expensive much, much faster than elite private universities (and both, especially State schools, have much less school-provided need-based grants available, resulting in much more dependence on loans, and much more impact on actual affordability from the sticker price increases.)

I'd like to piggyback on this question with my own, which is relevant.

tl;dr: do employers care at what age you finish your degree?

Long story: I'm a 35 year old software engineer with 6 years of experience (mostly java/scala), currently an EU citizen residing in UK (London). I've studied CS when I was 18 at the universtiy, but dropped out (various reasons). Now since Brexit news I no longer feel I want to continue living here and I am strongly thinking of moving to USA. My plan is to get a Computer Science BsC from Open University in 3 years, apply for H1B visa/job and then later green card. I'm only doing my degree now because of H1B requirements, no other reasons. I would be 38 by the time I finish it.

No, I think going back to school shows that your serious about your occupation, if anything, its a huge plus IMO
Right, I am actually going to school because I want to. I am already 34. I am learning at probably twice the speed I did when I was in my 20s, because now I've experienced what they are talking about.
In your case, it seems unlikely to be an issue. In most circumstances, I think it would result in a few extra questions.

Generally, a degree that comes after years of professional experience indicates a career switch, and those employees often need to work harder to find a good fit – usually, an organization that can make use of the skills they learned in the previous phase of their career. The reasons for this mostly come down to being very junior in skill level but having difficulty working under the same circumstances (low pay, trained by a 25 year old, potentially long hours...) of the typical junior hire.

There are exceptions to this, and there are many career switchers that navigate this well, but it's definitely worth keeping in mind.

I am getting my degree now and I've already been in work for 17 years. Why? Because I want to know the theory! :)

(My name relates to the part I know)

I can answer as someone who has done hiring.

Legally, no they don't care. There will be hiring policies that dictate complete independence of non-relevant factors

Truthfully speaking, as long as you're under 45 and you've done something with your life during your non-working time, you're okay. It really helps if you can have a steady employment history, or at least proof you've been given money for doing something related to your degree, but my experience is that 45 is the first age where questions start to arise.

For traditional businesses in the US, longevity and dedication to the company are big. 5 years at a traditional company is considered a short time - the closer you get to retirement, the less you can give the company, and the closer you are to having age related ailments, etc. Age discrimination is very real, especially in tech (and doubly so in programming specifically), but you're well under the limit for most employers. A few start-ups might go cock-eyed at the graduation dates, but start-ups are a different beast entirely.

I was a 34 year old software developer when I started my first semester at a US community college. I transferred to a top US engineering school a year later. I finished two BS degrees (Computer Science and Electrical Engineering) at 38 and started working on an Electrical and Computer Engineering MS.

It is my impression that employers don't care. They care much more about what you've learned, the projects you've worked on, and how passionate you are about the field.

As most everyone says, no most interviewers won't care. In the small chance anyone ever asks why you took longer, just don't spin a whole sob story to explain. Just say 'personal circumstances' or so, very short and neutral, and quickly divert attention away to your GPA (if it stays good) to make it clear that it's not because you couldn't do the work.

I had an interviewee once who would try to explain everything that was remotely sub-optimal on his CV with long stories of how horrible his upbringing was and how hard he had it in life. I guess he was trying to get sympathy but all I heard was 'drama all around'. Now, being able to overcome adversity is a good thing in general, but there is a fine line between that and being desperate to blame everything on everyone else or emotionally blackmailing people.

So my advice, for what it's worth, is to not be seduced into giving long emotional explanations. Just say 'I had to work a full time job' or 'I had to finance myself' and leave it at that.

You have not really overcome the adversity yet if it's still a chip on your shoulders years later.
What you need to understand is that employers don't care about anything other than whether you will be a good fit for the position you are applying to. Your CV is just a way to try to assess your skills and character, just like in-person interviews are.

So yes, an employer might take into consideration how long it took your to finish your CS degree but ultimately it likely won't matter much when all the other factors are taken into consideration. It's one tiny factor that may be very important for you right now but doesn't actually provide much useful information to the employer.

EDIT: Just to make my point even clearer: taking slightly longer than expected most likely won't stand out at all. Taking significantly longer may be a negative factor, or it may be a positive factor, but either way it will most likely not be even close to one of the most important factors an employer might consider unless you literally submit a slip of paper with only that piece of info on it.

They most definitely do not.
I have a B. A. In Fine Arts (studio specialization). I have spent all of my career as web, then software developer of some kind.

While I sometimes envy you (and others) for having CS degrees, I have never had a difficult time landing work as a developer. Imposter syndrome is still pretty high though.

As many others have suggested, just list the graduation date. That's all prospective employers care about. The fact that you have a CS degree matters more than how long you took to earn it.

But even that pales in comparison to your ability to clearly communicate what you're competent at. So focus on your communication skills and self esteem. And you'll do just fine!

Hi all,

I'm reading Hacker News pretty regularly but didn't bother to register since now that I saw this question from JxGZV.

I come from really small EU country that was formerly communist and I'm also an CS student in my final year:) With that being said, I want to share my experience that I had recently with a pretty well known big company which is in the business of software engineering and was merged with another company in 2012. Because of various reasons I'm studying longer that it is expected, but nevertheless my CV is outstanding, since I have many achievements as an undergrad (participating at conferences with posters, winning hackathons etc....). To make long story short, I was asked what was I doing all these years and if I was "doing drugs or what?!".My answer was "No I did not". I didn't get an offer after this interview and was really happy because of that.

For anyone reading this, if you are in a similar situation, do not stress yourself with such questions. Just send the application and CV. If they ask questions like these, you can find a better employer and you probably don't want to work for them anyway. Believe me. I experienced it.

If a political science major with a 2.0 gap spends 6 years going through a big state school - recruiters will assume they spent the time drinking. It won't hurt in a sales or politics job but perhaps elsewhere.

It won't hurt a smart CS major with a good GPA. When asked, say, "I self funded my education" or "I had to work" and that can even become a plus. (Just don't outright lie)

It took me four years to finish my degree (normally it should take 3) and nobody has ever brought it up in the last three or four years (I gradueted in 2011).

Don't sweat it too much - most people understand you can be perfectly capable of doing the job without having adegree in CS. More to the point, a lot of programmers don't even get a CS degree and they still hold down very productive programming jobs.

Most employers (in the US) care first and foremost that you have a degree in your field. Not so much where you got it, or how long it took you to get it.

inb4 people start posting they don't. HN isn't a solid representative sample of the US let alone world job market.

Yes, you are likely to get questions about it. If you have an interview it is wise to know beforehand what you will answer when they ask you this question. But it won't prevent you from landing a decent job.