u/Sugarcaneer

I applied for a software engineering internship and figured I'd try the standard "be proactive" advice everyone preaches online. I sent a polite message to the recruiter asking if they had any tips for standing out among applicants. I was expecting either complete silence or a standard canned response about checking the portal, but

I definitely wasn't expecting this level of hostility.

https://preview.redd.it/hrsc8csr73kh1.png?width=279&format=png&auto=webp&s=b492c77abe9dcc73efb1a1faf85b0d5627afcefc

they immediately hit me with "3000+ applicants, my advice? Hope." When I tried to roll with it and just asked about a timeline for hearing back they told me "if not, you'll figure it out," and then edited their last message mid-conversation to basically tell me "never mind, save yourself the trouble."

I get that recruiters are drowning in applications right now but the absolute lack of basic professionalism is insane. To tell an entry-level candidate to "hope" and then soft-reject them over LinkedIn messages within two hours of applying is a whole new level of cooked. Is this just the new norm for tech hiring now?

(long post ahead)

I think I reached a breaking point yesterday.

I’ve been watching everyone in my cohort spend half their day panicking about Claude and Cursor taking all the junior roles, and the other half using those exact same tools to copy-paste their way through our weekly assignments. The prevailing narrative on Reddit is that "AI killed the entry-level market," but yesterday I had a realization that’s probably going to rub a lot of people the wrong way:

AI isn't taking junior jobs because it's replacing software engineers. It's taking junior jobs because most bootcamp grads aren't actual engineers, they're syntax translators.

Yesterday, I watched someone in my group try to build a custom auth flow with role-based permissions using pure prompt engineering. When the LLM hallucinated outdated syntax, created circular dependency errors, and handed back a massive security flaw, they were completely stuck. They spent three hours typing "fix this error" back into the chat box over and over again, completely helpless, because they never actually learned how state management, HTTP requests, or database schemas work under the hood.

That was my turning point. I realized that if your entire skill set is taking a user story and writing basic CRUD boilerplate, you aren't competing with mid-level devs, you're competing with a hyper-fast autocomplete machine. And you will lose every single time.

The contrarian truth that nobody paying $15k for a coding bootcamp wants to admit is that AI is setting a higher bar for entry, not a lower one.

If an AI can spit out boilerplate code in 5 seconds, our value was never supposed to be "knowing how to write a syntax-perfect for loop." Our value has to be knowing how to architect systems, read documentation, debug subtle edge cases, and verify that the LLM isn't hallucinating catastrophic bugs into production.

The market isn't dead because of AI; the market is dead for people who "vibe code" their way through a 12-week program without understanding core computer science fundamentals. If you can't trace execution line-by-line or explain why a database query is failing without asking ChatGPT, you aren't a developer, you're just a middleman pasting broken code between VS Code and an API prompt.

I know people are going to downvote this and say "AI makes us 10x faster, why wouldn't we use it?" and I get it. Tools are great. But using AI as a crutch before you even know how to write a clean, unassisted function by hand is pure career suicide right now.

Am I being way too harsh here, or are you guys seeing the same thing in your cohorts? Are people actually learning how software works, or are we just graduating a wave of prompt engineers who can't debug a real codebase when the AI fails?

Why does a React-based portfolio site feel so slow and laggy without serious investment in optimization when Quake 3 could run smoothly at 60fps on a pentium II from the 90s.

We are now 30 years later and anything more than a toy project built by a bootcamp grad is a laggy mess by default.

inb4 skill issue bro: Well, it shouldn't be this difficult.

inb4 you need a better pc bro: I have M4 pro 48GB

i was so incredibly burnt out from cold-messaging random strangers and getting ghosted by recruiters that i just couldn't take it anymore. linkedin has become a total wasteland of toxic positivity and people bragging about their new jobs, its exhausting. it feels like you're just screaming into a void of corporate bots. so last tuesday i finally shut my laptop, turned off my job alerts, and forced myself to go to a local developer meetup in my city even though my anxiety was telling me to stay home and just grind out more applications.

the difference was night and day honestly. no corporate bs or fake networking pitches, just a bunch of regular people eating pizza and talking about actual software. i ended up chatting with this senior backend dev for like an hour about some geometric mapping and spatial data scripts i've been messing around with for a technical project. instead of the usual "go apply on our portal" brush off you get online, he was actually giving me genuine advice and drawing out database architecture ideas on a napkin. it was so refreshing to just be viewed as a human being who likes solving complex math and coding problems, rather than just another line of text in an ATS filtering software.

