I'll give you my opinion here, fwiw! If I'm looking at a dev in a corporate environment, the meme-related toy projects are a good start (everything else being

I'll give you my opinion here, fwiw! If I'm looking at a dev in a corporate environment, the meme-related toy projects are a good start (everything else being equal) but I'd rather compare apples to apples. If I was interviewing you, here are a few points that I'd likely bring up if you showed me your code (again, this is just my opinion and I'm going to assume you're looking at junior dev roles here): 1. Show me how you handle malicious input (assuming forms on your site) 2. Show me how you ensure you don't add errors to previously working code (here, I'd be looking for an example of tests - they don't have to be comprehensive, or even all that good, just that you are thinking about it) 3. Do you have a datastore of some sort? Show me how you read/write to it (again, doesn't have to be a clustered Postgres infrastructure, it can be a text file but I want to see how you handle the thought process of reading/writing to a data store. So if it was a text file, you'd likely have some sort of lock when writing so do you handle errors when another user wants to access it, for example). These are just things spewing out my head as I write this but I'd be looking for someone who is thinking correctly and perhaps has an idea of the kind of things that would be required in a corp env, not necessarily how to do them. So if your single unit test is a bit shite, but you actually have a unit test, I'd call that a big win (I'm sure I'm not the only one that's inherited multi-thousand-line codebases with no unit tests!!!). Likewise, you'd wrap certain code blocks in try-except blocks and so on. Oh, I may ask you to code something simple, fizzbuzz for example too and, in all honesty, if you can do that, you'd be an ideal candidate! Any/all of these things would put you high up on any candidate list I reckon. Anyway, just my $0.02