Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
Report this post
However, if you're trying to get a job as a software developer and you have a few mods which are well received and very few bugs, and those found are squished fast, that that could be good.
Many factories use PLCs in their processes, and those are extremely similar in operation to the what circuit networks work in Factorio. If you like the circuits and have done some complex designs that might deserve a mention, if you were going for a position working with PLCs or at least as an engineer working on processes where they are heavily used.
Of course, there's also the possibility that the resume reader knows and loves Factorio - and knows you'd always come to work short on sleep from playing all night. Might find a fellow player for some multiplayer games, but not get the job.
Though, as a general rule, hobbies usually don't belong on a resume unless they seriously display competence in the target field, and much as I love the game I'm not so sure being good at Factorio necessarily means good at engineering. Good at engineering probably means good at Factorio, just not the other way around.
Best bet, leave it off. You can mention it if you see the gear icon on their work computer, or their desktop wallpaper is a Factorio themed one.
Even if the subject matter was relevant it's doubtful it would have any effect at all, no self-respecting recruiter even cares what people's hobbies are.
In the modern IT market degrees are worth almost nothing. When given a choice between a guy with a programming degree and a guy who worked a year at a real job, in a real working environment, the latter will be picked almost every single time.
You're literally better off spending all this time learning it yourself, while doing pro-bono freelancing and working on your own projects, that would be worth a hundred times more on any resume than a degree. People don't care where you studied, they care where you worked and for how long, or what of note you have actually done. The only places where any programming degrees are required or cared about anymore are government tied or very public facing jobs: a combination of being stuck in the past and having to put on a "professional" veneer.
Do you have data to back up this claim? The company I work for wont hire unless you have at least a 4 year degree.
Sure, go look at job postings for generic programmers, testers, sysadmins, devops, etc. on linkedin for example, they are publicly available for everybody. Last time I checked almost none of them had degrees in their requirements, it's always working experience.
The only places that regularly require a degree are either some very specific fields that require some very specific subject knowledge that's very rare unless you actually studied it (like robotics), or postings for government or financial institutions (the ones that are very public facing and want to maintain this very pristine image of themselves for whatever reason). Maybe even some high profile public companies who want to do the same thing will do that, or some old companies that still haven't revised their hiring practices for whatever reasons.
But those are a very small segment of the whole, less than 10% I'd say. And from my own experience I can tell you this: I got into IT without any degree at all, I learned basics of coding by writing scripts for RPG maker back in the day, then it just went from there. After I secured some initial work experience my lack of degree didn't matter still, barely anybody asked me about it during any job interview. I never even mentioned my education in my resume, only my experience and achievements, together with any references (those actually matter A LOT when you get to later stages of recruitment and can easily be a deciding factor if they aren't sure which candidate to choose). I also have a couple of friends who are pretty much in the same boat as me, learned it either themselves or picked it up in high school from classes and them continued to learn and practice on their own, they all work different jobs in IT now together with me.
Would be a different story if you had a catalog of professional-looking mods to showcase that relate to the job, or something similar, but just playing a game is generally not something that improves your odds of being invited to an interview.
I believe that different aspects of the game can be used to showcase several different talents, including engineering. I'm not so sure that being a world record holder, or in that general range of speed to launch necessarily showcases engineering so much as practice and persistence.
There remains, however, one problem to using your star-studded map as a showcase. Whomever is to be impressed by the saved game has to understand the game well enough to recognize the "skill" it showcases.
If you happen to know that "this" hiring manager plays the game, it might be worth considering. I suspect that it's going to be rather rare for you to know this beforehand, however. Lacking that specific knowledge it might be more like playing the lottery.
Including the details on your resume would have one of two common responses. Of course there are a whole range of responses, but most will fit into one of two groups. The uncommon case is that the hiring manager, or someone else in the resume review chain, understands Factorio, whether they like it or not, and can "see" what your game has to showcase which relates to the position. The more common, probably around 95% of the time, is that nobody understands the game, if they even know it exists, and the references will trigger a response something like "Oh, no! Not another gamer!" and the resume will land in the circular file. Gamers understand gamers - even when they share no common games or genres. Most of the rest of society views gamers in a, shall we say, less than positive light. The conventional wisdom, esp. in business, is that gamers have no self control and are addicted to gaming just as much as an alcoholic is to whiskey. They just cannot help themselves, and eventually they'll start playing too much, staying up too late and be tired and unproductive, even when they manage to arrive on time.
Of course, we know that none of those stereotypes are correct. Gamers have bad apples like any other group of people. Still, are you willing to gamble that your resume lands on the desk of that one golden unicorn of a manager who understands gamers and knows how to "read" a Factorio map?
Either the one reading it does not know Factorio and won't accept you because you list video games on your resume.
Or he does know Factorio, but then he'll know that you are chronically sleep depraved, will come in late a lot or won't show up at all because you played "2 hours" but ut happened to be 2 days.