if your feeling completely drained and hopeless looking at the online job market right now, please do yourself a favor and find an in-person tech event nearby. the digital space is totally broken and oversaturated, but there are still real people out there who want to help you out if you just show up and talk to them.

I need to get something off my chest because I am starting to feel like a total fraud. I have been using tools like Cursor and GitHub Copilot to help build out my portfolio projects, and on the surface, it looks like I am absolutely flying through my code. The terrifying reality check happened to me a couple of days ago when I tried to do a basic coding challenge on a clean screen without any AI extensions turned on. I completely froze up. I struggled with basic syntax and couldn't even map out a multi-step array method without getting confused about where the data was going.

I want to know how you guys are actually balancing this because I don't think completely banning AI tools is realistic in 2026 when every company expects you to use them for productivity. Do you force yourself to turn them off entirely during the week and only use them on weekends, or do you have a strict rule where you write everything by hand first and only use the AI for debugging errors? I need to figure out a healthy boundary where these tools act as an accelerator rather than a crutch, because right now I feel like a professional prompt generator who doesn't actually know how to code.

If you are graduating from a bootcamp right now and submitting a portfolio filled with the exact same e-commerce apps, weather widgets, and Netflix clones as everyone else in your cohort, your resume is getting buried in the corporate black hole. The absolute fastest way to bypass this filtering noise and stand out in the current market is to prove you can already read massive, unfamiliar codebases and collaborate with standard engineering workflows by contributing to Open Source Software (OSS).

Once you have the fundamental Git workflows down, you can dramatically level up your engineering maturity by targeting full-scale, active web applications and devops infrastructure projects that hiring managers actually respect. Contributing to welcoming communities like Habitica (a gamified task manager built on a MongoDB, Express, Vue, and Node stack) or Mattermost (an enterprise chat app using React and Go) gives you hands-on experience handling complex state management and writing code that must pass rigorous automated testing pipelines. If you really want to differentiate yourself from other bootcamp grads, skip the frontend entirely and contribute to NotHarshhaa/DevOps-Projects to show you understand critical production-level concepts like containerizing full-stack web apps with Docker and configuring automated CI/CD validation pipelines via GitHub Actions.

If your portfolio consists entirely of frontend applications deployed on simple static web hosts, you are missing out on the exact infrastructure skills that hiring managers use to filter candidates. While it is incredibly easy to connect a GitHub repository to a static provider and get a clean URL, this automated loop completely shields you from the messy realities of modern software architecture, such as managing persistent server processes, configuring firewalled database connections, and handling environment variables. Transitioning your projects to cloud platforms like Render or Railway acts as the perfect next step because these services force you to understand how an application compiles inside a Linux container, how to link services via secure private networks, and how to read live runtime log streams to debug a crash independently.

If you want to maximize your resume value and gain a massive competitive advantage over other entry-level applicants, taking the time to deploy a project directly onto a traditional cloud provider like AWS is the ultimate move. Most junior candidates panic when looking at raw cloud primitives, so showing a hiring manager that you can confidently deploy, secure, and monitor a containerized full-stack application proves you understand the entire software lifecycle and instantly elevates you above the competition.

If you have been applying to jobs on LinkedIn or Indeed lately, you already know the system is fundamentally broken because new AI auto-apply tools allow job seekers to flood portals with thousands of applications within hours. This overwhelming noise forces recruiters to pull listings down immediately or use brutal keyword filters, meaning your carefully crafted resume is likely trapped in a digital black hole. To find authentic vacancies, you need to abandon public aggregators entirely and apply directly through the internal careers page of corporate websites, which often use completely separate tracking queues for high-intent candidates.

Hiring managers are drowning in low-quality public applications, they are increasingly hiding their best roles in tight-knit, high-friction industry spaces where bots cannot follow. You can uncover these high-value vacancies by joining specialized Slack channels, professional Discord servers, or by running precise social media search queries for active hiring updates posted directly by team leads. Once you locate a legitimate opening, do not just submit your application and pray for a response. Track down the specific department head or team leader who would actually be your direct boss, and reach out with a brief, highly personalized message about their recent projects or operational challenges. By showing up to ask for their advice and perspective on the team's direction, you turn yourself into a familiar human face and completely bypass the broken gatekeeping algorithms.

