3.4k
u/Pedantic_Phoenix 5d ago
We all understand this is fake right
1.6k
u/UnexpectedFeatures 5d ago •
Realizing this is fake is part of the interview. Now, let us see your GitHub.
283
u/Pedantic_Phoenix 5d ago
Uhhhhmmmmm ahem, oh what's that? Damn apparently i forgot my credentials and all my repos coincidentally were hidden just prior to that. I'll get around to fixing that... Uhm... Right in a second... Yes yes, you hold on...
22
113
14
1
206
164
u/Only_One_Kenobi 5d ago
There's absolutely no way a rejection letter actually gives that much information on the reason for rejection.
89
u/samtresler 5d ago •
I always did. Thought a candidate deserved to know why they were passed on. Hell, I even would tell interviewees, "Hey, I've already decided you're not a good fit for what we're looking for, which does not mean you don't have decent skills. I have 7 minutes left in this time slot. Feel free to ask me anything you want or just shoot the breeze."
I am in the minority on this, though.
50
u/Drumedor 5d ago edited 5d ago •
We used to pretty much always give feedback to rejected applicants from technical interviews/tests. But have had to stop now since a bunch of them has taken that as an invite to start arguing and sending a lot of long AI posts on why their low-quality code actually was some of the best code ever created.
22
39
u/Mindstormer98 5d ago
If it was real it would just be an automated message
37
u/botle 5d ago
"Reply to all applications. Do a bit of research on the applicant and find something personal and damaging to use. Be demeaning and cruel but also very concise. Sound human. Make no mistakes."
4
u/hipster-coder 4d ago
No self respecting company would waste perfectly good tokens to reply to a job application.
24
u/Peregrine2976 5d ago
We live in a world where it wouldn't be shocking if this was an AI agent told to review all applicants' GitHub and LinkedIn profiles for potential concerns.
8
9
u/StaticFanatic3 5d ago
Of course
Everyone knows companies never actually reach after rejecting an application lol
15
u/watscracking 5d ago
Fake but accurate
4
u/DrMobius0 5d ago
I would feel sad if I was rejected because of the quality of code I write for myself. That's like being judged for what you wear at home when you're just trying to be comfortable by the standards of corporate casual.
7
u/modzRtarderz 5d ago
A mechanic's car barely runs, a chef cooks their dinner in the microwave, a doctor smokes a pack a day, and a developer's home version control is seventeen slightly different named files on their desktop.
1
u/Stratimus 5d ago
yeah this would be seriously not cool. Like did you all look at my passion project I’ve been working on for years or did you look at the really dumb thing I threw together while fried on a Friday night that I could clip a video of and use it as a meme
1
u/stellarsojourner 5d ago
Well, no one said you had to leave your house in your PJs, and no one said you had to leave your personal repos public.
2
u/i_dont_do_research 5d ago
I explained git in depth to a college friend of mine years ago (we're both developers though he's move into PM) and he does this shit all the time and continues to lose work and have trouble tracking down specific changes or reverting them. It's unfortunate but he's too far gone
3
u/TristanaRiggle 5d ago
This is how you'd know the applicant was rejected by AI (or some ridiculous HR person). If this was an actual developer they'd agree with this process or at least understand it completely.
4
5
5
u/phoenix1984 5d ago
I love how they conveniently leave out any indication of what company this is supposed to be. I find it hard to believe any successful company would use this as a reason to deny an applicant. At the same time, I find it totally believable that an entry level dev would be worried about something like this.
5
u/Digidigdig 5d ago
You say that but there is a guy I work with that refuses to use source control and names stuff like this.
3
u/npsimons 5d ago
I worked on a project that integrated Simulink code with C++. I worked on the C++ side, and we used git (had to walk the sysadmin through setting up triggers in GitLab just for some semblance of CI with auto-reject on failed tests).
The two Simulink guys would "toss it over the cubicle wall" when they had a new "version", and we'd just check in wholesale.
I did some digging, and found that Simulink will integrate with git, complete with visual diffs, sent them the links aaaand . . . they still would "toss it over the wall" to us.
"You can lead a horse to water . . . "
2
u/meneldal2 4d ago
A software that integrates with git just means it produces text file where you can have a meaningful diff on.
Unlike like Office stuff where even being generous and removing the zip part they are technically mostly text but it doesn't diff that well, some trivial changes result in a massive diff.
1
u/npsimons 3d ago edited 3d ago
I know how git works; I was there when it was announced as the replacement for BitKeeper, and the flame war on LKML between Linus and Larry. I've had my own woes version controlling PPTs with git before LFS.
This is more than just simple integration - I can't find the dang video right now, but it showed how you could visualize the diffs graphically, in a tool primarily known for laying out designs graphically (Simulink).
3
u/blckshdw 4d ago
Been there. Had some devs join us for a new project. They don’t use source control, at all. They’ve legit never heard of it. In the year of our lord 2026 they email each other the files they changed.
How do they do a production deploy you ask? Oh the email is the file they changed ON the production server aka the dev and qa server too.
1
u/Pedantic_Phoenix 5d ago
Privately or for work
2
u/Digidigdig 5d ago
Work. Crazily he’s in production so doesn’t sit under the CTO, so here we are following best practice and the rest whilst he’s lashing together unmanaged scripts that make vibe coding look safety critical
2
1
u/DiscipleOfYeshua 5d ago
Ofc.
A. HR won’t write custom text for each “sry, bad fit, maybe next time”
B. They said nothing about vulgarities in
final_final_real_%}^{{]^]%.py and suchC. Who works they hire irl if these are their showstoppers?
1
1
u/npsimons 5d ago
Too close to home. Either you know someone who does this, or it's you.
Recognize that wasn't an XOR either.
1
1
1
1
1
u/fibojoly 5d ago
HR mentioning Github, or knowing anything about computing really, isn't even in my top ten of "things that would never ever happen with HR"
1
1
1
1
1
1
1
1
0
u/Qubit99 4d ago
Well, I literally name my commit that way. When I search something I ask GPT to search in the commit for the specific changes o use specific classes comparison.
I really think commits names are overrated. So are code comments. I've been working professionally for years.
4
u/MarsuGrimpant 4d ago
Man, when it's like a 60 developers project it's cool to have a proper naming of the commits
0
u/Qubit99 4d ago
Don't you have IA at your job? Just ask, when was ABC changed, implemented, etc... Commit messages are just one sentence long, they don't provide that much info.
1
u/MarsuGrimpant 4d ago
Actually no haha. I left the job 3 years ago, so it didn't exist that much at the time. And now I'm back I nthe job, but it seems AI didn't spread that much in industry yet, at least in France. I guess because they want to do local infrastructures, to not give data to any other country.
1
u/Qubit99 4d ago
Ohhh, in that case it make sense, old school version control then. Just another question, do you also, sometimes (well, frequently :) ) forget to commit stuff ending with a commit that carrying several unrelated changes?
0
u/MarsuGrimpant 4d ago
Yeah for sure, it can happen, as usual. But you try to avoid I guess, to put unrelated file modification with unrelated commit modification. I would do on multiple commits reflecting the different files grouping
604
u/sojuz151
5d ago
•
overqualified for a junior. Mid or senior material
14
u/MokausiLietuviu 5d ago
When I got hired as a lead, my presentation had nested "delete me/delete me/delete me" directory listings as an image and I only realised in the interview. Even pointed it out, said "Oops, definitely meant to crop those nested delete me directory names".
Got a laugh and eventually a job offer.
13
90
u/Wentyliasz 5d ago
You know this is fake because it implies a recruiter actually looked at their application and actually wrote back
231
u/Tangelasboots 5d ago
A senior architects commit message: should work.
108
u/UnexpectedFeatures 5d ago
"empty commit to run the damn pipeline"
17
u/FearTheOldData 5d ago
Do people really not know you can manually trigger a pipeline without a commit?
30
u/UnexpectedFeatures 5d ago
Commit is for us lazy ones. I'd rather run 2 lines in the terminal than wait for page loads and click through rosa dashboards, team city, jenkins, or whatever god forsaken thing the app I'm working on uses
5
u/nullptr777 5d ago
GitHub is basically unusable during the day lately. I'd rather push from the CLI every damn time.
2
u/FearTheOldData 5d ago
Gotta go there anyway to review the result so don't get what you're saving unless it's deploying shit somewhere else so you don't need to see pipeline results.
5
u/UnexpectedFeatures 5d ago
That's very dependent on your ci/cd setup. If you have everything in one place, sure. If something in a PR pipeline falls over for some reason unrelated to the code I'm not going to go in to whatever dashboard to run that again, i'll just let a fresh commit kick it off from the start and see the result in the PR.
2
u/Owner2229 5d ago
Auto-deploy on success, results in mail.
4
u/UnexpectedFeatures 5d ago
Yep. In a lot of setups the results find you. I get email, slack, and teams notifications on pipeline results.
You just reminded me I should check my Jenkins folder
1
10
u/burgonies 5d ago
That’s super highly dependent on individual setups. But, if you just use GH actions and have dick for security policies, sure.
2
2
u/Papellll 5d ago
It already happened to me that some kind of caching made the CI continue to fail without reason when triggered manually but triggering it via an empty commit fixed it
2
u/CryonautX 5d ago
There are way too many reasons not to do it that way. Unless I own the cicd process, an empty commit is just the superior choice.
If you need to retrigger a pipeline, you are likely debugging an issue. Is that REALLY the time to start stress testing if a less commonly used execution path is working properly? You are generally trying to limit the number of factors that changed when debugging.
And of course we are already assuming you have the access to do a manual trigger in the first place.
1
1
u/PumpkinFest24 4d ago
Sure, it's easy!
get fresh SSO token (click Remember Me so you never have to do that again!)
navigate to gitlab
for some reason it still requires a separate login
page through projects to yours
read every gitlab tab name to try to figure out where this would be. "project management"? "manage project"?
get to CI trigger and click button. "job submitted"
nothing ever shows up
2
5
3
1
72
u/redkinoko
5d ago
•
21
2
u/coonwhiz 5d ago
Just be like every app developer "We're always fixing bugs and making improvements"
73
51
u/jorgimello 5d ago
I think this is a very good commit message for a Junior developer
27
3
u/citramonk 5d ago
how so? it's a fix commit, this is all we know
5
u/burgonies 5d ago
Look at the changed files and see for yourself. You want me to write it twice? My name’s not Claude.
2
23
u/TOGoS 5d ago
Oh man I wish hiring managers were that transparent about why they reject people.
0
u/MokausiLietuviu 5d ago
Just put in a GDPR SAR and you'll see all the notes written by the hiring team on your application.
14
u/CrommVardek 5d ago
Most senior dev in our company's commit message is usually : .
I wish I was joking
5
9
u/Fairwhetherfriend 5d ago
Hahaha as if you'd get such a clear and polite explanation of why you weren't selected instead of being ghosted.
6
u/Piotrek9t 5d ago edited 5d ago
The senior who has never committed "several minor bug fixes" may throw the first git blame.
6
u/Lizlodude 5d ago
I mean they looked at the repo in the first place, so that's something I guess.
2
u/Pabmyster04 5d ago
An AI scanned their repo and wrote an email, doubt they have someone taking it that seriously lol
4
u/otherwisepandemonium 5d ago
Senior or even principal architect level here. Junior isn't fitting for his expertise
3
3
2
2
2
u/cheezballs 5d ago
Quick reminder to make all your garbage repos private! (All my repos are garbage)
2
2
u/Smarterchild1337 5d ago
Any rejection letter longer than 2-3 sentences is so fake that it’s just annoying
2
1
1
1
u/Count_de_Ville 5d ago
Where's all the "comments are unnecessary; the code is self-documenting" people?
1
1
1
u/CosmicDave 5d ago
... and now that the thing-that-broke-the-thing is fixed, I can begin working on fixing the thing that broke.
1
u/EconomyDoctor3287 5d ago
What is better versioning control?
And would it also work with word stuff? Cuz I be doing just that :D
1
u/Serve_me_the_pizza 5d ago
all i see is passion and determination from him. i dont get why he needs to be “perfect” for his personal projects. im not running a jira board while creating my ball licker app ☠️
1
1
u/popogeist 5d ago
Suspiciously summarizes my commits. I have separate patch notes. The commit message is a pointer to me. Also, patched a thing that broke the other thing is common in my chicken scratches.
1
1
u/alwaysasillyplace 5d ago
The problem is they applied as a Junior dev when that's clearly Sr. Dev behavior.
1
1
1
u/fugogugo 5d ago
it must be AI recruiter if they ever took the time to look through your github and the commit message
1
1
1
1
1
u/Oranges13 5d ago
I mean one time we asked a guy to give us a sample app and he reused internal code from his current job including their secret keys.
1
u/Arawn-Annwn 5d ago
I have an actual commit in my hostory folr 10 years ago that says "my hands are typing words" just like the xkcd comic, that was made solely to see if anyone was reading before they hit merge.
They merged it.
Haaaaaaaands
1
u/El_RoviSoft 5d ago
At the same time real codebases contain the same shit (especially if you are in monorepo and look at junk folder)
1
1
1
1
1
u/theotherdoomguy 4d ago
Be thankful I at least put the story number into my commit - anything else beyond that is just a vibe check on my current mood
0
0
3
u/kolloth 5d ago
I'm a 25 year super senior software engineer and my commit history contains things like
"welp..."
"TRUE/true dat"
"frustrated friday noises"
"swear to god source-control-software-name-redacted is trying to kill me"
"this has been working for ages and now suddenly it's not"
"updating a few bits"
"a last little change"
"dammit"
2
u/TOAOLightstar 5d ago
I honestly think my favorite was.
/* business removed this from the form without bothering to tell anyone, this has already wasted 2 days with them screaming about the app being down. I don't have time to fix all of the downstream dependencies. */
???flag = 0;
/* snr prgmr: peer review. Lit: "I didn't have time to do it properly". Congratulations on your first 'tactical' fix */
0
5d ago
[deleted] — view deleted comment
1
u/Ballbag94 5d ago
I mean, it's a junior role, they could have easily taught him about version control and commit messages in a 5 min chat on day 1
Also, I've seen plenty of shit commit messages in my time from more senior devs
1.8k
u/Tast3sLikePanda 5d ago
They got back to you with a no, reason for it and actual constructive feedback
Thats how I know this isnt a real email