Speaking from the perspective of someone looking to hire: It doesn't make for a good impression if I see anyone other than the original author with the same obviously distinctive style of site showing pretty much a subset of the info I can already see from your GitHub account, except the latter doesn't require JS to view.
If I'm looking at someone's personal site, it should look personal --- not "I cloned someone else's I found on GitHub and changed the names and details to mine."
> Speaking from the perspective of someone looking to hire: It doesn't make for a good impression if I see anyone other than the original author with the same obviously distinctive style of site
> If I'm looking at someone's personal site, it should look personal --- not "I cloned someone else's I found on GitHub
To me that seems petty and I feel you'll end up isolating a good portion of the talent pool. Anecdotally, I can only recall a handful of personal sites that appeared to be truly personal (by your definition) and not all may have been.
I don't think that parent comment means "you need to spend hours slaving over a personal website for me to look at". A unique site could be raw HTML with some links to projects. Or you could just not have a site and let your GitHub/LinkedIn/resume speak for itself. A cookie cutter site like this is arguably worse than no site because of how generic and uninspired it is
Exactly, and it is actually the content, i.e text, that matters, not the design (unless the person is a designer, at which point the homepage should be really good).
Judgements like "I'd expect dev to write it themselves" come across as arbitrary. I think there's no shared context wherein interviewers / job-applicants have the same set of assumptions.
Especially since "I'd expect a dev to not rewrite everything themselves, and leverage what's already available" is just as reasonable.
There's not exactly a specific "right answer" about whether you need a personal website, what it should look like, or how it should be written.
> Judgements like "I'd expect dev to write it themselves" come across as arbitrary.
I feel like this depends on the type of dev. If you write C code for microcontrollers then who cares, but if you do web dev then using a generic template not authored by you seems like a bad sign, no?
Part of my concern is: judging a resume is fine, since an applicant is explicitly submitting this. But rejecting based on things done for fun and publicly shown seems 'unfair'. (It's 'unfair' since I'll be judged right now for crap I haven't glanced at for 5 years or whatever, and haven't maintained to the best of my professional ability).
But part of why I consider it arbitrary is it's easy to come up with contradictory criteria, each of which might make sense. (-1 for using latest technology on a personal website, since it shows they buy into hype/resume-driven-development. -1 for not using the latest technology, since it shows they don't know the tools of the trade). I think this bleeds from trying to judge someone's professional capabilities as part of a team, from something produced in their spare time.
> But rejecting based on things done for fun and publicly shown seems 'unfair'.
Portfolio sites are used to showcase the developer's work. If the developer's work sucks then it doesn't matter if it was done just for fun or as an extension of his CV.
If anything, writing my own website sounds like a waste of time, especially when there are so many good tools out there like Hugo, Jekyll, etc. and templates to use as a basis for any personal blog or portfolio.
Hell, I can’t even find time to pick a template and design the look and feel or choose what content to put on my own website.
Please, explain why then? That really doesn’t make sense to me. If someone setup their personal blog/website it’s something they do in their free time. Using the default template is a good way to spend their limited time on what matters, the actual content, instead of creating something that random people will find or not “personal looking enough to be worthy of the job position”.
You get zero signal from the fact that someone decided to use a default template.
If your profession is to create new, compelling, functional front ends and you opt for the easiest default you can imagine for your personal project, why wouldn't you opt for the most easiest thing on your work project?
If I want just someone to write simple stuff I have whole of India to choose from and they are way cheaper than you. If I'm looking for a web dev from western market I'm looking for highly talented people and if you can not showcase that talent then what good are you for?
From my experience thous who have no personal projects of passion that involve programming to any extend usually aren't that good at their job. That obviously doesn't mean that you can not or shouldn't have other hobbies that are not computer related, but again if it comes down to two candidates and one has proof of work in their github profile then the choice isn't that hard to make.
Expecting a dev to reuse code for a personal website is not reasonable.
A personal website is not a software development project. It is not something to use to evaluate a developers technical skills. When you have a real project on the line, then you will see the real skills come out.
For a personal website, I’d expect a developer to give a fuck enough to develop something on his own.
It is just one person's opinion. You don't have to try to slam it down as 'petty'.
They didn't say they reject candidates based on this, simply that it doesn't make a 'good impression'. Weather you agree or not, it shouldn't be hard to understand why someone would think that.
>It is just one person's opinion. You don't have to try to slam it down as 'petty'.
Why? if it is petty, why not slam it? it is a single opinion - do we need at least N people to share it before we can slam it?
>They didn't say they reject candidates based on this, simply that it doesn't make a 'good impression'. Weather you agree or not, it shouldn't be hard to understand why someone would think that.
Unless you make 'Good Impression' on recruiter you aren't gonna pass forward in the process, so it is indeed equivalent with rejection.
I'm a salaried software/database guy for the last 10 years. I ceased programming for personal pleasure before github was invented and haven't done anything more complex than a minor tool on my own time in years.
My personal website is a wordpress blog we've I've dumped some photos of the hardware stuff I do as a hobby.
I'm curious to hear how this factors into your views on what to look for when hiring people?
I'm curious to hear how this factors into your views on what to look for when hiring people?
Having a WordPress blog is generic enough that it alone won't really sway any opinion, but the content you have on it can. The same goes for a GitHub account.
It's really the "I copied someone else's work and made it look like it's mine" type of thing that gives a bad impression.
With the exception of frontend developers. There is an expectation that you have a good personal site regardless of how much experience you have if your job is to push HTML, CSS and JS. Its a showcase for what you can do when you're not constrained by a product or a client.
What I find interesting about your site is that you've updated it at least once to use more modern web standards - that <main> tag was introduced in HTML5 in 2014, and before that you had a PNG image for your name (https://web.archive.org/web/*/http://stefanfisk.com/). Updating a site to give the user a better experience (eg to use semantic tags) is great.
In the beginning I felt like I would need a portfolio and all that, so this minimal thing was supposed to be super temporary. But it turned out that actually talking to customers about their needs and what I could do for them was a quite reliable way to land projects. If anyone asks to see prior projects I send them a selected list that seems appropriate in that context.
If your definition of "frontend developer" is designer, then sure. Otherwise for any dev with experience, this is a dumb expectation. Part of a dev's job is to use the right tool for the job, and there's no sense in wasting time reinventing the wheel.
(I say this as someone who used to overengineer my own personal websites with the hottest tech stack of the week, but am now in the process of throwing it all away for a simple WordPress site.)
Otherwise for any dev with experience, this is a dumb expectation.
A good website that demonstrates some ability to write frontend code well is a shortcut to demonstrating that you're good at what I want to employ you to do. It's a showcase of your skills, just as a graphic designer would have a Dribbble portfolio or a backend dev would have a few repos on Github. I'm not suggesting you can't get hired without a nice site, but if I get your resume you're much more likely to get a call for an interview if you do.
No, the equivalent here would be to expect back-end devs to build their own blog applications. What a waste of time. I did that when I was younger and it was only a distraction from actually writing and building things that mattered.
I built my own blog in Elixir/Phoenix when I was looking for a job as a junior dev, and at that time it indicated to employers that I can learn a new language on my own, that I understand basic web dev, etc. Now that I'm more on the hiring side of the equation I would still be impressed if a fresh CS or bootcamp grad built a blog (or any other simple project) in a newer stack that doesn't yet have hand-holding tutorials.
However, outside of junior level positions, I don't think there's much you can glean from whether somebody has done trivial side projects or not. Obviously an ambitious side project is worth a lot, but the bar for building one is really high and there are so many great devs who can't reasonably make the time outside of work to do that.
No one is forcing you to do any of this stuff. If you can find a job you like without doing it then that's awesome, but plenty of people can't. I'm suggesting a way that people can avoid being filtered out based on their resume because, whether you like it or not, wanting a candidate to demonstrate that they can code reasonably well before the interview stage is quite common.
I think people get a bit too hung up on the way FAANG-size corporations do hiring, with code tests, full time hiring managers, etc. That's only a fraction of the software industry, and if you're applying to somewhere smaller having a public portfolio is useful.
Sure, but this thread is about being judged by the thing that basically links to your portfolio (Github) or contains your demonstration of knowledge (like blog posts) instead of judging those those things directly. The OP dismisses the latter in favor of the former, and that's what I meant was a waste of time.
That you should build something if you don't have anything to show off at all is a completely different point -- and that doesn't seem to be your point when I reread your previous comment? At which point, I'd recommend building something more interesting than a blog unless you're a beginner, and I'd avoid mixing your writing with your attempt to build your first demo project. But this thread isn't about beginner advice.
Personally I place more weight on their professional experience / portfolio and don't feel that having a pretty or flashy site is a good predictor of a developer's ability, especially when most devs are using templates anyways. But yea, all else equal a nicer site is an advantage even if a minimal one at that, not going to disagree with you there.
While it's nice for someone to have a public portfolio of URLs they've worked on you can't really rely on that so much now. 15 years ago sure, everyone made websites so you just asked to see what site's the candidate had built. Over the past 10 years I've found it increasingly common that developers working with front end tech are building things they can't show off - SaaS, internal apps, etc. That's one of the reasons I like to see a personal site or a side project - often that's the only publicly visible code they have.
Ok sure, if you have nothing to show off and no publicly visible code, then sure a nice site might help. My last two companies I worked at have publicly visible websites that I worked on that I can point to, so I don't see why that would matter in my case.
I mean, it depends. I hire SRE/Devops and I really don't care that much if you used someone else's theme, or paid someone to write one for you and credit them. In fact, it'd be kinda neat to find someone who bought a theme. That's just good specialization and collaboration skills.
And my own website is basically the Pelican generator default with a different color selected. Far more damning is the placid update schedule. Try not to put dated content on your front page if you're putting a website in front of manager's faces.
Speaking from the perspective of someone also looking to hire: if you think reusing open source work to accomplish a goal is a great way to avoid wasting time on originality points, then get in touch.
Agreed! If I were a founder and learned that someone in HR was using such arbitrary judgement, they'd be the one looking for a new job. By their standard they wouldn't hire someone like Fabrice Bellard: https://bellard.org/
Exactly. His accomplishments aside, that's the type of personal website that says "I don't really do web design, but I still made a page" --- obviously if you're hiring a web developer then plain nonstyled HTML would be a bit surprising, but someone in a non-web position showing such a site would definitely be seen positively: It indicates honesty and modesty.
Speaking from the same perspective: I don't really care. I rarely look into github repos, unless they mention something during the interview/screen or sounds interesting in the CV. Even then, I spend a small amount of time there (less than 15 min). The noise-to-signal ratio for github/gitlab links is really high.
source: I've been a hiring manager for large companies (and a few startups) in SF for the last 8 years.
Well, I'd argue that using templates as a base is OK. Especially if it's just gonna be a page containing your portfolio - looks more presentable that just a plain github account.
Using templates can be free, or low cost, compared to writing everything from scratch yourself. There are other things I'd rather be doing in my spare time.
Would you be impressed by some out-of-place text, an animated SVG and a shade of purple as theme? I could randomize the parameters and make a lull-recruiter-as-a-service.
"Is your website too bland? Did you just git clone someone else's repository? Concerned about job prospects? Do not fret!"
> Speaking from the perspective of someone looking to hire
Doesn't it friend in what you're hiring for? I'm not sure a backend developer should be expected to craft together a great website.
And even if you're hiring for the front end, I've found that being proficient at a11y or building React apps or designing elegant CSS doesn't really predict your ability to execute on a professional profile site, which is essentially a marketing tool.
Disclaimer: I'm working on a tool for developers [1] in this vein.
So you're basically judging the book by its cover? You don't care about the content at all?
That only makes sense if you're hiring a frontend developer. Many people who are excellent programmers hate frontend development, and will happily use a theme or clone a repo if they can avoid frontend work that way.
So you're saying you wouldn't want to hire someone who put in the absolute minimum effort to meet the desired functional requirements without wasting time/money?
I think the functional requirements in this case are to impress someone who doesn't code, an HR person, etc. Because a qualified programmer manager shouldn't be particularly impressed with any personal homepage put together in a reasonable amount of time for the sole purpose of impressing a hiring manager.
There's places where it's worth it to "think outside the box" and then there are places that -- well, there's a reason we have boxes, because they work well for what they're designed to do.
I probably wouldn’t take the time to build a personal website at all, but if I did, the website is just a means to facilitate communication of whatever core message I want to convey. Personally I think a strong engineer is resourceful. I’m not saying this Git repo should be cloned by everyone or anyone, but in solving real world problems, I don’t expect my team to reinvent logging, dependency injection, or basically any other undifferentiated piece of work unless we have a strong business or technical reason to justify why it wouldn’t be undifferentiated. To me, the website is similar maybe unless I’m trying to show my web and visual design skills.
When going for a haircut, would you rather have your hair cut by a person with an immaculate haircut, or by a person who has noticeably not had their hair cut in a while?
On the flipside, developers are not designers. "I took a decent pre-existing design and didn't try to fiddle with it too much" is a Good Thing, surely.
Another static site generator. Being an emacs user i based mine off of org-page by forking it. Perhaps other can fork this too or just go ahead and use Jekyll?
Hm. I might share my personal site with you (I don't operate one anymore) but certainly not my github account. I agree with the site would need a personal touch, but not every programmer is a web developer. There is quite a bit of specific knowledge required to set one up.
That might be different if you hire web developers of course.
There’s also something to be said, from a recruitment point of view, to having everyone’s site look the same. It eliminates one bit of unconscious bias. In a way, it can help anonymise each person, which can make for a different (perhaps fairer?) hiring process.
If I'm looking at someone's personal site, it should look personal --- not "I cloned someone else's I found on GitHub and changed the names and details to mine."