u/SetLoose4928

Did I completely torpedo my standing here from my manager?

I had my mid-year review yesterday. I’ve been grinding non-stop for months taking on extra tickets generally carrying a massive workload. I knew I deserved a good review but I was also running on pure caffeine and sheer burnout from working 50+ hour weeks.

My manager was listing off my recent deliverables and we had this conversation

Manager: "How do you feel about your overall impact on the team so far?"

Me: "Bringing me onboard was the best decision this department made all year."

The words left my mouth before my brain could even register what I was saying.

There was an agonizing five-second silence. He just kind of blinked leaned back in his chair and went "Well... confidence definitely isn't an issue with you." He chuckled and moved the conversation along but I’ve been sweating bullets ever since.

Part of me knows I’ve been delivering but another part of me feels like I just permanently branded myself as an arrogant unhinged weirdo in front of leadership.

I need some real talk from anyone who’s been through this because I am currently spiraling. After being unemployed for almost a year following a layoff, my resume was going straight into a black hole with zero callbacks, and I knew the massive gap was killing my chances.

Out of pure desperation, I extended the end date of my last job on my resume to make it look like I was still currently employed. It actually worked, I blew through three rounds of interviews and just signed an offer letter today.

I know I brought this stress on myself and shouldn't have lied in the first place, but I was at my wit's end trying to survive in this market.

I'm torn between putting my actual real dates on the background check form, sticking to the lied dates and praying, or coming clean to the recruiter before the report comes back.

Has anyone been in this exact situation and survived the background check process, or am I completely screwed?

I'm completely freaking out about whether putting my real dates on the portal will immediately trigger a discrepancy flag with HR, or if putting the fake dates on the form will fail the third-party audit altogether.

I’ve been working remotely for over a year and recently let my discipline slip. Yesterday, my manager messaged me asking why activity tracking logs showed multiple hours of complete inactivity over the past few weeks, flagging a major mismatch between my logged hours and actual keypresses/mouse movement.

I panicked and gave a weak excuse about doing "offline research," but HR just scheduled a meeting on my calendar for tomorrow to review "remote work compliance."

I know I messed up big time and lost their trust. Moving forward into tomorrow's meeting, should I fully own up to my mistake and apologize, or stick to my original story? Also, if this ends in immediate termination, how should I handle explaining this departure to future employers?

Can someone explain to me why everyone still treats a $100k salary like it’s this magical milestone where you’ve finally "made it" and can live comfortably?

I’m looking at a hybrid offer right now ($100k base, 3–4x a month in-office in a major metro area, rest WFH), and when I break down the actual numbers, I feel like I'm taking crazy pills compared to what people here claim.

Everyone insists $100k as a single person with no kids is "more than enough to live comfortably," but after taxes, absurd rent in any decent city, maxing out basic retirement savings, health insurance, groceries, and student loans, you’re basically left with just enough to eat out twice a week and save a couple hundred bucks.

That’s not "living comfortably", that’s just baseline survival with a slightly nicer apartment.

If comfortable means actually building real wealth, traveling without pinching pennies, and having actual financial freedom, $100k isn't even close to cutting it anymore in a metro area.

how are people out here actually pulling $500k to $800k+ a year in these vague corporate executive roles?? i was talking to this VP at a tech firm last week who makes absolute insane money, and it literally blew my mind. everyone on reddit always says "it's just pure nepotism" or "they got lucky with stock options," but watching how this person operates made me realize that cope is completely wrong.

you're literally being paid emotional hazard pay to take the fall when shit hits the fan. if a $100k worker messes up, they get a slap on the wrist or put on a PIP. but if a $500k exec makes one bad call or misses quota twice, they get fired on a random tuesday with zero hesitation because they're directly responsible for tens of millions of dollars. people say they want $500k, but they actually just want $500k for doing $100k effort with zero stakes and perfect work-life balance.

what do these hyper-high-paying roles even entail on a day-to-day basis for those of you who have seen them up close? is it literally just pure risk management, organizational politics, and living with a target on your back 24/7, or is there something else I'm missing here?

Let's be completely real here. If you vibe code - like truly vibe code - as a student in a bootcamp, it might be time to find a new home.

By vibe coding, I mean genuinely writing little to no code by hand and letting your AI do it instead. Pretending to be an orchestrator while the AI does all the real engineering. Not struggling through a problem, and instead mistaking speed for competence.

Most of the people that I know who do this say that it's to "get comfortable with agentic coding". But the result is catastrophic: You're paying companies to do the job that you want to get paid to do.

The standard defence of industry professionals is that AI can't be a real software engineer because the experience of building things on your own gives you judgement and skill that are impossible to replicate with AI. Judgement and skill that can even be used to guide AI agents if willing. But if you spend your 12 weeks skirting around experience by outsourcing to an AI, you have no value. There is nothing that you have that an AI doesn't. You don't build the judgment, you don't build the experience, you don't build the intuition for what does and doesn't smell.

