Mixing
Building a portfolio/developing skills vs sending a job application now
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
0
down vote
favorite
I'm looking at moving into a different technology set (Ruby on Rails) than I'm using in my current job while also using some of the technology set I am using my current job (AngularJS).
To do this, I have to work on my portfolio, which is a website, in the weekends.
Progress developing my skill set is going slower than I'd like. I don't always have time (or the priority, I also like exercising and spending time with friends on my weekends) to work on the weekend. For example currently I've got stuck at understanding the Rails asset pipeline, which means I can't showcase the Angular skills which I'm already familiar with.
The dilemma I'm facing is, if I see a job that I'm interested in (a Rails job), I can apply now and either omit my portfolio, or explain that I'm only learning. I'm concerned that this would reflect badly on myself.
On the other hand, I could defer applying until the portfolio looks good, and then apply then.
How is either option likely to be perceived by a potential employer?
software-industry job-search
edited Oct 22 '15 at 3:56
Dawny33
12.2k34563
asked Oct 22 '15 at 1:22
dwjohnston
937515
suggest improvements |Â
up vote
0
down vote
favorite
I'm looking at moving into a different technology set (Ruby on Rails) than I'm using in my current job while also using some of the technology set I am using my current job (AngularJS).
To do this, I have to work on my portfolio, which is a website, in the weekends.
Progress developing my skill set is going slower than I'd like. I don't always have time (or the priority, I also like exercising and spending time with friends on my weekends) to work on the weekend. For example currently I've got stuck at understanding the Rails asset pipeline, which means I can't showcase the Angular skills which I'm already familiar with.
The dilemma I'm facing is, if I see a job that I'm interested in (a Rails job), I can apply now and either omit my portfolio, or explain that I'm only learning. I'm concerned that this would reflect badly on myself.
On the other hand, I could defer applying until the portfolio looks good, and then apply then.
How is either option likely to be perceived by a potential employer?
software-industry job-search
edited Oct 22 '15 at 3:56
Dawny33
12.2k34563
asked Oct 22 '15 at 1:22
dwjohnston
937515
1
Related: workplace.stackexchange.com/questions/41824/…
– Jane S♦
Oct 22 '15 at 1:35
3
1) You will not exhaust the supply of advertised jobs. 2) If you defer them they will be filled by others. Apply now, apply later, apply always.
– Nathan Cooper
Oct 22 '15 at 7:14
suggest improvements |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm looking at moving into a different technology set (Ruby on Rails) than I'm using in my current job while also using some of the technology set I am using my current job (AngularJS).
To do this, I have to work on my portfolio, which is a website, in the weekends.
Progress developing my skill set is going slower than I'd like. I don't always have time (or the priority, I also like exercising and spending time with friends on my weekends) to work on the weekend. For example currently I've got stuck at understanding the Rails asset pipeline, which means I can't showcase the Angular skills which I'm already familiar with.
The dilemma I'm facing is, if I see a job that I'm interested in (a Rails job), I can apply now and either omit my portfolio, or explain that I'm only learning. I'm concerned that this would reflect badly on myself.
On the other hand, I could defer applying until the portfolio looks good, and then apply then.
How is either option likely to be perceived by a potential employer?
software-industry job-search
edited Oct 22 '15 at 3:56
Dawny33
12.2k34563
asked Oct 22 '15 at 1:22
dwjohnston
937515
I'm looking at moving into a different technology set (Ruby on Rails) than I'm using in my current job while also using some of the technology set I am using my current job (AngularJS).
To do this, I have to work on my portfolio, which is a website, in the weekends.
Progress developing my skill set is going slower than I'd like. I don't always have time (or the priority, I also like exercising and spending time with friends on my weekends) to work on the weekend. For example currently I've got stuck at understanding the Rails asset pipeline, which means I can't showcase the Angular skills which I'm already familiar with.
The dilemma I'm facing is, if I see a job that I'm interested in (a Rails job), I can apply now and either omit my portfolio, or explain that I'm only learning. I'm concerned that this would reflect badly on myself.
On the other hand, I could defer applying until the portfolio looks good, and then apply then.
How is either option likely to be perceived by a potential employer?
software-industry job-search
edited Oct 22 '15 at 3:56
Dawny33
12.2k34563
asked Oct 22 '15 at 1:22
dwjohnston
937515
edited Oct 22 '15 at 3:56
Dawny33
12.2k34563
edited Oct 22 '15 at 3:56
Dawny33
12.2k34563
edited Oct 22 '15 at 3:56
Dawny33
12.2k34563
12.2k34563
asked Oct 22 '15 at 1:22
dwjohnston
937515
asked Oct 22 '15 at 1:22
dwjohnston
937515
asked Oct 22 '15 at 1:22
dwjohnston
937515
937515
1
Related: workplace.stackexchange.com/questions/41824/…
– Jane S♦
Oct 22 '15 at 1:35
3
1) You will not exhaust the supply of advertised jobs. 2) If you defer them they will be filled by others. Apply now, apply later, apply always.
– Nathan Cooper
Oct 22 '15 at 7:14
suggest improvements |Â
1
Related: workplace.stackexchange.com/questions/41824/…
– Jane S♦
Oct 22 '15 at 1:35
3
1) You will not exhaust the supply of advertised jobs. 2) If you defer them they will be filled by others. Apply now, apply later, apply always.
– Nathan Cooper
Oct 22 '15 at 7:14
1
1
Related: workplace.stackexchange.com/questions/41824/…
– Jane S♦
Oct 22 '15 at 1:35
Related: workplace.stackexchange.com/questions/41824/…
– Jane S♦
Oct 22 '15 at 1:35
3
3
1) You will not exhaust the supply of advertised jobs. 2) If you defer them they will be filled by others. Apply now, apply later, apply always.
– Nathan Cooper
Oct 22 '15 at 7:14
1) You will not exhaust the supply of advertised jobs. 2) If you defer them they will be filled by others. Apply now, apply later, apply always.
– Nathan Cooper
Oct 22 '15 at 7:14
suggest improvements |Â
2 Answers
2
active
oldest
votes
up vote
3
down vote
Companies generally are ok with taking people who are learning the requisite technologies and learning them fast, if they are passionate about that, and if they think the candidate would be a good fit for the role.
So, you can show them your learning process through projects. Show them the projects which you have done during your learning process, and be ready to explain clearly about them.
Projects are the only way of gauging your learning process when it comes to the software industry.
How is either option likely to be perceived by a potential
employer?
A potential employer, if given a choice would definitely prefer the candidate who already knows the skill. But, if they are to choose between two candidates who are learning the skill currently, they would definitely consider the one who is actively applying and validated his learning by doing projects/building something.
answered Oct 22 '15 at 3:55
Dawny33
12.2k34563
suggest improvements |Â
up vote
0
down vote
The dilemma I'm facing is, if I see a job that I'm interested in (a
Rails job), I can apply now and either omit my portfolio, or explain
that I'm only learning. I'm concerned that this would reflect badly on
myself.
On the other hand, I could defer applying until the portfolio looks
good, and then apply then.
Your best bet is to make your portfolio a priority, and get it into a viable state over the next few weeks.
Meanwhile, apply for whatever jobs interest you, and for which you feel you are qualified.
By the time an interview rolls around, you'll be ready to talk about your expertise, and show off the results of your concentrated efforts.
Basically, you have to decide if you value the opportunity for a new job (and consequent preparation) more than exercising and spending time with friends on weekends for a few weeks, or not. You have the ability, you now need to decide if it's a priority.
How is either option likely to be perceived by a potential employer?
Some employers deem a portfolio as a critical attribute, others don't.
In my hiring, I seldom cared about a "portfolio". For the positions I was filling, the answers to my questions were far more important that projects the applicants chose to do in their spare time. I've always felt that work done at the behest of an employer, under time deadlines, was a far better predictor of future performance than a self-selected project done in the individual's spare time.
Your mileage may vary.
answered Oct 22 '15 at 12:09
Joe Strazzere
223k104653921
suggest improvements |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
Companies generally are ok with taking people who are learning the requisite technologies and learning them fast, if they are passionate about that, and if they think the candidate would be a good fit for the role.
So, you can show them your learning process through projects. Show them the projects which you have done during your learning process, and be ready to explain clearly about them.
Projects are the only way of gauging your learning process when it comes to the software industry.
How is either option likely to be perceived by a potential
employer?
A potential employer, if given a choice would definitely prefer the candidate who already knows the skill. But, if they are to choose between two candidates who are learning the skill currently, they would definitely consider the one who is actively applying and validated his learning by doing projects/building something.
answered Oct 22 '15 at 3:55
Dawny33
12.2k34563
suggest improvements |Â
up vote
3
down vote
Companies generally are ok with taking people who are learning the requisite technologies and learning them fast, if they are passionate about that, and if they think the candidate would be a good fit for the role.
So, you can show them your learning process through projects. Show them the projects which you have done during your learning process, and be ready to explain clearly about them.
Projects are the only way of gauging your learning process when it comes to the software industry.
How is either option likely to be perceived by a potential
employer?
A potential employer, if given a choice would definitely prefer the candidate who already knows the skill. But, if they are to choose between two candidates who are learning the skill currently, they would definitely consider the one who is actively applying and validated his learning by doing projects/building something.
answered Oct 22 '15 at 3:55
Dawny33
12.2k34563
suggest improvements |Â
up vote
3
down vote
up vote
3
down vote
Companies generally are ok with taking people who are learning the requisite technologies and learning them fast, if they are passionate about that, and if they think the candidate would be a good fit for the role.
So, you can show them your learning process through projects. Show them the projects which you have done during your learning process, and be ready to explain clearly about them.
Projects are the only way of gauging your learning process when it comes to the software industry.
How is either option likely to be perceived by a potential
employer?
A potential employer, if given a choice would definitely prefer the candidate who already knows the skill. But, if they are to choose between two candidates who are learning the skill currently, they would definitely consider the one who is actively applying and validated his learning by doing projects/building something.
answered Oct 22 '15 at 3:55
Dawny33
12.2k34563
Companies generally are ok with taking people who are learning the requisite technologies and learning them fast, if they are passionate about that, and if they think the candidate would be a good fit for the role.
So, you can show them your learning process through projects. Show them the projects which you have done during your learning process, and be ready to explain clearly about them.
Projects are the only way of gauging your learning process when it comes to the software industry.
How is either option likely to be perceived by a potential
employer?
A potential employer, if given a choice would definitely prefer the candidate who already knows the skill. But, if they are to choose between two candidates who are learning the skill currently, they would definitely consider the one who is actively applying and validated his learning by doing projects/building something.
answered Oct 22 '15 at 3:55
Dawny33
12.2k34563
answered Oct 22 '15 at 3:55
Dawny33
12.2k34563
answered Oct 22 '15 at 3:55
Dawny33
12.2k34563
answered Oct 22 '15 at 3:55
Dawny33
12.2k34563
12.2k34563
suggest improvements |Â
suggest improvements |Â
up vote
0
down vote
The dilemma I'm facing is, if I see a job that I'm interested in (a
Rails job), I can apply now and either omit my portfolio, or explain
that I'm only learning. I'm concerned that this would reflect badly on
myself.
On the other hand, I could defer applying until the portfolio looks
good, and then apply then.
Your best bet is to make your portfolio a priority, and get it into a viable state over the next few weeks.
Meanwhile, apply for whatever jobs interest you, and for which you feel you are qualified.
By the time an interview rolls around, you'll be ready to talk about your expertise, and show off the results of your concentrated efforts.
Basically, you have to decide if you value the opportunity for a new job (and consequent preparation) more than exercising and spending time with friends on weekends for a few weeks, or not. You have the ability, you now need to decide if it's a priority.
How is either option likely to be perceived by a potential employer?
Some employers deem a portfolio as a critical attribute, others don't.
In my hiring, I seldom cared about a "portfolio". For the positions I was filling, the answers to my questions were far more important that projects the applicants chose to do in their spare time. I've always felt that work done at the behest of an employer, under time deadlines, was a far better predictor of future performance than a self-selected project done in the individual's spare time.
Your mileage may vary.
answered Oct 22 '15 at 12:09
Joe Strazzere
223k104653921
suggest improvements |Â
up vote
0
down vote
The dilemma I'm facing is, if I see a job that I'm interested in (a
Rails job), I can apply now and either omit my portfolio, or explain
that I'm only learning. I'm concerned that this would reflect badly on
myself.
On the other hand, I could defer applying until the portfolio looks
good, and then apply then.
Your best bet is to make your portfolio a priority, and get it into a viable state over the next few weeks.
Meanwhile, apply for whatever jobs interest you, and for which you feel you are qualified.
By the time an interview rolls around, you'll be ready to talk about your expertise, and show off the results of your concentrated efforts.
Basically, you have to decide if you value the opportunity for a new job (and consequent preparation) more than exercising and spending time with friends on weekends for a few weeks, or not. You have the ability, you now need to decide if it's a priority.
How is either option likely to be perceived by a potential employer?
Some employers deem a portfolio as a critical attribute, others don't.
In my hiring, I seldom cared about a "portfolio". For the positions I was filling, the answers to my questions were far more important that projects the applicants chose to do in their spare time. I've always felt that work done at the behest of an employer, under time deadlines, was a far better predictor of future performance than a self-selected project done in the individual's spare time.
Your mileage may vary.
answered Oct 22 '15 at 12:09
Joe Strazzere
223k104653921
suggest improvements |Â
up vote
0
down vote
up vote
0
down vote
The dilemma I'm facing is, if I see a job that I'm interested in (a
Rails job), I can apply now and either omit my portfolio, or explain
that I'm only learning. I'm concerned that this would reflect badly on
myself.
On the other hand, I could defer applying until the portfolio looks
good, and then apply then.
Your best bet is to make your portfolio a priority, and get it into a viable state over the next few weeks.
Meanwhile, apply for whatever jobs interest you, and for which you feel you are qualified.
By the time an interview rolls around, you'll be ready to talk about your expertise, and show off the results of your concentrated efforts.
Basically, you have to decide if you value the opportunity for a new job (and consequent preparation) more than exercising and spending time with friends on weekends for a few weeks, or not. You have the ability, you now need to decide if it's a priority.
How is either option likely to be perceived by a potential employer?
Some employers deem a portfolio as a critical attribute, others don't.
In my hiring, I seldom cared about a "portfolio". For the positions I was filling, the answers to my questions were far more important that projects the applicants chose to do in their spare time. I've always felt that work done at the behest of an employer, under time deadlines, was a far better predictor of future performance than a self-selected project done in the individual's spare time.
Your mileage may vary.
answered Oct 22 '15 at 12:09
Joe Strazzere
223k104653921
The dilemma I'm facing is, if I see a job that I'm interested in (a
Rails job), I can apply now and either omit my portfolio, or explain
that I'm only learning. I'm concerned that this would reflect badly on
myself.
On the other hand, I could defer applying until the portfolio looks
good, and then apply then.
Your best bet is to make your portfolio a priority, and get it into a viable state over the next few weeks.
Meanwhile, apply for whatever jobs interest you, and for which you feel you are qualified.
By the time an interview rolls around, you'll be ready to talk about your expertise, and show off the results of your concentrated efforts.
Basically, you have to decide if you value the opportunity for a new job (and consequent preparation) more than exercising and spending time with friends on weekends for a few weeks, or not. You have the ability, you now need to decide if it's a priority.
How is either option likely to be perceived by a potential employer?
Some employers deem a portfolio as a critical attribute, others don't.
In my hiring, I seldom cared about a "portfolio". For the positions I was filling, the answers to my questions were far more important that projects the applicants chose to do in their spare time. I've always felt that work done at the behest of an employer, under time deadlines, was a far better predictor of future performance than a self-selected project done in the individual's spare time.
Your mileage may vary.
answered Oct 22 '15 at 12:09
Joe Strazzere
223k104653921
answered Oct 22 '15 at 12:09
Joe Strazzere
223k104653921
answered Oct 22 '15 at 12:09
Joe Strazzere
223k104653921
answered Oct 22 '15 at 12:09
Joe Strazzere
223k104653921
223k104653921
suggest improvements |Â
suggest improvements |Â
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
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f56350%2fbuilding-a-portfolio-developing-skills-vs-sending-a-job-application-now%23new-answer', 'question_page');
);
Post as a guest
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
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
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
1
Related: workplace.stackexchange.com/questions/41824/…
– Jane S♦
Oct 22 '15 at 1:35
3
1) You will not exhaust the supply of advertised jobs. 2) If you defer them they will be filled by others. Apply now, apply later, apply always.
– Nathan Cooper
Oct 22 '15 at 7:14