That said the main thing the company hiring needs to know is does SO story predict success in the job? Probably a little bit - it at least highlights commitment and you could scrape HN to find good stories then reach out. But if you ask “do you have a story/why not” to people coming in from regular channels even SO applicants I think it’ll waste a lot of people’s time in both sides.
I fail to see how, if we are talking “clean code,” a short leetcode test will say anything more than a portfolio; even one with “quick and dirty” code (which is all you’ll get in the test, anyway).
Also, if companies start using portfolios as material for hiring, then folks are a lot more likely to take care, in their extracurricular work. That won’t hurt. I think there’s a real crisis of quality, in today’s software.
I see a lot of pretty impressive stuff, daily on GitHub; even “experimental” projects. There’s a great deal of code and history out there. The fact that someone is working on side projects; especially if they are doing so as part of a team, can speak volumes on their behalf.
The SO Story is less common. I wouldn’t expect that from everyone, but it can be quite helpful. It organizes this stuff.
Have you ever seen a graphic designer apply for a job?
When they arrive for their interview, they come in, holding a large, flat, black case. It’s called a “portfolio,” and contains samples of their work. They often also contain interim work, showing the person’s process.
Even students, fresh out of school, are expected to have one. It’s so standardized, that companies don’t even mention the need to bring one with you.
Today, it’s probably quite common for the portfolio to be digital.
No design company on earth would ignore that, flip a matchbook into the interview table, and ask the designer to “draw Spunky,” but that is exactly what most tech companies are doing, these days.
Basically, what I am saying, is that many folks have a lot of pretty good stuff available as some kind of portfolio, and it’s, quite frankly, ridiculous to think a whiteboard test will tell us more about someone than that.
Even if the work is not suitable for our use, it can be the structure for a conversation. One of my favorite things to do, in an interview, was to find a “story” the applicant wanted to tell, so a lot of my questions were designed to find the “hook,” where they suddenly smiled, and started to tell me about problems they solved, or teams they worked with.
Those conversations are gold. They are what we look for. All the rest is BS, and many developers aren’t “people persons.” Getting them to “open up” like that is really the job of any interviewer.
It has been my experience that hiring managers and recruiters completely ignore portfolios. Even companies that ask for GH or HN handles seem to ignore the contents. I think they just want to find out if people have them, as some kind of “cultural flag” (I have also seen a lot of GH handles that tell me the developer is not so good, but I’d not know that, unless I looked; and what people write here...well, not so sure that’s helpful to convince managers that we’d be good team members).
[0] Don’t take my word for it; look for yourself: https://github.com/ChrisMarshallNY
[1] This shows the reach of the project. It’s a “live” dashboard: https://tally.bmlt.app/
Yes you have, prima facie, written good code. I don't have 2 hours now to fully critique it though. If I were interviewing you and using this code to see whether to hire you, I need to do a lot of work to see if (a) you really wrote it and (b) it is well engineered given the problem space. I'd mark you up for the great documentation though - I can see at a glance that there are lots of code comments, and a good README.md - so that is positive. But it's not a deciding factor, I still need to see if you can code.
If I am looking at Githubs, well I have 20 candidates. 20 different code bases, trying to achieve 20 different things. That's a lot of work to weed out. I don't mind that at a late stage, but not an early one. Some companies say - 2 hour coding test or BYO open source project - BUT that should be a small volume and you need screening rounds before that.
However if I were interviewing you and gave you a leetcode or similar test, I know the answer, and I can probably run some auto tests on it. Much easier and practical for early rounds.
Also switching it around a lot of good devs don't do side projects at all. Doctors who do doctors without borders are probably better on average (?) but would it be a hiring criteria?
Or builders who help their local church rebuild a wall.
Builders can have portfolios. Luckily that can be based on the work they were paid for, due to IP not being an issue. When a new architectural techniques comes out, say a new kind of render, they can add this to their portfolio. If a new tech comes out, say "Rust", I need to make a mirror project for my portfolio as the work project is IP protected. I need to build that church wall to get a job if a FOSS project is expected.
If someone is able to hack GitHub to fake tens of thousands of lines of high-quality code, ten years of commit history, dozens of Medium articles and blog entires, multiple Web sites, and documentation up the wazoo, then you should hire them on the spot; even if they are fronting for a Hyderabad shop.
Like I originally said, and this goes double for small teams and startups, every employee is a huge commitment. I would gently suggest that “shortcutting” the process is kind of reckless. It’s pretty easy to figure out if someone wrote something, by simply saying “This project you did is pretty cool. Tell me a bit about it.” Bang. You just struck gold. A portfolio would be a perfect opening for these types of questions. I would struggle to find those "hooks," with some applicants.
In my stint as a manager, I had to fight like hell for every headcount, and I kept employees for decades. There was no way that I’d “shortcut” that process.
YMMV
I think that we’ll be seeing a lot more open source for proprietary work, in the future. Decompilers are so good, that it’s damn near impossible to truly hide how we do stuff.
Another thing that needs to DIAF, is the "shower clause." This is the clause in the employment contract that says "Every idea you come up with in the shower at home belongs to us."
I didn't have it with my job, so I was able to design a lifesaving infrastructure that is being used by thousands of people around the world, and has now been passed on to another generation of engineers. It's going to become a ubiquitous infrastructure, and will directly impact many, many lives.
That would not exist, if I had had a "shower clause."
If someone has a great idea in an extracurricular venue, then don't try to bully them into handing it to you for free. Figure out another (more equitable) way to get it.
The whole deal with employees, is that we're not "Programming Modules." We're humans, and we need to be treated as humans, from the job ad, to retirement.
But I have the luxury of choosing what I want to work on.
I’ve spent my life living frugally, and investing cautiously, but aggressively.
I am not wealthy, but have enough to maintain my (fairly humble) lifestyle, while I spend -literally- 7 days a week, learning tech, which I love doing.
When I left my last company, after nearly 27 years, I did look at working elsewhere (I was a manager), but the way I was treated in that search was so abominable, that I decided it was not healthy for me to continue the efforts.
Being older in tech really stinks. This goes double, when we switch from management, back to tech, so my network is useless.
It was much better for me to give up on playing other people’s games, and do what I need. It literally would have killed me, otherwise. My health has improved dramatically, after making the decision to do my own thing.
It’s working out. I discovered that I never lost a thing, tech-wise, but I did need to spend the last three years “retooling” myself.
I am not actively seeking gigs. It’s been my experience, that as soon as people find out about my age, the relationship immediately dies. This is particularly obvious with recruiters. I’ve started to make my age clear, right off the start, to avoid that.
I’m an extremely good engineer, with “bleeding edge” skills, coupled with a lifetime of shipping software. I’m damn good, up to date, and used to Getting Things Done. I can prove it, too, with an enormous portfolio of code, apps, Web articles and participation in many fora.
I’m an “open book,” with nothing to hide, and nothing to be ashamed of. I have a very high level of personal integrity, self-discipline, and empathy.
I have a fairly deep and wide skillset that is quite rare in today’s tech world, coupled with enormous experience and a great deal of energy. I’m gregarious, optimistic, compassionate, and a marvelous team member. I treat others with respect and kindness. I’ve architected infrastructure that has become a world standard, and written humble little “toy” apps. I also have some specialization in areas with a substantial future (iOT, Apple tech, and Surveillance tech). My current project is a low-level abstraction of Core Bluetooth for Apple operating systems[0]. It’s not complete, because I still need to write three more test harnesses and supporting documentation. Despite that, it’s already in a shipping app[1].
I’ve been looking at applying my skills to help NPOs and whatnot to thrive in today’s world. There’s a dearth of up-to-date talent interested in doing that, as there’s not a lot of money, and the NPO scene is pretty crazy, in its own right.
Because of my investments and humble lifestyle, I would have been happy to work for far less than many, as long as the work was interesting, and I was not asked to compromise my principles. I wouldn’t have minded taking risks with startups, to which I could have brought a really unique level of experience and expertise. I would think that someone that is used to shipping would be useful to a startup. Also, I've got lots of experience evangelizing projects to cynical, empirical, intelligent managers at all levels of a corporation.
I’ve also started to look at training. That’s something I can do quite well.
But I’m pretty bad at leetcode, and I’m...well...not young.
I won’t enter a relationship that requires I be humiliated and treated like garbage. You -literally- can’t pay me enough for that. I never did that with any of my employees, and it’s rather shocking to encounter that in today’s tech scene.
It’s not surprising that the average stay at a company for an engineer is around 18 months. I kept senior-level employees for decades. It’s amazing what simple compassion and respect will buy you. None of us was paid particularly outrageously, but we were a very tight team.
It really is interesting that requesting (not demanding) to be treated with a little bit of respect is considered “arrogance.”
[0] https://github.com/RiftValleySoftware/RVS_BlueThoth
[1] https://apps.apple.com/us/app/blue-van-clef/id1511428132
Remember, "Python to create thousands of individual reports on thousands of rows of postgres data per report"
I think paying over, say, $75K is going to fail because anyone who can easily make more than that is going to consider themselves too good to do this stuff.
There's plenty of stuff that you can pay peanuts for, that you can't get a FAANG-level SWE to do for any price, so the answer to finding the right person is not always "pay more" or do any of the other things that people making $600K instead of $60K expect.
However, I do have something that will tell you an unbelievable amount about me; the StackOverflow Story[0].
I have a gigantic portfolio, with dozens of repos, hundreds of thousands of lines of code, a decade of commit history, dozens of published articles, going into tremendous detail about the way I think, work, architect and code. I also have a bunch of apps on the App Store, with full source[1].
TL;DR: There should be no question as to my abilities, or even "soft" factors, like personality and team dynamics.
Maybe you don't want a "shortcut." I was a development manager for a quarter of a century. It was a small, high-functioning team. Every person we hired became part of the "family," and was a commitment. When they finally rolled up our team, the person with the least seniority had a decade.
There was no way that I would “shortcut” that hiring process. Each engineer was a major deal. I would have killed for the type of information that even a quick glance at a GitHub ID will give, let alone an SO Story.
It has been my experience that the "shortcut" everyone wants, is a 50-line binary tree leetcode test; which I am pretty terrible at, as are many experienced engineers.
For some reason, that tells more about me than the portfolio; which recruiters have always immediately ignored. It was insulting. It was meant to be. After a few of those, I just gave up looking for work long ago. I now just do my own thing. I don’t have a thing to prove to anyone.
I am not alone. I routinely visit GitHub pages jammed with detail about how people work.
I often see solid green activity logs (like mine[2]).
You should look for a portfolio, and ask why not, if they don’t have it. Also, don’t wait for them to come to you. Seek them out. Use your network. It’s a big deal. It’s worth the time and effort.
[0] https://stackoverflow.com/cv/chrismarshall
[1] https://littlegreenviper.com/AppDocs/
[2] https://github.com/ChrisMarshallNY