3 ms·
Investing in the Future: The Case for Hiring and Mentoring Junior Tech Talent
- tombert 3y agoAt a previous job, we hired a fair number of both junior and senior engineers. The job was doing F# and since most places don't do a ton of functional programming, I would try and get people up to speed in some of the more functional aspects of the language (how good I was at that is a matter of opinion). I always enjoyed teaching the junior engineers more, simply because they hadn't developed a lot of habits yet, and their brains were more plastic. Instead of trying to "write Java in F#", it was easier to just teach them idiomatic F#. Senior engineers were more annoying, because they were kind of "too good". Instead of making a real effort to try and learn the language and its quirks, they would instead just try and figure out ways to do their old imperative stuff in F# (e.g. using `mutable` everywhere, using classes for everything, relying on state instead of function arguments, not really utilizing monads, etc.). Most of them did eventually pick up F# and got reasonably good at it, but it was always harder to sell them on it. I think it's good to have a mix of both. Senior engineers come in with a lot of expertise and can often think about projects at a higher level, and that has obvious value, but I think they can also develop tunnel vision and get fixed in their ways [1]. Junior engineers can look at things with fresh eyes, and give new perspectives on things that can sometimes be non obvious. I also think mentoring is good for senior engineers as well. It's extremely easy to become jaded with industry. Corporations are uncaring monsters that kind of objectively suck ass, and it can easily make someone extremely cynical over the course of several years. I think there's a lot of value in having exposure to people that haven't had the life and hope drained out of them yet. While I'm not planning on doing it again for the foreseeable future, I did enjoy teaching at a university for two semesters, and I particularly enjoyed talking to the ambitious students who really took school seriously. I'd like to think I made a positive impact on them and helped them grow their futures but of course it's impossible to really know that. [1] I'm certainly guilty of that, though I do my best to try and fight it.
- zer00eyz 3y agoNo, we dont want jr level tech talent. If are walking into your first job and you dont have an internship or some open source on your resume I know that you got your degree for the money, not because your passionate. I can also tell you that all the leet code interviews are bullshit. They are a piss poor excuse to filter out the "undesirable candidates". Could you imagine if we hired designers like coders? Yes were gonna need you to come in, we have some text for you to kern and the easle portion of your application is going to be in acrylic or oils, sorry we dont do water color here.
- tombert 3y ago> I can also tell you that all the leet code interviews are bullshit. How else are we going to figure out if this developer knows how to use a hash table??? :) > If are walking into your first job and you dont have an internship or some open source on your resume I know that you got your degree for the money I don't to be "that guy", but what's wrong with doing things "for the money"? I code for fun more than average, but I work for corporations, unambiguously, for the money. If they stopped paying me, I'd stop showing up. There are lots of days (most days?) that I would much rather be working on my own projects than trying to make multi[m|b]illionaires even more millions, but I also like having a paycheck so I work at a company for the money. I think treating work like anything other than a business transaction is a great way to get burnt out, which is why I really don't put up with companies saying "we're more than a job, we're family here!", because that's not true. I used to believe that stuff, longer than I should, but fundamentally a business is a for-profit enterprise, the moment that they think it'll be more profitable to not pay you then they will stop paying you. A "family" doesn't require me to constantly prove my worth to them. I don't think I'm going to have a Zoom meeting with my mom talking about how the market has been bad and my performance is down from last quarter and they have to drop me as a son. Nearly all employment in the US is "at will", and that goes both ways. ETA: I guess what I'm getting at is that I don't really like the sort of culty thing that software engineer do, where you have to treat "coding" as something deeper than "a job". I have met plenty of engineers that I think are very good, but after they sign off for the day they don't even touch the computer. I do code all the time, but I don't really begrudge people who do it transactionally, and it's not something we demand from most other professions. Do you really care if your mechanic fixes up cars in their free time? Are you going to be upset if your chef eats mostly Hamburger Helper at home? Do you think a carpenter is untalented just because they have Ikea furniture at home? You're free to think all those things, but I don't. It's easy to forget that coding is still work, and a lot of people don't really want to work if they're not getting something out of it, and I don't blame them.