Live data from Hacker News

Ask HN: Is vibe coding a new mandatory job requirement?

news.ycombinator.com

51–60 of 92 posts

Re: Ask HN: Is vibe coding a new mandatory job requirement?

#51
post #5
post #4

We 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.

> Random question but what are some issues your facing with these ?

I’ve seen some folks who are quite productive with these tools, but there is a lot more slop too. On my team on same the code base you see two different team members producing vastly different results.

Re: Ask HN: Is vibe coding a new mandatory job requirement?

#52

Earlier quoted context omitted.

This is personal. I wouldnt like to work with someone who is creating sound effects or rap songs etc. Every sound is some piece of pain. Doing html-web stuff is more useful. Internet is a good thing. Noone knows how the internet works still. Sound-movie makes it understanding even more difficult. It is the click sound of browser originally.

So when you bring this up with your coworkers, do they tell you just what to do with or where to put your value judgments of their hobbies?

Well the rap and audio plugins are created by some people. It's ok, but I am not ok with it. Having a musician career on Spotify is a lie. It is only vibe draggingdrop or code. I prefer my coworkers doing html-programming work kind of vibe coding.

Re: Ask HN: Is vibe coding a new mandatory job requirement?

#53
At my company, we ask everyone in the hiring process about how they have used any kind of agentic coding tools.

We're not concerned about hiring for the 'skill' of using these things, but more as a culture check - we are a very AI-forward company, and we are looking for people who are excited to incorporate AI into their workflow. The best evidence for such excitement is when they have already adopted these tools.

Among the team, the expectation is that most code is being produced with AI, but there is no micromanager checking how much everyone is using the AI coding tools.

Re: Ask HN: Is vibe coding a new mandatory job requirement?

#54
post #51
post #5

Earlier quoted context omitted.

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.

> Random question but what are some issues your facing with these ? I’ve seen some folks who are quite productive with these tools, but there is a lot more slop too. On my team on same the code base you see two different team members producing vastly different results.

> On my team on same the code base you see two different team members producing vastly different results.

And if they use LLMs to assist, does the same thing happen?

Re: Ask HN: Is vibe coding a new mandatory job requirement?

#55

The framing of "is vibe coding a job requirement" conflates two things: the skill of coding-by-prompting, and the skill of knowing what you need to build. The second one is genuinely underrated. Knowing your problem well enough to describe a working solution, the inputs, the logic, the outputs, who uses it, is hard to automate. Generating the actual app from that description is increasingly not. We've been using Lyzr…

You're describing two different jobs though, "what you need to build" is supposed to be done by the army of "product managers/owners" or whatever they're called, rather than letting the programmer do that, and the product managers/owners whole reason for existing is figuring out what to build, what not to build and how the thing should work.

If you end up having engineers do the work of product people, you'd end up with the typical "engineered mess" that might be very fast, and lots of complicated abstractions so 80% of the codebase can be reused, but no user can make sense of it.

Add in LLMs that tend to never push back on adding/changing things, and you wend up with deep technical debt really quickly.

Edit: Ugh, apparently you wrote your comment just to push your platform (https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu...) which is so trite, apparently HN is for people to push ads about their projects now...

Re: Ask HN: Is vibe coding a new mandatory job requirement?

#56
Here’s another question. Has anyone been able to get an agent to produce reliable high quality code?

My first experience with it was a year ago and the tests it produced were so horrendously hard to maintain that I kinda gave up, but I imagine that things have gotten a lot better in the last year.

Re: Ask HN: Is vibe coding a new mandatory job requirement?

#57

The framing of "is vibe coding a job requirement" conflates two things: the skill of coding-by-prompting, and the skill of knowing what you need to build. The second one is genuinely underrated. Knowing your problem well enough to describe a working solution, the inputs, the logic, the outputs, who uses it, is hard to automate. Generating the actual app from that description is increasingly not. We've been using Lyzr…

I admit that vibe coding was kind of a clickbaity way to frame this, but I couldn't think of a better way to describe it. That might just underscore my ignorance in this domain.

One problem I personally have here is that I write code as a way to reason through and think about a problem. It's hard for me to grasp the best solution in a space until I try some things out first.

Re: Ask HN: Is vibe coding a new mandatory job requirement?

#58

The framing of "is vibe coding a job requirement" conflates two things: the skill of coding-by-prompting, and the skill of knowing what you need to build. The second one is genuinely underrated. Knowing your problem well enough to describe a working solution, the inputs, the logic, the outputs, who uses it, is hard to automate. Generating the actual app from that description is increasingly not. We've been using Lyzr…

> + multi-agent backend

Does that mean you need AI subscriptions just to run your backend? That explodes costs even more than opaque cloud pricing. Sweet!

Re: Ask HN: Is vibe coding a new mandatory job requirement?

#59

Earlier quoted context omitted.

> We won’t hire anybody moving forward who doesn’t have hands-on agentic programming experience. This doesn't make a lot of sense to me even as someone who uses agentic programming. I would understand not hiring people who are against the idea of agentic programming, but I'd take a skilled programmer (especially one who is good at code review and debugging) who never touched agentic/LLM programming (but knows they wi…

I suspect it’s not about agentic coding being a special skill, and more about why a competent programmer wouldn’t have tried it by this point, and whether that is a sign of ideological objections that could cause friction with the team. Not saying I agree with that thinking, but I definitely see why a hiring manager could think that way.

> why a competent programmer wouldn’t have tried it by this point

What does one have to do with the other? Since when is following every fad a prerequisite for competence?

Re: Ask HN: Is vibe coding a new mandatory job requirement?

#60
post #59

Earlier quoted context omitted.

I suspect it’s not about agentic coding being a special skill, and more about why a competent programmer wouldn’t have tried it by this point, and whether that is a sign of ideological objections that could cause friction with the team. Not saying I agree with that thinking, but I definitely see why a hiring manager could think that way.

> why a competent programmer wouldn’t have tried it by this point What does one have to do with the other? Since when is following every fad a prerequisite for competence?

Don't shoot the messenger, I'm just telling you how some hiring managers might think, not endorsing the opinion and it's definitely not something I consider in my hiring.

I will say it's a little weird to frame it as "every fad" though. Do you really not see any net new or lasting utility for software engineering in AI tools? If not then more power to you, but software engineering being a fast-moving field where there are (fair or unfair) expectations to keep up is nothing new.

Post reply on HN