<p>Feature building is a junior developer job. It's also a senior developer job. Feature building is part of any developers job.</p>

<p>QA is testing of those features. If you become a QA specialist you won't be developing features at all. You also won't be using TDD. TDD comes before the code under test. Not after.</p>

<p>QA testers come in two types: <a href="https://sqa.stackexchange.com/a/27737/17901">manual testers</a> and <a href="https://en.wikipedia.org/wiki/Test_automation" rel="nofollow noreferrer">automation testers</a>.  Automation testers are often feature developers as well.</p>

<p>If someones convinced you that newbies must start in QA they've feeding you crap and I wouldn't want to work there. </p>

<p>Some shops don't even have QA roles because the developers test the crap out of their own stuff and then hand it to a peer to test it again with fresh eyes. Some do all that and then still hand it to a QA group who spend all day doing nothing but gleefully breaking software.</p>

<p>QA is a speciality in and of itself. It's a mindset as much as it's ever a job title.</p>

<p>But QA is not where newbies need to start and it's not a dumping ground for sub par developers. QA is where you put your best or it's not QA.</p>

<p>At the end of the day, a junior developer is just someone who might learn a thing or two from a senior developer. </p>

<p>As for the career advice find people doing these jobs and ask them what their day is like. That will tell you what you're likely to learn in those roles.</p>

CC BY-SA 4.0
2020-02-16T18:50:05.137Z
2020-02-16T18:50:05.137Z
candied_orange
<p>Yes you need to start at the bottom. Find somewhere where you will get good experience. Also practice at home. Do coding katas, use revision control, practice test-driven-development, use <a href="https://en.wikipedia.org/wiki/Transformation_Priority_Premise" rel="nofollow noreferrer">transformation priority</a>, study functional programming, learn the history of programming (much of the best stuff was invented in the 1960s), study user interaction design. (just don't do it all at the same time, you have a life-time to do it in.)</p>

<p>However note that most developers have less that 5 years experience, because of exponential (this word is being used correctly here) growth in number of developers, with a doubling rate of 5 years. Therefore you should expect to change to a more senior role soon.  </p>

CC BY-SA 4.0
2020-02-15T11:46:57.867Z
2020-02-15T11:46:57.867Z
ctrl-alt-delor
<p>I am sorry if this is not the right place to ask this, but I would really like to know.</p>

<p>I have finished a computer programming bootcamp and found I took to programming deeply. Some of my course mates have found jobs which are not 'junior developer' jobs (i.e. jobs which focus heavily on feature building, rather than on QA, etc...).</p>

<p>I would like to take the course of maximum learning, so is doing a typical junior developer job an important stepping stone on the way to being a great developer? The bootcamp did not teach TDD, so perhaps a 'junior' pathway is a sensible one.</p>

<p>Thank you for any thoughts.</p>

CC BY-SA 4.0
2020-02-15T11:41:17.683Z
I did not grok what you said your class mates new jobs were.
ctrl-alt-delor
CC BY-SA 4.0
2020-02-15T11:49:23.417Z
While this question is not about teaching, it is about learning. I think it therefore should be **left open**.
ctrl-alt-delor
CC BY-SA 4.0
2020-02-15T12:56:50.877Z
Actually it is about taking a certain kind of job. There are other sites here focused on that.
Buffy
CC BY-SA 4.0
2020-02-15T15:01:43.670Z
I agree with @Buffy that this seems like career advice more than education advice, but I won't close it unilaterally without more input.
Ben I.
<careers>
Should I start out as a “junior developer”?
# Should I start out as a “junior developer”?

(Asked by: username_0 on 2020-02-15)

I am sorry if this is not the right place to ask this, but I would really like to know.

I have finished a computer programming bootcamp and found I took to programming deeply. Some of my course mates have found jobs which are not 'junior developer' jobs (i.e. jobs which focus heavily on feature building, rather than on QA, etc...).

I would like to take the course of maximum learning, so is doing a typical junior developer job an important stepping stone on the way to being a great developer? The bootcamp did not teach TDD, so perhaps a 'junior' pathway is a sensible one.

Thank you for any thoughts.

**Tags:** careers

> **Comments:**
> **username_1**: I did not grok what you said your class mates new jobs were.  
> **username_1**: While this question is not about teaching, it is about learning. I think it therefore should be **left open**.  
> **username_2**: Actually it is about taking a certain kind of job. There are other sites here focused on that.  
> **username_3**: I agree with @username_2 that this seems like career advice more than education advice, but I won't close it unilaterally without more input.  

---

## 2 answers

### Answer by username_4 on 2020-02-16. Score: 2

Feature building is a junior developer job. It's also a senior developer job. Feature building is part of any developers job.

QA is testing of those features. If you become a QA specialist you won't be developing features at all. You also won't be using TDD. TDD comes before the code under test. Not after.

QA testers come in two types: [manual testers](https://sqa.stackexchange.com/a/27737/17901) and [automation testers](https://en.wikipedia.org/wiki/Test_automation). Automation testers are often feature developers as well.

If someones convinced you that newbies must start in QA they've feeding you crap and I wouldn't want to work there.

Some shops don't even have QA roles because the developers test the crap out of their own stuff and then hand it to a peer to test it again with fresh eyes. Some do all that and then still hand it to a QA group who spend all day doing nothing but gleefully breaking software.

QA is a speciality in and of itself. It's a mindset as much as it's ever a job title.

But QA is not where newbies need to start and it's not a dumping ground for sub par developers. QA is where you put your best or it's not QA.

At the end of the day, a junior developer is just someone who might learn a thing or two from a senior developer.

As for the career advice find people doing these jobs and ask them what their day is like. That will tell you what you're likely to learn in those roles.


---

### Answer by username_1 on 2020-02-15. Score: 1

Yes you need to start at the bottom. Find somewhere where you will get good experience. Also practice at home. Do coding katas, use revision control, practice test-driven-development, use [transformation priority](https://en.wikipedia.org/wiki/Transformation_Priority_Premise), study functional programming, learn the history of programming (much of the best stuff was invented in the 1960s), study user interaction design. (just don't do it all at the same time, you have a life-time to do it in.)

However note that most developers have less that 5 years experience, because of exponential (this word is being used correctly here) growth in number of developers, with a doubling rate of 5 years. Therefore you should expect to change to a more senior role soon.


---

