I worked in industry for 1.5 years before going to grad school. I want to drop out - should I be applying for...
I found it very frustrating to notice in my job search that pretty much all the positions are either looking for senior developers with +3-4 years experience or (much more rarely) completely entry-level people / fresh graduates.
I'm neither. I can definitely generate more value to the company than a fresh graduate, having been exposed to a number of different technologies and having had some experience operating in a corporate setting. On the other hand I'm confident I can pick up new technologies quickly but I'm not able to offer deep expertise in any particular useful specialism, as my work up to this point had been rather broad / on proprietary platforms.
And so, in general, is it better to apply for graduate schemes / entry level positions and then hope they will see my added value or is it better to apply for senior positions and underwhelm slightly with the hope of being offered a lower-seniority position?
job-search applications seniority
edited Dec 2 '18 at 20:02
Kilisi
112k61248433
asked Dec 2 '18 at 15:54
KubaFYI
1406
add a comment |
I found it very frustrating to notice in my job search that pretty much all the positions are either looking for senior developers with +3-4 years experience or (much more rarely) completely entry-level people / fresh graduates.
I'm neither. I can definitely generate more value to the company than a fresh graduate, having been exposed to a number of different technologies and having had some experience operating in a corporate setting. On the other hand I'm confident I can pick up new technologies quickly but I'm not able to offer deep expertise in any particular useful specialism, as my work up to this point had been rather broad / on proprietary platforms.
And so, in general, is it better to apply for graduate schemes / entry level positions and then hope they will see my added value or is it better to apply for senior positions and underwhelm slightly with the hope of being offered a lower-seniority position?
job-search applications seniority
edited Dec 2 '18 at 20:02
Kilisi
112k61248433
asked Dec 2 '18 at 15:54
KubaFYI
1406
add a comment |
I found it very frustrating to notice in my job search that pretty much all the positions are either looking for senior developers with +3-4 years experience or (much more rarely) completely entry-level people / fresh graduates.
I'm neither. I can definitely generate more value to the company than a fresh graduate, having been exposed to a number of different technologies and having had some experience operating in a corporate setting. On the other hand I'm confident I can pick up new technologies quickly but I'm not able to offer deep expertise in any particular useful specialism, as my work up to this point had been rather broad / on proprietary platforms.
And so, in general, is it better to apply for graduate schemes / entry level positions and then hope they will see my added value or is it better to apply for senior positions and underwhelm slightly with the hope of being offered a lower-seniority position?
job-search applications seniority
edited Dec 2 '18 at 20:02
Kilisi
112k61248433
asked Dec 2 '18 at 15:54
KubaFYI
1406
I found it very frustrating to notice in my job search that pretty much all the positions are either looking for senior developers with +3-4 years experience or (much more rarely) completely entry-level people / fresh graduates.
I'm neither. I can definitely generate more value to the company than a fresh graduate, having been exposed to a number of different technologies and having had some experience operating in a corporate setting. On the other hand I'm confident I can pick up new technologies quickly but I'm not able to offer deep expertise in any particular useful specialism, as my work up to this point had been rather broad / on proprietary platforms.
And so, in general, is it better to apply for graduate schemes / entry level positions and then hope they will see my added value or is it better to apply for senior positions and underwhelm slightly with the hope of being offered a lower-seniority position?
job-search applications seniority
job-search applications seniority
edited Dec 2 '18 at 20:02
Kilisi
112k61248433
asked Dec 2 '18 at 15:54
KubaFYI
1406
edited Dec 2 '18 at 20:02
Kilisi
112k61248433
asked Dec 2 '18 at 15:54
KubaFYI
1406
edited Dec 2 '18 at 20:02
Kilisi
112k61248433
edited Dec 2 '18 at 20:02
Kilisi
112k61248433
edited Dec 2 '18 at 20:02
Kilisi
112k61248433
112k61248433
asked Dec 2 '18 at 15:54
KubaFYI
1406
asked Dec 2 '18 at 15:54
KubaFYI
1406
asked Dec 2 '18 at 15:54
KubaFYI
1406
1406
add a comment |
add a comment |
5 Answers
5
active
oldest
votes
I would go for entry level, if you add value you should progress quickly and impress while learning. If you aim too high and land a job you're not going to be good at you will get a bad reputation or mediocre one.
It's always better to start strong so you can build and keep momentum.
answered Dec 2 '18 at 16:19
Kilisi
112k61248433
add a comment |
Junior. Because you ARE a junior. Juniors, broadly speaking, are people with roughly anything under 3 years experience. That's just how it is in the broadest, most generalized terms. That's not to say you'll stay there. But in the broadest terms you're a junior. Get the job, impress, and get promoted. If you're providing the value you claim you can, you'll be promoted very quickly. Also, it keeps expectations in check and allows you room to grow into the company. On top of that, broad knowledge is essentially what junior developers have. They can do a lot of things on a shallow surface level. Depending on the organization, tech stack and whatever unknown unknown, you may want to be cautious. It's very easy to get in over your head. I say take junior, impress and move up.
answered Dec 3 '18 at 13:22
ShinEmperor
1,51029
add a comment |
It's impossible to answer your question without knowing what your skills are, where you worked and what positions you are considering.
To give you an example, if you spent 1.5 years at Google and are now applying for a job in the same field at a small local startup, go for a senior role (provided you learnt something of course).
If you spent 1.5 years at a local startup but are now applying for a job at Google, go for a junior position.
The decision to apply for a junior or senior position should also depend on
- your ability to learn quickly and
- your ability to sell yourself. To give you an example, during my last job search I was offered several senior positions in a field I'd never worked in since people treated my previous job experience as somehow related.
answered Dec 2 '18 at 18:41
BigMadAndy
11k82155
add a comment |
It depends.
But you should A) take inventory for your skills, B) match it to the requirements of the jobs you are shooting for, and C) continue applying as long as you fulfil around 70% of the requirements. If you have less than required experience, you will need to either demonstrate proficiency, or find a hiring manager who will open a more junior role for you.
answered Dec 2 '18 at 22:08
Monoandale
3,22352055
add a comment |
Apply for whichever jobs strike you as more interesting. Some employers will have a literal hard requirement for years worked, others use it only as a guide - often with soft language, i.e. it'll say "3+ years experience or equivalent." Some in both of those categories would include your grad studies as experience, so it's a wash.
Regardless, you should recognize that the application is only getting your foot in the door. It's the first step. Regardless of which positions you apply for, be ready to answer questions about your history:
- Why did you work for 1.5 years and then go back to school?
- Why are you now dropping out, prior to completing your program?
answered Dec 3 '18 at 13:16
dwizum
11.7k52744
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "423"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
noCode: true, onDemand: false,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f123845%2fi-worked-in-industry-for-1-5-years-before-going-to-grad-school-i-want-to-drop-o%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
StackExchange.ready(function () {
$("#show-editor-button input, #show-editor-button button").click(function () {
var showEditor = function() {
$("#show-editor-button").hide();
$("#post-form").removeClass("dno");
StackExchange.editor.finallyInit();
};
var useFancy = $(this).data('confirm-use-fancy');
if(useFancy == 'True') {
var popupTitle = $(this).data('confirm-fancy-title');
var popupBody = $(this).data('confirm-fancy-body');
var popupAccept = $(this).data('confirm-fancy-accept-button');
$(this).loadPopup({
url: '/post/self-answer-popup',
loaded: function(popup) {
var pTitle = $(popup).find('h2');
var pBody = $(popup).find('.popup-body');
var pSubmit = $(popup).find('.popup-submit');
pTitle.text(popupTitle);
pBody.html(popupBody);
pSubmit.val(popupAccept).click(showEditor);
}
})
} else{
var confirmText = $(this).data('confirm-text');
if (confirmText ? confirm(confirmText) : true) {
showEditor();
}
}
});
});
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
I would go for entry level, if you add value you should progress quickly and impress while learning. If you aim too high and land a job you're not going to be good at you will get a bad reputation or mediocre one.
It's always better to start strong so you can build and keep momentum.
answered Dec 2 '18 at 16:19
Kilisi
112k61248433
add a comment |
I would go for entry level, if you add value you should progress quickly and impress while learning. If you aim too high and land a job you're not going to be good at you will get a bad reputation or mediocre one.
It's always better to start strong so you can build and keep momentum.
answered Dec 2 '18 at 16:19
Kilisi
112k61248433
add a comment |
I would go for entry level, if you add value you should progress quickly and impress while learning. If you aim too high and land a job you're not going to be good at you will get a bad reputation or mediocre one.
It's always better to start strong so you can build and keep momentum.
answered Dec 2 '18 at 16:19
Kilisi
112k61248433
I would go for entry level, if you add value you should progress quickly and impress while learning. If you aim too high and land a job you're not going to be good at you will get a bad reputation or mediocre one.
It's always better to start strong so you can build and keep momentum.
answered Dec 2 '18 at 16:19
Kilisi
112k61248433
answered Dec 2 '18 at 16:19
Kilisi
112k61248433
answered Dec 2 '18 at 16:19
Kilisi
112k61248433
answered Dec 2 '18 at 16:19
Kilisi
112k61248433
112k61248433
add a comment |
add a comment |
Junior. Because you ARE a junior. Juniors, broadly speaking, are people with roughly anything under 3 years experience. That's just how it is in the broadest, most generalized terms. That's not to say you'll stay there. But in the broadest terms you're a junior. Get the job, impress, and get promoted. If you're providing the value you claim you can, you'll be promoted very quickly. Also, it keeps expectations in check and allows you room to grow into the company. On top of that, broad knowledge is essentially what junior developers have. They can do a lot of things on a shallow surface level. Depending on the organization, tech stack and whatever unknown unknown, you may want to be cautious. It's very easy to get in over your head. I say take junior, impress and move up.
answered Dec 3 '18 at 13:22
ShinEmperor
1,51029
add a comment |
Junior. Because you ARE a junior. Juniors, broadly speaking, are people with roughly anything under 3 years experience. That's just how it is in the broadest, most generalized terms. That's not to say you'll stay there. But in the broadest terms you're a junior. Get the job, impress, and get promoted. If you're providing the value you claim you can, you'll be promoted very quickly. Also, it keeps expectations in check and allows you room to grow into the company. On top of that, broad knowledge is essentially what junior developers have. They can do a lot of things on a shallow surface level. Depending on the organization, tech stack and whatever unknown unknown, you may want to be cautious. It's very easy to get in over your head. I say take junior, impress and move up.
answered Dec 3 '18 at 13:22
ShinEmperor
1,51029
add a comment |
Junior. Because you ARE a junior. Juniors, broadly speaking, are people with roughly anything under 3 years experience. That's just how it is in the broadest, most generalized terms. That's not to say you'll stay there. But in the broadest terms you're a junior. Get the job, impress, and get promoted. If you're providing the value you claim you can, you'll be promoted very quickly. Also, it keeps expectations in check and allows you room to grow into the company. On top of that, broad knowledge is essentially what junior developers have. They can do a lot of things on a shallow surface level. Depending on the organization, tech stack and whatever unknown unknown, you may want to be cautious. It's very easy to get in over your head. I say take junior, impress and move up.
answered Dec 3 '18 at 13:22
ShinEmperor
1,51029
Junior. Because you ARE a junior. Juniors, broadly speaking, are people with roughly anything under 3 years experience. That's just how it is in the broadest, most generalized terms. That's not to say you'll stay there. But in the broadest terms you're a junior. Get the job, impress, and get promoted. If you're providing the value you claim you can, you'll be promoted very quickly. Also, it keeps expectations in check and allows you room to grow into the company. On top of that, broad knowledge is essentially what junior developers have. They can do a lot of things on a shallow surface level. Depending on the organization, tech stack and whatever unknown unknown, you may want to be cautious. It's very easy to get in over your head. I say take junior, impress and move up.
answered Dec 3 '18 at 13:22
ShinEmperor
1,51029
answered Dec 3 '18 at 13:22
ShinEmperor
1,51029
answered Dec 3 '18 at 13:22
ShinEmperor
1,51029
answered Dec 3 '18 at 13:22
ShinEmperor
1,51029
1,51029
add a comment |
add a comment |
It's impossible to answer your question without knowing what your skills are, where you worked and what positions you are considering.
To give you an example, if you spent 1.5 years at Google and are now applying for a job in the same field at a small local startup, go for a senior role (provided you learnt something of course).
If you spent 1.5 years at a local startup but are now applying for a job at Google, go for a junior position.
The decision to apply for a junior or senior position should also depend on
- your ability to learn quickly and
- your ability to sell yourself. To give you an example, during my last job search I was offered several senior positions in a field I'd never worked in since people treated my previous job experience as somehow related.
answered Dec 2 '18 at 18:41
BigMadAndy
11k82155
add a comment |
It's impossible to answer your question without knowing what your skills are, where you worked and what positions you are considering.
To give you an example, if you spent 1.5 years at Google and are now applying for a job in the same field at a small local startup, go for a senior role (provided you learnt something of course).
If you spent 1.5 years at a local startup but are now applying for a job at Google, go for a junior position.
The decision to apply for a junior or senior position should also depend on
- your ability to learn quickly and
- your ability to sell yourself. To give you an example, during my last job search I was offered several senior positions in a field I'd never worked in since people treated my previous job experience as somehow related.
answered Dec 2 '18 at 18:41
BigMadAndy
11k82155
add a comment |
It's impossible to answer your question without knowing what your skills are, where you worked and what positions you are considering.
To give you an example, if you spent 1.5 years at Google and are now applying for a job in the same field at a small local startup, go for a senior role (provided you learnt something of course).
If you spent 1.5 years at a local startup but are now applying for a job at Google, go for a junior position.
The decision to apply for a junior or senior position should also depend on
- your ability to learn quickly and
- your ability to sell yourself. To give you an example, during my last job search I was offered several senior positions in a field I'd never worked in since people treated my previous job experience as somehow related.
answered Dec 2 '18 at 18:41
BigMadAndy
11k82155
It's impossible to answer your question without knowing what your skills are, where you worked and what positions you are considering.
To give you an example, if you spent 1.5 years at Google and are now applying for a job in the same field at a small local startup, go for a senior role (provided you learnt something of course).
If you spent 1.5 years at a local startup but are now applying for a job at Google, go for a junior position.
The decision to apply for a junior or senior position should also depend on
- your ability to learn quickly and
- your ability to sell yourself. To give you an example, during my last job search I was offered several senior positions in a field I'd never worked in since people treated my previous job experience as somehow related.
answered Dec 2 '18 at 18:41
BigMadAndy
11k82155
answered Dec 2 '18 at 18:41
BigMadAndy
11k82155
answered Dec 2 '18 at 18:41
BigMadAndy
11k82155
answered Dec 2 '18 at 18:41
BigMadAndy
11k82155
11k82155
add a comment |
add a comment |
It depends.
But you should A) take inventory for your skills, B) match it to the requirements of the jobs you are shooting for, and C) continue applying as long as you fulfil around 70% of the requirements. If you have less than required experience, you will need to either demonstrate proficiency, or find a hiring manager who will open a more junior role for you.
answered Dec 2 '18 at 22:08
Monoandale
3,22352055
add a comment |
It depends.
But you should A) take inventory for your skills, B) match it to the requirements of the jobs you are shooting for, and C) continue applying as long as you fulfil around 70% of the requirements. If you have less than required experience, you will need to either demonstrate proficiency, or find a hiring manager who will open a more junior role for you.
answered Dec 2 '18 at 22:08
Monoandale
3,22352055
add a comment |
It depends.
But you should A) take inventory for your skills, B) match it to the requirements of the jobs you are shooting for, and C) continue applying as long as you fulfil around 70% of the requirements. If you have less than required experience, you will need to either demonstrate proficiency, or find a hiring manager who will open a more junior role for you.
answered Dec 2 '18 at 22:08
Monoandale
3,22352055
It depends.
But you should A) take inventory for your skills, B) match it to the requirements of the jobs you are shooting for, and C) continue applying as long as you fulfil around 70% of the requirements. If you have less than required experience, you will need to either demonstrate proficiency, or find a hiring manager who will open a more junior role for you.
answered Dec 2 '18 at 22:08
Monoandale
3,22352055
answered Dec 2 '18 at 22:08
Monoandale
3,22352055
answered Dec 2 '18 at 22:08
Monoandale
3,22352055
answered Dec 2 '18 at 22:08
Monoandale
3,22352055
3,22352055
add a comment |
add a comment |
Apply for whichever jobs strike you as more interesting. Some employers will have a literal hard requirement for years worked, others use it only as a guide - often with soft language, i.e. it'll say "3+ years experience or equivalent." Some in both of those categories would include your grad studies as experience, so it's a wash.
Regardless, you should recognize that the application is only getting your foot in the door. It's the first step. Regardless of which positions you apply for, be ready to answer questions about your history:
- Why did you work for 1.5 years and then go back to school?
- Why are you now dropping out, prior to completing your program?
answered Dec 3 '18 at 13:16
dwizum
11.7k52744
add a comment |
Apply for whichever jobs strike you as more interesting. Some employers will have a literal hard requirement for years worked, others use it only as a guide - often with soft language, i.e. it'll say "3+ years experience or equivalent." Some in both of those categories would include your grad studies as experience, so it's a wash.
Regardless, you should recognize that the application is only getting your foot in the door. It's the first step. Regardless of which positions you apply for, be ready to answer questions about your history:
- Why did you work for 1.5 years and then go back to school?
- Why are you now dropping out, prior to completing your program?
answered Dec 3 '18 at 13:16
dwizum
11.7k52744
add a comment |
Apply for whichever jobs strike you as more interesting. Some employers will have a literal hard requirement for years worked, others use it only as a guide - often with soft language, i.e. it'll say "3+ years experience or equivalent." Some in both of those categories would include your grad studies as experience, so it's a wash.
Regardless, you should recognize that the application is only getting your foot in the door. It's the first step. Regardless of which positions you apply for, be ready to answer questions about your history:
- Why did you work for 1.5 years and then go back to school?
- Why are you now dropping out, prior to completing your program?
answered Dec 3 '18 at 13:16
dwizum
11.7k52744
Apply for whichever jobs strike you as more interesting. Some employers will have a literal hard requirement for years worked, others use it only as a guide - often with soft language, i.e. it'll say "3+ years experience or equivalent." Some in both of those categories would include your grad studies as experience, so it's a wash.
Regardless, you should recognize that the application is only getting your foot in the door. It's the first step. Regardless of which positions you apply for, be ready to answer questions about your history:
- Why did you work for 1.5 years and then go back to school?
- Why are you now dropping out, prior to completing your program?
answered Dec 3 '18 at 13:16
dwizum
11.7k52744
answered Dec 3 '18 at 13:16
dwizum
11.7k52744
answered Dec 3 '18 at 13:16
dwizum
11.7k52744
answered Dec 3 '18 at 13:16
dwizum
11.7k52744
11.7k52744
add a comment |
add a comment |
Thanks for contributing an answer to The Workplace Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f123845%2fi-worked-in-industry-for-1-5-years-before-going-to-grad-school-i-want-to-drop-o%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
