Contact Us
Questions, comments, ideas for future content? Contact us below.
Daring people to quit is a hell of a lot cheaper than laying them off. Consider 2 trends in tech:
1. Return to Office Mandates…among people who were both hired remote and in completely different cities.
Before I start, I do want to mention that “everyone should be remote” takes are probably the most egregious pandering content out there. Office work has advantages. Remote work has advantages. And it’s all situational depending on industry, roles, experience level, etc.
Let’s admit that like adults and move on.
But there’s something different about hiring someone full remote, who doesn’t even live in the same city, then forcing an office return. Especially if that hire was made in the last year. And someone upended their life by quitting another job to make the switch.
Amazon pulled this move a couple of weeks ago. A survey by Blind (here) showed 91% of employees were pissed about it.
The part that made me laugh: “The conglomerate said that it would make exceptions to its RTO policy for family emergencies, workers with sick children, and coding assignments requiring isolation.”
So 2010 selling points are making a comeback! Awesome.
It’s pretty obvious that for Amazon, this is a feature, not a bug. They want people to quit. Because they don’t have to pay severance if they do.
2. Quotas for salespeople in some SaaS firms are absurdly off the mark. By design.
I spoke to a friend in sales management last week. Publicly traded org. He grew his account base by 140% compared to the previous year. And he’s at 40% of quota.
His entire team – all of whom have always been over 100% of quota every previous year – have grown their accounts 80%-130% and are in the 30-40% of target number as well. The response from their leadership is along the lines of “whoop, looks like we miscalculated, our bad” without any actual change.
If you peel back the layers, it’s another ‘feature not a bug’ situation: if salespeople don’t hit their quotas, they don’t get paid. The financial analysts *love* it when you grow revenue without increasing costs. And as you can imagine, that entire sales team is looking for new roles.
Asking around, I know several other people in different companies in similar situations. This is more the rule than the exception.
To be clear: this isn’t every company. Not all companies trying to bring people back to office are daring people to quit. Not all companies changing their comp plans are trying to juke their EBITDA numbers at the expense of their employees.
👉But workers are becoming increasingly jaded and distrustful.
These moves are not subtle. Everyone is becoming more skeptical of the next job they interview for, even with companies who keep everything above board.
The key to attracting talent in the next few cycles will be how adept you are at addressing corporate transparency issues that may have nothing to do with you.
Partner at Hirewell. #3 Ranked Sarcastic Commenter on LinkedIn.
Over the last year, hiring teams have started seeing a wave of new job titles pop up across tech, sales, and operations.
Some are legitimate new roles.
Others are existing jobs with a slightly different name.
And many of them have one thing in common: AI is suddenly part of the job description.
From Go-to-Market Engineers to AI Specialists, companies are experimenting with new roles as they figure out how automation and AI fit into their teams.
But most of these positions aren’t entirely new. They’re evolutions of existing roles.
One role that is gaining traction is the Go-to-Market Engineer.
Depending on who you ask, it is either:
In practice, it is a bit of both.
As Matt Tokarz recently pointed out after closing a search for an Outbound & Go-to-Market Specialist, the role looked very different from traditional RevOps. The focus was not reporting or CRM hygiene. It was building prompts, leveraging tools like Clay and Smartlead, and enabling SDRs and AEs with backend insights to accelerate pipeline growth.
Instead of traditional RevOps work like reporting and CRM management, the focus was on:
The goal was not simply managing sales data. It was accelerating pipeline generation through automation.
One trend is becoming clear. Companies are not replacing entire departments with AI.
Instead, they are changing how existing roles operate.
Sales teams still need pipeline.
Marketing teams still need content.
Engineering teams still need to build software.
The difference is that employers now expect candidates to use AI tools as part of their workflow.
As Zac Colip noted during the discussion, we are currently in a transitional phase where companies are labeling roles with “AI” as they experiment with how the technology fits into teams.
But that may not last forever.
Right now, AI still feels new enough that companies highlight it in job titles.
But eventually, AI will likely become a baseline expectation, not a specialty.
Think about it like cloud technology or data analytics.
At first, companies hired “cloud specialists.” Now most engineers are expected to understand cloud infrastructure.
The same shift will likely happen with AI.
Instead of hiring “AI-enabled marketers” or “AI engineers,” companies will simply expect employees to know how to work with AI tools.
One challenge with these emerging roles is simple: there aren’t many candidates with real experience yet.
Many of these positions didn’t exist two years ago.
In one recent search, we started looking for a candidate locally in Chicago. Eventually we expanded nationwide because the pool of people with relevant experience was extremely limited.
This is a common issue with emerging roles:
That gap will likely persist for the next few years.
Another noticeable shift is that roles are becoming more hybrid.
Instead of hiring for narrow responsibilities, companies are combining multiple functions into one position.
As Matt Mulcahy highlighted, one example is the rise of Forward Deployed Engineers, a model popularized by Palantir.
These engineers:
What used to involve several roles, including product managers, engineers, and solution architects, can now sometimes be handled by one person. AI development tools are part of what makes this possible.
Not every industry is moving at the same pace.
As Ashley DuBois pointed out, some sectors, such as transportation, are applying AI to specific workflows like load booking and operational automation.
At the same time, some companies are adding “AI” to job titles even when the core responsibilities remain largely traditional.
In many cases, it is still essentially an IT manager role with AI familiarity layered in.
This reflects a broader transition period where companies want to signal modernization and candidates want to signal relevance.
In logistics, AI is increasingly handling scheduling, tracking, and coordination tasks.
According to Brittany Lasky, operational roles such as logistics coordinators may experience the greatest impact from automation.
However, freight brokers who manage negotiation and strategic RFPs remain in demand.
AI can optimize processes. It does not replace relationship management or strategic negotiation.
Across industries, a pattern is emerging.
Execution becomes automated. Strategy becomes more valuable.
Automation is also reshaping finance and accounting roles.
As Adam Slater noted, accounts receivable jobs that once focused on high-volume manual processing are evolving into more analytical positions centered on reporting and insights.
The work is not disappearing. The expectations are increasing.
Organizations are now hiring for:
Even roles traditionally considered administrative now require deeper technical capability.
AI is not eliminating analyst roles. It is expanding them.
Financial analysts are also expected to understand tooling, sourcing, and data transformation.
In many cases, two or three roles are being combined into one.
This raises a long-term question.
If entry-level roles become more complex or disappear entirely, how will organizations develop senior talent in the future?
The traditional model of high-volume cold calling is changing.
According to Jack Smith and Emily Canna, teams are shifting toward:
At the same time, companies are moving away from activity-based KPIs and focusing more on outcomes such as demos set and SQLs generated.
In a market saturated with automated outreach, authentic communication has become a competitive advantage.
Several clients have said it directly. They want a human in the seat.
Every six to twelve months, hiring trends in go-to-market teams shift.
As Jennifer Salerno noted, companies move through cycles.
One quarter it is BDRs.
Then RevOps.
Now it is go-to-market engineers.
Many companies experimented heavily with AI to accelerate pipeline generation.
What those experiments exposed were structural gaps, particularly in outbound strategy.
AI can support execution. It does not replace a well-built top-of-funnel engine.
Inbound momentum can hide weaknesses. Outbound forces clarity.
The companies gaining traction right now are not chasing trends. They are rebuilding the fundamentals of their go-to-market strategy.
For employers, the takeaway is straightforward. Job descriptions and expectations need to evolve alongside technology.
Across functions, we are seeing the same shift play out. AI is not eliminating entire roles. It is changing how those roles operate and increasing the baseline skill set required to perform them well.
Hiring managers should start thinking less about traditional titles and more about capabilities. That often means prioritizing candidates who can:
In many cases, the perfect candidate with the exact title simply does not exist yet. The strongest hires are often people who have developed adjacent skills and shown the ability to adapt as the tools evolve.
The broader trend is that AI is accelerating a shift that was already underway.
Roles are becoming more hybrid. Expectations are increasing across nearly every function. And repetitive tasks are being automated, leaving more strategic work behind.
Sales teams still need pipeline.
Operations teams still need coordination.
Finance teams still need reporting and analysis.
Engineering teams still need to build software.
What is changing is how the work gets done and what skills are required to do it well.
Right now we are in a transitional phase where companies are still labeling roles with “AI” as they experiment with new workflows and technologies.
Over time, that label may disappear.
AI will simply become part of how work gets done.
And the roles themselves, while evolving, will look more familiar than the titles might suggest.