Agents and the Future of Work
By 2030, agents will probably handle most routine knowledge work. The question is what humans will do instead.
History shows automation creates new categories of work even as it eliminates old ones. Agents are the latest wave.
Three skills that will matter most
- Knowing what to ask agents to do
- Reviewing agent work for errors
- Doing the parts agents cannot (relationships, ethics, creativity)
The big idea: Agents will reshape work. The lasting skill is being good at deciding WHAT should be done.
End-of-lesson check
15 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-builders-agentic-agent-future-jobs
Which sentence best captures the main idea of 'Agents and the Future of Work'?
- Agents and chatbots are the same thing in every way
- Agents should always run without limits or oversight
- Tools and goals are unnecessary for agent design
- By 2030, agents will probably handle most routine knowledge work.
Which of the following is part of 'A 2030 prediction'?
- Never log what the agent did
- Always run with no oversight
- Hide tool calls from the operator
- Knowledge workers spend more time on judgment, relationships, and creative direction. Agents handle the execution.
Which of the following is part of 'Three skills that will matter most'?
- Disable safety checks for speed
- Knowing what to ask agents to do
- Ignore cost when scaling
- Never log what the agent did
Which of the following is part of 'Review date'?
- Use the most expensive model regardless of fit
- Reviewed in 2026. Treat fast-changing product names, prices, availability, and policy details as examples to verify before use.
- Always run with no oversight
- Avoid taking any actions in the world
What is 'knowledge work' in this context?
- A core concept covered in Agents and the Future of Work
- A trick to bypass approvals
- A reason to skip all logging
- A way to disable the agent's tools
What is 'execution' in this context?
- A reason to skip all logging
- A core concept covered in Agents and the Future of Work
- A way to disable the agent's tools
- A trick to bypass approvals
What is 'judgment' in this context?
- A core concept covered in Agents and the Future of Work
- A trick to bypass approvals
- A way to disable the agent's tools
- A reason to skip all logging
What is the most useful framing for jobs in an agent-rich future?
- Nothing will change at work
- All jobs will vanish
- Tasks within jobs change first; new roles appear around designing, supervising, and auditing agents
- Only managers will have jobs
What should an agent's trace let you do after a run?
- Reconstruct each step, decision, and tool call so you can debug or audit
- Hide what the agent did from the user
- Replace the need for any tests
- Make the agent run faster next time automatically
An agent that costs $0.04 per task on average will run 10,000 times this month. Roughly what should you budget?
- About $400
- About $4,000
- About $4
- About $40
Why is it dangerous to give an agent access to your email and calendar without scoped permissions?
- It will refuse to work
- Scoped permissions slow the model down
- Broad access means a single misstep can send the wrong message or wipe events
- Scopes only matter for paid accounts
Why are clear success criteria critical when building an agent?
- They are required by law
- Without them you cannot tell whether the agent worked or guess
- They reduce the number of tokens used
- They make the agent sound smarter
Which signal best tells you an agent is stuck in a runaway loop?
- It finishes the task in one step
- It asks one clarifying question
- It returns a short summary and stops
- It keeps repeating the same tool call with no new progress
Before letting an agent take a destructive action, what is the safest default?
- Hide the action from any log
- Require explicit human approval for the specific action
- Approve once and let the agent repeat forever
- Skip approvals if the user trusts the agent
Why is logging every tool call an agent makes a baseline requirement?
- Logs are needed to debug, audit, and explain agent behavior to users
- Logs are only for legal teams
- Logs make the model run faster
- Logs replace the need for testing