Am I a junior or senior front-end developer? [closed]
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
-1
down vote
favorite
I hope this is the right stackexchange site to this question... If not, please just vote to close.
My job position is something really new in the business field, before people like me was just called "web developer", but now a differentiation is necessary, because there's a specialization in specific fields of the web development.
I've worked professionally with HTML, CSS and JavaScript for about 5 years (starting from 2011). First using just vanilla JavaScript and jQuery, then, 2 years ago I've started with Node.js and for the past year I've heavily worked with front-end frameworks (mostly Ember.js).
In my specific field (HTML, JS and CSS) I think to have an extensive knowledge and usually I come up with a solution to any problem I face.
I'm just 23 tho, and everytime I sign a contract I get the "junior" title.
I know the informations I've provided are not a lot but I would like to understand if I'm a still a junior front-end developer or something else.
careers
closed as off-topic by Thomas Owens, Dawny33, Philip Kendall, Telastyn, paparazzo Dec 2 '15 at 16:07
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions seeking advice on company-specific regulations, agreements, or policies should be directed to your manager or HR department. Questions that address only a specific company or position are of limited use to future visitors. Questions seeking legal advice should be directed to legal professionals. For more information, click here." â Thomas Owens, Dawny33, Philip Kendall
suggest improvements |Â
up vote
-1
down vote
favorite
I hope this is the right stackexchange site to this question... If not, please just vote to close.
My job position is something really new in the business field, before people like me was just called "web developer", but now a differentiation is necessary, because there's a specialization in specific fields of the web development.
I've worked professionally with HTML, CSS and JavaScript for about 5 years (starting from 2011). First using just vanilla JavaScript and jQuery, then, 2 years ago I've started with Node.js and for the past year I've heavily worked with front-end frameworks (mostly Ember.js).
In my specific field (HTML, JS and CSS) I think to have an extensive knowledge and usually I come up with a solution to any problem I face.
I'm just 23 tho, and everytime I sign a contract I get the "junior" title.
I know the informations I've provided are not a lot but I would like to understand if I'm a still a junior front-end developer or something else.
careers
closed as off-topic by Thomas Owens, Dawny33, Philip Kendall, Telastyn, paparazzo Dec 2 '15 at 16:07
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions seeking advice on company-specific regulations, agreements, or policies should be directed to your manager or HR department. Questions that address only a specific company or position are of limited use to future visitors. Questions seeking legal advice should be directed to legal professionals. For more information, click here." â Thomas Owens, Dawny33, Philip Kendall
4
In the grand scheme of things, job titles are pretty meaningless - although some people get very attached to them. How long you have worked with something is different from how many year's professional experience you have. A junior developer is often someone who as 2 or 3 years' professional experience, but again, that can be fairly arbitrary. People who are hiring you are more interested in your skills than your previous job titles.
â Laconic Droid
Dec 2 '15 at 15:40
How is your experience in comparison to your colleagues who don't have the "junior" title?
â Brandin
Dec 2 '15 at 15:51
2
As I said, it varies from company to company, but Junior/Senior titles typically depend on number of years of professional experience rather than specific skill sets. Senior Developers are often expected to have other skills over and above technical proficiency that come from "years on the job".
â Laconic Droid
Dec 2 '15 at 15:51
1
When you find yourself answering more front end questions vs asking them you know you're closer to senior than junior. As far as titles being handed out, you need to ask if the position is looking for a junior or senior level front end designer. You're letting other people decide your fate, you should be deciding it.
â The Muffin Man
Dec 2 '15 at 19:33
How much guidance do you need? How much guidance do you give to others? Those are often the key distinctions between "ranks"... but for resume purposes strong examples of what you can do are far more useful than titles,
â keshlam
Dec 3 '15 at 2:00
suggest improvements |Â
up vote
-1
down vote
favorite
up vote
-1
down vote
favorite
I hope this is the right stackexchange site to this question... If not, please just vote to close.
My job position is something really new in the business field, before people like me was just called "web developer", but now a differentiation is necessary, because there's a specialization in specific fields of the web development.
I've worked professionally with HTML, CSS and JavaScript for about 5 years (starting from 2011). First using just vanilla JavaScript and jQuery, then, 2 years ago I've started with Node.js and for the past year I've heavily worked with front-end frameworks (mostly Ember.js).
In my specific field (HTML, JS and CSS) I think to have an extensive knowledge and usually I come up with a solution to any problem I face.
I'm just 23 tho, and everytime I sign a contract I get the "junior" title.
I know the informations I've provided are not a lot but I would like to understand if I'm a still a junior front-end developer or something else.
careers
I hope this is the right stackexchange site to this question... If not, please just vote to close.
My job position is something really new in the business field, before people like me was just called "web developer", but now a differentiation is necessary, because there's a specialization in specific fields of the web development.
I've worked professionally with HTML, CSS and JavaScript for about 5 years (starting from 2011). First using just vanilla JavaScript and jQuery, then, 2 years ago I've started with Node.js and for the past year I've heavily worked with front-end frameworks (mostly Ember.js).
In my specific field (HTML, JS and CSS) I think to have an extensive knowledge and usually I come up with a solution to any problem I face.
I'm just 23 tho, and everytime I sign a contract I get the "junior" title.
I know the informations I've provided are not a lot but I would like to understand if I'm a still a junior front-end developer or something else.
careers
edited Dec 2 '15 at 15:47
asked Dec 2 '15 at 15:33
Fez Vrasta
22116
22116
closed as off-topic by Thomas Owens, Dawny33, Philip Kendall, Telastyn, paparazzo Dec 2 '15 at 16:07
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions seeking advice on company-specific regulations, agreements, or policies should be directed to your manager or HR department. Questions that address only a specific company or position are of limited use to future visitors. Questions seeking legal advice should be directed to legal professionals. For more information, click here." â Thomas Owens, Dawny33, Philip Kendall
closed as off-topic by Thomas Owens, Dawny33, Philip Kendall, Telastyn, paparazzo Dec 2 '15 at 16:07
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions seeking advice on company-specific regulations, agreements, or policies should be directed to your manager or HR department. Questions that address only a specific company or position are of limited use to future visitors. Questions seeking legal advice should be directed to legal professionals. For more information, click here." â Thomas Owens, Dawny33, Philip Kendall
4
In the grand scheme of things, job titles are pretty meaningless - although some people get very attached to them. How long you have worked with something is different from how many year's professional experience you have. A junior developer is often someone who as 2 or 3 years' professional experience, but again, that can be fairly arbitrary. People who are hiring you are more interested in your skills than your previous job titles.
â Laconic Droid
Dec 2 '15 at 15:40
How is your experience in comparison to your colleagues who don't have the "junior" title?
â Brandin
Dec 2 '15 at 15:51
2
As I said, it varies from company to company, but Junior/Senior titles typically depend on number of years of professional experience rather than specific skill sets. Senior Developers are often expected to have other skills over and above technical proficiency that come from "years on the job".
â Laconic Droid
Dec 2 '15 at 15:51
1
When you find yourself answering more front end questions vs asking them you know you're closer to senior than junior. As far as titles being handed out, you need to ask if the position is looking for a junior or senior level front end designer. You're letting other people decide your fate, you should be deciding it.
â The Muffin Man
Dec 2 '15 at 19:33
How much guidance do you need? How much guidance do you give to others? Those are often the key distinctions between "ranks"... but for resume purposes strong examples of what you can do are far more useful than titles,
â keshlam
Dec 3 '15 at 2:00
suggest improvements |Â
4
In the grand scheme of things, job titles are pretty meaningless - although some people get very attached to them. How long you have worked with something is different from how many year's professional experience you have. A junior developer is often someone who as 2 or 3 years' professional experience, but again, that can be fairly arbitrary. People who are hiring you are more interested in your skills than your previous job titles.
â Laconic Droid
Dec 2 '15 at 15:40
How is your experience in comparison to your colleagues who don't have the "junior" title?
â Brandin
Dec 2 '15 at 15:51
2
As I said, it varies from company to company, but Junior/Senior titles typically depend on number of years of professional experience rather than specific skill sets. Senior Developers are often expected to have other skills over and above technical proficiency that come from "years on the job".
â Laconic Droid
Dec 2 '15 at 15:51
1
When you find yourself answering more front end questions vs asking them you know you're closer to senior than junior. As far as titles being handed out, you need to ask if the position is looking for a junior or senior level front end designer. You're letting other people decide your fate, you should be deciding it.
â The Muffin Man
Dec 2 '15 at 19:33
How much guidance do you need? How much guidance do you give to others? Those are often the key distinctions between "ranks"... but for resume purposes strong examples of what you can do are far more useful than titles,
â keshlam
Dec 3 '15 at 2:00
4
4
In the grand scheme of things, job titles are pretty meaningless - although some people get very attached to them. How long you have worked with something is different from how many year's professional experience you have. A junior developer is often someone who as 2 or 3 years' professional experience, but again, that can be fairly arbitrary. People who are hiring you are more interested in your skills than your previous job titles.
â Laconic Droid
Dec 2 '15 at 15:40
In the grand scheme of things, job titles are pretty meaningless - although some people get very attached to them. How long you have worked with something is different from how many year's professional experience you have. A junior developer is often someone who as 2 or 3 years' professional experience, but again, that can be fairly arbitrary. People who are hiring you are more interested in your skills than your previous job titles.
â Laconic Droid
Dec 2 '15 at 15:40
How is your experience in comparison to your colleagues who don't have the "junior" title?
â Brandin
Dec 2 '15 at 15:51
How is your experience in comparison to your colleagues who don't have the "junior" title?
â Brandin
Dec 2 '15 at 15:51
2
2
As I said, it varies from company to company, but Junior/Senior titles typically depend on number of years of professional experience rather than specific skill sets. Senior Developers are often expected to have other skills over and above technical proficiency that come from "years on the job".
â Laconic Droid
Dec 2 '15 at 15:51
As I said, it varies from company to company, but Junior/Senior titles typically depend on number of years of professional experience rather than specific skill sets. Senior Developers are often expected to have other skills over and above technical proficiency that come from "years on the job".
â Laconic Droid
Dec 2 '15 at 15:51
1
1
When you find yourself answering more front end questions vs asking them you know you're closer to senior than junior. As far as titles being handed out, you need to ask if the position is looking for a junior or senior level front end designer. You're letting other people decide your fate, you should be deciding it.
â The Muffin Man
Dec 2 '15 at 19:33
When you find yourself answering more front end questions vs asking them you know you're closer to senior than junior. As far as titles being handed out, you need to ask if the position is looking for a junior or senior level front end designer. You're letting other people decide your fate, you should be deciding it.
â The Muffin Man
Dec 2 '15 at 19:33
How much guidance do you need? How much guidance do you give to others? Those are often the key distinctions between "ranks"... but for resume purposes strong examples of what you can do are far more useful than titles,
â keshlam
Dec 3 '15 at 2:00
How much guidance do you need? How much guidance do you give to others? Those are often the key distinctions between "ranks"... but for resume purposes strong examples of what you can do are far more useful than titles,
â keshlam
Dec 3 '15 at 2:00
suggest improvements |Â
1 Answer
1
active
oldest
votes
up vote
6
down vote
A job title is not set in stone. It's not even standardized. You are what the company says you are. As everything else, you can negotiate that for your contract. In the end, it's meaningless though. It's just a given title.
You could found a company and call your developers "Senior Grandmaster of the Universe". You could still pay them peanuts and treat them badly. Look for a company that treats you well, your title is secondary at best.
suggest improvements |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
6
down vote
A job title is not set in stone. It's not even standardized. You are what the company says you are. As everything else, you can negotiate that for your contract. In the end, it's meaningless though. It's just a given title.
You could found a company and call your developers "Senior Grandmaster of the Universe". You could still pay them peanuts and treat them badly. Look for a company that treats you well, your title is secondary at best.
suggest improvements |Â
up vote
6
down vote
A job title is not set in stone. It's not even standardized. You are what the company says you are. As everything else, you can negotiate that for your contract. In the end, it's meaningless though. It's just a given title.
You could found a company and call your developers "Senior Grandmaster of the Universe". You could still pay them peanuts and treat them badly. Look for a company that treats you well, your title is secondary at best.
suggest improvements |Â
up vote
6
down vote
up vote
6
down vote
A job title is not set in stone. It's not even standardized. You are what the company says you are. As everything else, you can negotiate that for your contract. In the end, it's meaningless though. It's just a given title.
You could found a company and call your developers "Senior Grandmaster of the Universe". You could still pay them peanuts and treat them badly. Look for a company that treats you well, your title is secondary at best.
A job title is not set in stone. It's not even standardized. You are what the company says you are. As everything else, you can negotiate that for your contract. In the end, it's meaningless though. It's just a given title.
You could found a company and call your developers "Senior Grandmaster of the Universe". You could still pay them peanuts and treat them badly. Look for a company that treats you well, your title is secondary at best.
answered Dec 2 '15 at 16:03
nvoigt
42.6k18105147
42.6k18105147
suggest improvements |Â
suggest improvements |Â
4
In the grand scheme of things, job titles are pretty meaningless - although some people get very attached to them. How long you have worked with something is different from how many year's professional experience you have. A junior developer is often someone who as 2 or 3 years' professional experience, but again, that can be fairly arbitrary. People who are hiring you are more interested in your skills than your previous job titles.
â Laconic Droid
Dec 2 '15 at 15:40
How is your experience in comparison to your colleagues who don't have the "junior" title?
â Brandin
Dec 2 '15 at 15:51
2
As I said, it varies from company to company, but Junior/Senior titles typically depend on number of years of professional experience rather than specific skill sets. Senior Developers are often expected to have other skills over and above technical proficiency that come from "years on the job".
â Laconic Droid
Dec 2 '15 at 15:51
1
When you find yourself answering more front end questions vs asking them you know you're closer to senior than junior. As far as titles being handed out, you need to ask if the position is looking for a junior or senior level front end designer. You're letting other people decide your fate, you should be deciding it.
â The Muffin Man
Dec 2 '15 at 19:33
How much guidance do you need? How much guidance do you give to others? Those are often the key distinctions between "ranks"... but for resume purposes strong examples of what you can do are far more useful than titles,
â keshlam
Dec 3 '15 at 2:00