Even worse is the fact that you lose the ability to make new things. AI isn't actually able to do something that has never been done. It can pretend it does by hacking together a bunch of stuff that has been built, but this isn't true ingenuity and leads to significant technical debt. You lose the most valuable human resource in this field: ingenuity.

If you're vibe coding in a bootcamp, you are genuinely utterly cooked. It is impossible to justify your value to this industry.

I feel like bootcamps sell us this beautiful lie that being a software engineer means sitting in front of a blank screen, running a clean installation, and building gorgeous new apps from the ground up. we get so addicted to that fresh repository feeling where everything makes sense because we wrote every single line of it. but i was talking to a senior engineer the other day and he totally reset my expectations. he told me that in the real world, junior devs almost never build anything from scratch. instead, your handed a massive, terrifying legacy codebase that was written five years ago by some dev who left the company, and its just completely full of undocumented hacks and weird logic.

Companies don't pay you to rebuild their entire multi-million dollar platform every time they bring on a junior, they pay you to maintain and fix bugs in the stuff that already exists. the actual day-to-day job is like 80% reading confusing spaghetti code and only 20% actually writing new stuff.

i went on github, found an older open-source repo with a bunch of open issues, and just forced myself to try and read through the source files to figure out how the components even connect. it is way harder than building my own clean stuff and honestly gave me a massive headache, but it feels a whole lot more realistic. are any of you guys actually practicing reading other peoples messy code, or are we all just trapped in tutorial purgatory building perfect apps that don't match reality??

like the sheer panic of dealing with your first massive merge conflict where git tells you that you and three other devs broke the same file is enough to make me wanna throw my laptop. and dont even get me started on git rebase... i still don't fully get how it works and the thought of accidentally messing up a shared main branch gives me actual hives. then you gotta deal with senior devs absolutely roasting your code in pull request reviews, and watching your build fail in some automatic CI/CD pipeline because you forgot to run a linter or write a unit test. its a whole different level of stress that you just never get when your just coding by yourself in your bedroom.

I feel like we spend 99% of our time learning syntax and framework logic, but almost zero time learning how to actually collaborate inside a real software engineering workflow. how are the rest of you guys prepping for this side of the job before your first day? are you doing mock group projects, trying to contribute to open source, or is there a tool/resource that actually simulates what its like to work on a team? because right now, the coding part feels fine, but the actual workflow part has me absolutely sweating.

I am so incredibly tired of looking at "Entry-Level" job descriptions only to scroll down to the qualifications and see that they are demanding 2 to 3 years of commercial experience. It is the ultimate catch-22 that is paralyzing the job market right now because you literally need a job just to get the experience required to apply for a junior position. It makes you feel completely defeated before you even submit your application, but after talking to a few tech recruiters and hiring managers, I realized that this entire trap is almost always a massive bluff. It is not a hard, unyielding rule, but rather an idealized wishlist designed to scare away people who lack confidence.

To actually beat this filter, I completely changed how I format my resume, and it has been an absolute game-changer for getting call-backs. Stop separating your bootcamp apps or personal projects into a sad little section at the very bottom of the page because that instantly flags you as having zero real experience to an automated tracking system. Instead, bundle your capstone projects, open-source contributions, and any freelance or contract work under a single, unified header called "Software Engineering Experience." Frame your projects like real-world client products by quantifying your results, focusing on database optimizations, and detailing how you handled live traffic. If your resume looks structurally professional and shows you can operate like a real developer on day one, you will pass the automated gatekeepers, and a real human manager is not going to care about the exact month you graduated.

You finish your bootcamp or degree, stare at your GitHub portfolio, and open LinkedIn only to find "entry-level" roles demanding three to five years of experience in advanced tools like Docker, AWS, and Kubernetes. This leaves you trapped in a brutal experience paradox where you cannot land a job without experience, but you cannot get experience because no one will hire you. The reality of the current market is that "junior" has been completely redefined by corporate environments; it now essentially means a senior engineer who costs the price of an intern and doesn't complain about the workload. Recruiters pack job descriptions with a massive laundry list of buzzwords like microservices and cloud architecture, even though the actual day-to-day work often just involves fixing broken layout spacing or patching minor bugs on a legacy codebase. To make matters worse, companies shield themselves from the massive flood of automated AI applications by forcing candidates to dance through a multi-stage boss fight of technical assessments and extensive take-home projects, only to ghost them at the finish line.

To survive this environment, you have to stop playing the numbers game and start treating job descriptions as corporate wish lists rather than strict checklists. Stop wasting your energy on public job board portals where thousands of bots have already applied, and instead target mid-sized companies directly by reaching out to engineering leads for genuine human conversations about their actual architecture. Focus your portfolio on showing that you understand the "boring" production fundamentals like automated testing and basic containerization because proving you are a safe, independent hire who won't break a live server is the absolute fastest way to bypass the resume black hole and get noticed.