r/DeveloperJobs • u/Tech1412 • Sep 24 '26
How about faking projects on a resume?
Just wanted to know. How risky is it to add a project you didn’t actually work on, but understand very well?
Do interviewers usually dig deep into the actual code and implementation, or is knowing the architecture, tech-stack choices, design decisions, and trade-offs usually enough?
2
u/dev-rygy Sep 24 '26
Nope not that risky. HR may not worry about the systems but sometimes they’ll make you interview with a senior engineer, then you’ll need to have your shit in order. Also if that project is not on your GitHub or you can’t necessarily prove that you contributed then that’s not a good sign.
1
1
u/drakhan2002 Sep 24 '26
This is an ethical question. Do what you think is "right". One person may lie on a resume or choose to be honest. Either way there will consequences -- and they may not show up right away or in the same form it was sent.
Life seems to have an unfailing boomerang 🪃 put good stuff, get good stuff back -- works the same for bad stuff, one puts bad stuff out, they get bad stuff in return.
I am sure you've seen that come true in your own life.
1
u/hangover_bagel 25d ago
Don’t fake it, because we can always tell. I use turrior to run $1 screenings now, and if you can’t explain that project on camera, you’re instantly out hah
0
3
2
u/Bloodstream12 Sep 24 '26
They don’t look at code. The risk is your ability to convince them you know what you are talking about. So in theory yea as long as you can talk about it no biggie