4 ms·

It sounds like you werent given the space and time to learn as a junior dev on a project that needed seniors. I'd recommend making some commits to open source t

It sounds like you werent given the space and time to learn as a junior dev on a project that needed seniors. I'd recommend making some commits to open source to publically demo your skills which will prove youve learnt from early mistakes and show a commitment to learning new things.

brailsafe 9y ago
Good suggestion and you're probably right. At least in terms of JavaScript programming expertise in 2014. Looking back, I did have the skills in other areas but was perhaps overconfident about my JS programming skill. Since then I've developed more humility. My github is here https://github.com/LukeTully https://github.com/LukeTully. Whenever I'm using something that isn't working like it should, I try to find a way to contribute. I could definitely be more proactive about looking for contributions to make.
- godot 9y ago
  Just going by how you talk about the tech stack you work on and a brief look at your Github, my opinion is that you should have the qualifications needed to land a job at the Software Engineer level. Going off the tangents a little bit, I think as an industry we're going through a phrase where we're having a whole new influx of qualified candidates and we're being overly picky in hiring. A bit of anecdotal points -- I went through a job search earlier this year after my startup went through a shutdown. I have 10 years of industry experience at this point and have done well in all of it, having moved up in a big company from SE to Architect in 6 years, and then as CTO of my startup. I had a surprisingly difficult time landing an offer during my job search. After I did, and started at a company, I quickly also began interviewing new candidates for the company as well. This time from the other side's perspective, I found us to be surprisingly critical when selecting candidates. We have a ton of candidates coming from programs like Hack Reactor and other similar ones, who all have good working knowledge of our stack (the most common one out there now -- Node, React), but we're being almost overly selective in choosing who to take in. Many of the candidates who we rejected, though junior level, actually did relatively well in their interviews to the level where, 7 years ago at my last big company, I would've hired them when I interviewed them there. I have a completely unproven and unbacked up theory that programs like Hack Reactor and others are giving us a massive influx of new qualified candidates now, and every company is seeing it, and suddenly every employer has intentionally or unintentionally raised their expectations in hiring because the supply allowed them to be a lot more selective. This is a bit of a counter-point to the general consensus that there's always huge demand for tech talent and not enough supply.
  - brailsafe 9y ago
    That's kind of you to say. Your story probably touches on a reality that myself and likely many others aren't really thinking about or taking seriously enough. In my—albeit very limited—experience talking to codecamp graduates, my impression is that the specific skills are taught for the React+Node stack, adding to the talent pool, but then the knowledge doesn't go very deep. I don't know how well those programs prepare people for generalized problem solving on the web. Reminds me of when some of my friends only learned jQuery. Granted, I probably wouldn't expect that from a focussed program either. What skills did you end up selecting for and how have those hires turned out?

brailsafe 9y ago

Good suggestion and you're probably right. At least in terms of JavaScript programming expertise in 2014. Looking back, I did have the skills in other areas but was perhaps overconfident about my JS programming skill. Since then I've developed more humility. My github is here https://github.com/LukeTully https://github.com/LukeTully. Whenever I'm using something that isn't working like it should, I try to find a way to contribute. I could definitely be more proactive about looking for contributions to make.

godot 9y ago
Just going by how you talk about the tech stack you work on and a brief look at your Github, my opinion is that you should have the qualifications needed to land a job at the Software Engineer level. Going off the tangents a little bit, I think as an industry we're going through a phrase where we're having a whole new influx of qualified candidates and we're being overly picky in hiring. A bit of anecdotal points -- I went through a job search earlier this year after my startup went through a shutdown. I have 10 years of industry experience at this point and have done well in all of it, having moved up in a big company from SE to Architect in 6 years, and then as CTO of my startup. I had a surprisingly difficult time landing an offer during my job search. After I did, and started at a company, I quickly also began interviewing new candidates for the company as well. This time from the other side's perspective, I found us to be surprisingly critical when selecting candidates. We have a ton of candidates coming from programs like Hack Reactor and other similar ones, who all have good working knowledge of our stack (the most common one out there now -- Node, React), but we're being almost overly selective in choosing who to take in. Many of the candidates who we rejected, though junior level, actually did relatively well in their interviews to the level where, 7 years ago at my last big company, I would've hired them when I interviewed them there. I have a completely unproven and unbacked up theory that programs like Hack Reactor and others are giving us a massive influx of new qualified candidates now, and every company is seeing it, and suddenly every employer has intentionally or unintentionally raised their expectations in hiring because the supply allowed them to be a lot more selective. This is a bit of a counter-point to the general consensus that there's always huge demand for tech talent and not enough supply.
- brailsafe 9y ago
  That's kind of you to say. Your story probably touches on a reality that myself and likely many others aren't really thinking about or taking seriously enough. In my—albeit very limited—experience talking to codecamp graduates, my impression is that the specific skills are taught for the React+Node stack, adding to the talent pool, but then the knowledge doesn't go very deep. I don't know how well those programs prepare people for generalized problem solving on the web. Reminds me of when some of my friends only learned jQuery. Granted, I probably wouldn't expect that from a focussed program either. What skills did you end up selecting for and how have those hires turned out?