<p>The jump from working with a chatbot to having an agent that actually helps automate a process requires a real amount of work. <br>

<br>

Most companies will need to have dedicated people that are responsible for bringing automation to their teams, instead of leaving this up to every individual employee. Partly because the work is more technical than we imagine today, and partly because it’s just hard to do this as a side project.<br>

<br>

The job spec is to map out new workflows with agents, implement new systems to deploy agents, make sure the agent has all the right (up to date) context to work with, wiring up internal systems to connect to the agents, creating evals for the agents, figuring out where the human is in the loop, managing the system when there are new upgrades, helping with the change management of the existing business process, and so on.<br>

<br>

These jobs may come from IT or engineering, or live directly in the business function itself. They’ll be called different things depending on the company, and in some sense it’s the future of software engineering that you’ll see a huge growth of in non-tech companies.<br>

<br>

Most companies will have to be hiring for this now or in the future, and it’s another example of the kind of new jobs that will be created in AI.</p>

<hr/>

<blockquote>

<b>Harry Stebbings (@HarryStebbings)</b>

<p>

<p>What Role Does Not Exist Today But Will Be So Common in Five Years Time:<br>

<br>

"500K-1M jobs will be created for agent operators.<br>

<br>

This person will be somewhat technical. They will be deep in the AI world.<br>

<br>

They're gonna have to understand MCPs and CLIs and they are going to have to know how to write skills.<br>

<br>

It's going be this group of people that will know how to go into your marketing team or your legal team, or your operations team, or your life sciences research team and this is the person that is basically going to enable that function to get leverage from agents." <a href="https://nitter.net/levie" title="Aaron Levie">@levie</a><br>

<br>

Where is this right? Where is this wrong? <a href="https://nitter.net/jasonlk" title="Jason ✨👾SaaStr.Ai✨ Lemkin">@jasonlk</a> <a href="https://nitter.net/gregisenberg" title="GREG ISENBERG">@gregisenberg</a> <a href="https://nitter.net/amasad" title="Amjad Masad">@amasad</a> <a href="https://nitter.net/AnjneyMidha" title="Anjney Midha">@AnjneyMidha</a></p>

<a href="https://nitter.net/HarryStebbings/status/2046353968973160675#m">

<br>Video<br>

<img src="https://nitter.net/pic/amplify_video_thumb%2F2046240319830974464%2Fimg%2FPRku0eJBkHvNJjNT.jpg" style="max-width:250px;" />

</a>

</p>

<footer>

— <cite><a href="https://nitter.net/HarryStebbings/status/2046353968973160675#m">https://nitter.net/HarryStebbings/status/2046353968973160675#m</a>

</footer>

</blockquote>

为什么值得关注

能改变理解方式，而不只是重复常识；符合当前抓取需求；它提供了新的理解或解释，而不只是表面观点

来源：x，领域：projects，保留分：0.60