Hot take on Jensen Huang’s job vs. task distinction and what it actually means for engineers
The Job Is Not the Checklist
Jensen Huang said something recently that I keep coming back to. Not because it was surprising, but because of how little softening was in it.
“If your job is the task, then you’re very highly going to be disrupted.”
Not might be. Very highly going to be. That phrasing matters. He wasn’t offering a warning with an escape hatch. He was describing something already in motion.
And then, almost in the same breath, he handed over the prescription: “If your job’s purpose includes certain tasks, then it is vital that you go learn how to use AI to automate those tasks.”
That distinction between a job and a task sounds obvious until you realize how many people have spent their entire career collapsing the two together.
What Engineers Are Actually Doing All Day
I’ve built enough AI systems and worked alongside enough engineering teams to have a pretty clear picture of where time actually goes. And it isn’t pretty.
A meaningful chunk of most engineers’ days is mechanical. Boilerplate code that follows the same pattern every time. Ticket triage that amounts to sorting by priority and assigning to queues. Status updates that pull from the same three data sources. Documentation that mirrors what the code already says.
That work isn’t engineering. It’s data entry with a compiler. And Huang’s point is that this is exactly what dislocation looks like. Not layoffs announced in a press release. Tasks quietly becoming automated, one by one, until the person doing them has to justify what’s left.
The question engineers should be asking isn’t “will AI take my job?” The question is “what percentage of my week could be written as a step-by-step procedure?” If the answer is more than 40%, the math is not in your favor.
🔧
The Automation Asymmetry
Here’s what I think most people get wrong about this moment. They treat automation as something that happens to them. Huang is describing something you can do on purpose.
The engineer who automates their own boilerplate generation doesn’t lose work. They recapture hours that were previously spent on execution and redirect them toward design, architecture, the decisions that actually require judgment. The person who hands the checklist to the machine first doesn’t get replaced. They get a compounding advantage over everyone still doing it by hand.
Huang was explicit: “It is the case that the technology will dislocate and will eliminate many tasks. And because it will automate it.” No hopeful footnote attached. Dislocation is the word he used. Tasks get eliminated. That part is settled.
The variable is whether you eliminated them yourself, on your own timeline, and kept the interesting work. Or whether someone else eliminated them for you.
What Actually Stays Human
I’m not going to pretend the line is perfectly clean. It isn’t. But there is a real distinction between executing a process and owning the judgment around it.
Judgment about what to build. Context about why a system behaves a certain way under load. The instinct to recognize when a technically correct answer is wrong for the situation. The ability to sit in a room with a product team, understand what they’re actually worried about, and translate that into something buildable.
None of that is a checklist. All of that is the job.
The tasks inside the job? Those are increasingly fair game. And the engineers I’ve seen thrive in the last two years are the ones who drew that line clearly for themselves early, gave the repetitive work to their tools, and spent the freed time going deeper on the parts that required them specifically.
🧠
Where This Leaves You
Huang’s framing is useful precisely because it doesn’t offer false comfort. The window to get on the right side of this is open. It is closing. And his position at Nvidia, watching how compute gets deployed at scale across every industry, gives him a vantage point that most commentators don’t have.
I’d take the warning seriously. Not as a reason to panic, but as a reason to spend one afternoon this week auditing your own workflow. Write down what you actually do. Mark the things that follow a pattern. Then ask yourself honestly: is this judgment, or is this a checklist?
The answer will tell you more about your career trajectory than any performance review.
Sources