I have officially hit the 5-year mark as an assistant, and I feel like I've run straight into a brutal professional wall where leadership only views me as "essential support" rather than a strategic asset. Right now it reads like a boring grocery list of daily chores such as scheduling, tracking inventory, and managing data entry. I know our daily operations, bottleneck areas, and client pipelines inside and out, but I am completely stuck on how to reframe that deep institutional knowledge so that external hiring managers see someone capable of managing a team or driving operations, instead of just someone who passively executes orders.

what should I do to make recruiters see me as a high-level strategist?

I’ve officially hit the 5-year mark as a sales assistant and I feel like I've run straight into a brutal professional wall. My main purpose for writing this is to get some realistic advice on how to pivot, because I'm completely stuck. I know our floor operations, inventory, and client pipeline better than almost anyone else on the team, yet I keep getting passed over for promotions. I’m starting to worry that I’ve become too good at my current job, and leadership just views me as "essential support" that they can't afford to move, rather than a leader who can drive real revenue.

For anyone who successfully broke out of a long-term assistant or retail floor role and transitioned into corporate sales or upper management, how did you do it? What was the exact project or conversation that finally made leadership stop looking at you as an assistant and start seeing you as a leader?

the discussion around AI in the coding community is driving me completely crazy, and I'm genuinely trying to figure out how to adapt my daily workflow before I fall behind. My main purpose for writing this is to get a realistic reality check from people actually working in the industry, because the internet is stuck between "software engineers are going extinct" and "AI is just a glorified autocomplete." From what I'm seeing, tools like Cursor and Copilot are generating a massive chunk of the code landing in production, but at the same time, it feels like code quality and developer trust are tanking because these models spit out so many subtle bugs, duplicates, and security vulnerabilities. I often find myself spending more time debugging a hallucinated function than it would have taken to just write it myself, and I feel completely lost on how to navigate this new landscape.

For the devs who have successfully integrated advanced agents into their daily routine, how are you balancing manual coding with AI review, and what specific architectural skills should I be prioritizing to stay highly valuable?

I am beginning a regular full-stack web development bootcamp this Monday. My real aim, though, is to enter the field of AI engineering and I genuinely have no idea how to connect those dots. I'm mentioning this because the course only covers conventional subjects like JavaScript and React that seem very distant from working with large language models. As an absolute novice, I have no clue how to begin changing direction.

From the deep rabbit holes I've explored, it seems like AI engineering is mainly software development applied to pre-existing models and not really about complex research math. So, my tentative plan is to essentially divert my own assignments. Rather than creating typical weather apps, I will try integrating LLM APIs instead. When we start learning SQL, I'll also attempt understanding vector databases such as Pinecone concurrently - even though I fear it might be too much for me handle. What I'm gradually realizing is that while fundamental coding practices remain same; one needs to forcefully manipulate backend into AI data workflows on their own. If someone is presently working in AI, how would you approach a fundamental web development bootcamp if starting again from zero? Any help would be great.

writing this because i see so many people thinking you need to drop $15k on a bootcamp or spend 4 years in college just to get a foot in the door. watched tim kim's breakdown on how he went from a college dropout to a hired software dev in 4 months completely self-taught, and the blueprint is surprisingly simple if you cut out the noise.

you don't need a million different courses. he literally just used three core things: freeCodeCamp to get the baseline coding reps down, a class called "learning how to learn" on coursera to fix his actual study habits, and watchandcode for deep javascript foundations. find a couple high-quality free resources, fix your learning mechanics so you don't burn out, and start writing real code immediately.

making this post because i see so many grads accept the very first number thrown at them out of pure fear. you think because you have zero professional experience, you have zero leverage. that's a total myth. the second a company extends an offer, the leverage shifts to you. they just spent weeks interviewing dozens of people and chose you. they aren't going to pull the offer just because you ask a polite question.

the mistake is making it personal. never say "i need more money because my rent is high." instead, anchor it to market data and gratitude. you want to say something like: "i’m incredibly excited about the team, but based on my research for similar entry-level roles in this area, the market average is closer to [X]. is there any flexibility to get closer to that number?" the big takeaway is that negotiation is just a standard corporate script. worst case they say there's no budget and the original offer stands. best case you get a 5-10% bump for a 30-second email. you lose nothing by asking.