I spoke with a recruiter a few weeks ago and was somewhat surprised that a requirement for the position was experience building software with LLMs. Has this become the new norm in tech hiring?
Ask HN: Is vibe coding a new mandatory job requirement?
1–10 of 92 posts
Re: Ask HN: Is vibe coding a new mandatory job requirement?
#2In fact, they want 10 years of vibe coding experience
Re: Ask HN: Is vibe coding a new mandatory job requirement?
#3I'd say that a this point, if your job involves computers and you aren't at least familiar with how you can leverage AI tools, you're basically admitting that you really enjoy the art of working with one hand tied behind your back.
That's not vibe coding. Imagine if you were hiring a chef and a candidate came in who'd never used a stove. Sure, technically there are other ways to heat food, but it would be a bit odd.
Re: Ask HN: Is vibe coding a new mandatory job requirement?
#4We won’t hire anybody moving forward who doesn’t have hands-on agentic programming experience. We’re in the traditionally slower moving GovTech space. I have to imagine this is now a common expectation in many sectors.
Teams where I work can use Claude Code, Codex, Cursor, and Copilot CLI. Internally, it seems like Claude Code and Codex are the more popular tools being used by most software teams.
If you’re new to these tools, I highly recommend trying to build something with them during your free time. This space has evolved rapidly the past few months. Anthropic is offering a special spring break promotion where you can double the limits on weeknights and weekends for any of its subscription plans until the end of March.
Re: Ask HN: Is vibe coding a new mandatory job requirement?
#5We won’t hire anybody moving forward who doesn’t have hands-on agentic programming experience. We’re in the traditionally slower moving GovTech space. I have to imagine this is now a common expectation in many sectors. Teams where I work can use Claude Code, Codex, Cursor, and Copilot CLI. Internally, it seems like Claude Code and Codex are the more popular tools being used by most software teams. If you’re new to th…
Random question but what are some issues your facing with these ? I am just curious because everyone in my org uses them but act like it doesn't bring them any productivity gains probably they are scared to admit that it's actually been super helpful otherwise they are out of a job.
Re: Ask HN: Is vibe coding a new mandatory job requirement?
#6In fact, they want 10 years of vibe coding experience
hey 10 years for a junior position your going to need like 25 years for a senior level position.
Re: Ask HN: Is vibe coding a new mandatory job requirement?
#7I'd say that a this point, if your job involves computers and you aren't at least familiar with how you can leverage AI tools, you're basically admitting that you really enjoy the art of working with one hand tied behind your back. That's not vibe coding. Imagine if you were hiring a chef and a candidate came in who'd never used a stove. Sure, technically there are other ways to heat food, but it would be a bit odd.
lol what. This is more like a chef who reheats tv dinners and sometimes taste them in case theres mold
Re: Ask HN: Is vibe coding a new mandatory job requirement?
#8I couldn't imagine wanting to hire someone who doesn't use LLMs for coding unless they are bringing something very special to the table. It accelerates many coding tasks significantly. But you have to know the limitations to use them efficiently and that only comes with experience.
Re: Ask HN: Is vibe coding a new mandatory job requirement?
#9We do not interview for this nor care about it, despite using agentic and code complete tooling heavily. It's not a deep technical skill like C++ that requires years of hands-on experience. Spend a few weeks getting comfortable with Claude Code and you're probably at about parity with most devs.
That seems like sort of a red flag to me to have that as a job requirement.
Re: Ask HN: Is vibe coding a new mandatory job requirement?
#10I think AI assisted coding is a new job requirement, and I think the more I do it the more I’m convinced it’s going to wreck productivity. And it’s not because these tools aren’t as good as people say they are, it’s because they’re too good.
Everyone talking about vibe coding all your dependencies and the problem is that the people who are good with these tools and do get 50% or greater productivity benefits won’t be able to empathize with the people who are bad with these tools and create all the slop.
I think AI encourages people to take side quests to solve easy problems and not focus on hard problems.
That without domain expertise problems will compound themselves. But I dunno, I agree that they’re here to stay.