- knowing what to prompt

- directing the model and knowing when its going off the rails

- verification

- setting up the right loops, harness, graphs around the models

economics still apply to hiring people. if all your competitors are using ai and there's market share to fight over and people still are a productivity positive vs. only ai, hiring will increase as we've seen recently with swes

▲

8cvor6j844qw_d6 28 minutes ago | parent | next [-]

Could agree with some of the points.

I noticed the newer batch of interns tends to have less mechanical coding skills but does well on understanding and planning on the design, DB design, etc.

▲

bogzz an hour ago | parent | prev [-]

Again though, these recommendations are so vacuous. If you already are a capable developer, then you can pick all of that up within a week. "Learn AI skills" is such a low effort reflexive response that I'd expect it from a non-technical executive, not from an HN commenter.

▲

vanuatu 19 minutes ago | parent [-]

You'd be surprised, I used to do a first round technical screen where we let the interviewee use any ai tool they want to build a simple api (and they can oneshot the problem if they just pasted it into any capable agent). I quite liked the problem, it was really a system design problem for senior+ but more algorithmic for junior/mid

The more senior the candidate the less they took advantage of the tools. Most commonly they would manually copy/paste error or syntax errors and then run out of time. One candidate only copy pasted his questions into google and used the AI overview

Junior candidates tended to be overly ai eager, a lot of them oneshotted the problem but were unable to explain any of the details

That being said I think 80% of the skills should come easily to a capable dev that is willing to put in the effort to learn and get used to managing agents. Building agents that perform work themselves is a lot harder (and still pretty unsolved)

	▲	bogzz 7 minutes ago \| parent [-]
		But I don't believe what you've said disproves my point. To me, it boils down to attitude, not so much aptitude when it comes to "AI skills" in this context. You even admitted that some of the solutions could be one-shotted by copying and pasting the problem. As for building agents that perform work themselves, in my opinion it boils down to understanding the problem space, isolating the key business logic, and determining what the pertinent requirements are. Kinda sounds like looping back around to software engineering skills IMO.