10 ms·

How did you go about getting a software developer job without a degree

1 points by smithmayowa 9y ago

How do i go about getting a software developer job if i do not have a degree, but have a portfolio of previous works, Do i stand a chance or should i just suck it up and go get a degree in computer science

davman 9y ago
Previous place I have worked had a strong 'degree-holders-only' policy, but made an exception at least 3 times I can remember for exceedingly strong candidates who demonstrated high levels of skill. If you're good enough, and you have a body of work to prove it, you don't need a degree.
sevensor 9y ago
Do you have any degree? We've had good results in the past by hiring people with degrees in the sciences and (non-software) engineering. If it were purely portfolio, I'd want to see some strong evidence of maturity and self-discipline in the portfolio material.
- smithmayowa 9y ago
  I do have a diploma degree in marine engineering, and as regards the maturity and self-discipline issue how do you suggest i showcase that in my portfolio ?.
  - sevensor 9y ago
    Well, everybody has their own ideas about what good code looks like, but I think the following advice would get you pretty far along: 1. Develop a consistent coding style. Indentation, variable naming, commenting. There are many schools of thought. If you're writing in a language with a large community, pick a widely represented style convention. If you diverge from that, do so consistently. Space-users aren't going to pass on you for tabs, and vice versa, but nobody's going to be impressed if you mix them willy-nilly. 2. This is the next step up. For the languages you use, understand the conventional ways language features and standard libraries are used. Use them in the appropriate context, don't show your ignorance by not using them where appropriate, use them in a way that shows you understand the performance tradeoffs involved. What makes sense in one language may raise red flags in another (e.g. using lots of exceptions in Python versus using lots of exceptions in C++). 3. Organize the overall project in a way that makes sense. Is the organization of the project in line with the conventions for the language you've chosen? Is it clear how to build and distribute the project? 4. Write something that looks like somebody would actually want to use it. If it's a library, it should have an API without obvious footguns. If it's a CLI program, its arguments shouldn't clash with each other, they should be well-documented and unsurprising in their behavior, and you shouldn't spam the console with status information unless the user has activated a verbose flag. If it's a GUI program or website, value clarity and simplicity over graphical flourishes. You're looking for a job as a programmer, not a designer. Also, make sure the thing you wrote looks like it's actually useful to somebody, even if it's a really specialized audience. I've only indirectly referred to stuff that gets taught in a traditional CS curriculum, and only in point (2) about performance tradeoffs and appropriate context. But there's a world of important stuff there. Choose a dictionary when you need a linked list, or a linked list when you could use an array, and you showcase your ignorance. Know what these structures are, how to implement toy versions yourself, and when you should use them. (But don't use your toy versions in your portfolio!) Also learn enough about graphs to know one when you're looking at it. Best of luck!
guilhas 8y ago
I have no degree. There are a lot of companies hiring in UK without it. You just have to be careful for low paying job, sucky software dev, repetitive web dev, companies with low quality team where you will not learn or evolve much. On the long term I recommend degree. It is good for better career progression, and mandatory in many higher positions.

1 points by smithmayowa 9y ago

davman 9y ago

Previous place I have worked had a strong 'degree-holders-only' policy, but made an exception at least 3 times I can remember for exceedingly strong candidates who demonstrated high levels of skill. If you're good enough, and you have a body of work to prove it, you don't need a degree.

sevensor 9y ago

Do you have any degree? We've had good results in the past by hiring people with degrees in the sciences and (non-software) engineering. If it were purely portfolio, I'd want to see some strong evidence of maturity and self-discipline in the portfolio material.

smithmayowa 9y ago
I do have a diploma degree in marine engineering, and as regards the maturity and self-discipline issue how do you suggest i showcase that in my portfolio ?.
- sevensor 9y ago
  Well, everybody has their own ideas about what good code looks like, but I think the following advice would get you pretty far along: 1. Develop a consistent coding style. Indentation, variable naming, commenting. There are many schools of thought. If you're writing in a language with a large community, pick a widely represented style convention. If you diverge from that, do so consistently. Space-users aren't going to pass on you for tabs, and vice versa, but nobody's going to be impressed if you mix them willy-nilly. 2. This is the next step up. For the languages you use, understand the conventional ways language features and standard libraries are used. Use them in the appropriate context, don't show your ignorance by not using them where appropriate, use them in a way that shows you understand the performance tradeoffs involved. What makes sense in one language may raise red flags in another (e.g. using lots of exceptions in Python versus using lots of exceptions in C++). 3. Organize the overall project in a way that makes sense. Is the organization of the project in line with the conventions for the language you've chosen? Is it clear how to build and distribute the project? 4. Write something that looks like somebody would actually want to use it. If it's a library, it should have an API without obvious footguns. If it's a CLI program, its arguments shouldn't clash with each other, they should be well-documented and unsurprising in their behavior, and you shouldn't spam the console with status information unless the user has activated a verbose flag. If it's a GUI program or website, value clarity and simplicity over graphical flourishes. You're looking for a job as a programmer, not a designer. Also, make sure the thing you wrote looks like it's actually useful to somebody, even if it's a really specialized audience. I've only indirectly referred to stuff that gets taught in a traditional CS curriculum, and only in point (2) about performance tradeoffs and appropriate context. But there's a world of important stuff there. Choose a dictionary when you need a linked list, or a linked list when you could use an array, and you showcase your ignorance. Know what these structures are, how to implement toy versions yourself, and when you should use them. (But don't use your toy versions in your portfolio!) Also learn enough about graphs to know one when you're looking at it. Best of luck!

guilhas 8y ago

I have no degree. There are a lot of companies hiring in UK without it. You just have to be careful for low paying job, sucky software dev, repetitive web dev, companies with low quality team where you will not learn or evolve much. On the long term I recommend degree. It is good for better career progression, and mandatory in many higher positions.