Kinda clever, but as a hiring manager who looks through commit histories to see how you write code and what your typical process is, I would immediately disqualify a candidate for using a tool like this.
The typical interviewer would first proceed by checking the developer’s grid, the more you get green squares, the better. Specially on Sundays and Saturdays.
Yes, this is how it works .
Look, congrats on making and releasing a thing, but this is pretty daft. You are suggesting making it so that the most visible thing on a user’s profile page is something that really, really obviously is a lie. At least just make a bot that does something silly for the sake of being silly, this is just daft
I would toss out an applicant if I found this. Honestly, I would probably toss out an applicant for having this as a project repo (it tells me you have no problem being explicitly manipulative).
First there is a difference about what you wish to recruit and what you recruit in reality. As the repo is private, you would never notice the trick, and enjoy the green grid
Second, maybe you work in an hiring agency or a big company, then you would be looking for someone with experience or diploma, you would never hire a junior self thaught on this website.
If you would be a business owner, maybe instead to see evil people who cannot fit in your HR checkboxes sheet, you would appreciate people who can get the sh*t done and do the job.
Please don’t double down here! If you’d just said you’d made a silly thing that auto committed, fair enough. But you wrote an article to try to persuade people to use this as a genuine tool.
I can’t quite believe I’m having to explain this, but the grid is just a compact calender view. Say someone gets an interview & had used your script. They now have a GH account which displays huge amounts of private activity. They are going to have to lie about why they’re constantly using GH. It’s not going to make an interviewee look like a go-getter, it’s just going to make them look extremely stupid.
The typical interviewer would first proceed by checking the developer’s grid, the more you get green squares, the better. Specially on Sundays and Saturdays.
What I want to hire is a developer that’s going to stick around for at least 90 days (and then one year after that) with glowing feedback in their performance reviews. That’s true for every hiring manager.
What I don’t want is a developer that is fired for:
Incompetence.
Culture fit or maliciousness.
I work for a small-mid SAAS company. We do all our own hiring.
A degree in CS is favorable. Projects are favorable. Past relevant cross-experience is favorable. I would not throw out an applicant just because they lack a degree. Again, my #1 focus is placing an applicant that’s going to achieve and stick around (my bonuses are tied to those KPIs).
Very incorrect.
I learned about FCC from an applicant. He was self taught (mostly from here) and still works with the company. No degree.
I actively recommend FCC to anyone that asks me “what’s the best way to learn coding and get a job?”. I also recommend FCC to students studying CS so they’re actually employable.
To piggyback on this, if I see months worth of GH activity without a missing day, I’m going to ask about that history. If you give me a vague “oh, yeah I’m sure active” I’ll push for an answer about the project such as:
This holds up until the question of “I see you have a lot of github activity, what do you work on?” comes up. You either make something up, or you admits its fabricated, both aren’t good.
Its one thing to see activity, its another to talk about it. Any interviewer worth their salt will want to know what you do more than how much you do it.
I’d consider this bot either a fun experiment, or a bad attempt at working the system, all depending on you spin in. Like any lie you either end up having to make more lies, or you get found out and pay for it.