CAREER STRATEGY • WORKPLACE POWER • CAREER SURVIVAL
NEW ROLES | WORKPLACE STRATEGY | OFFICE POLITICS | VISIBILITY | CAREER SURVIVAL

Posted on Jun 7, 2026 by
Emma Cladwell
Most professionals entering a new role ask themselves the same question.
Am I doing enough?
Am I performing well enough, working hard enough, delivering enough output to be taken seriously?
That is the wrong question.
And Arend, CTO of a multi-million dollar AI company in the green technology space, just explained why.
He did not build his company's infrastructure by accident.
He has spent years watching people enter technical and leadership roles, reading the room well or getting it wrong, and quietly determining which ones were worth the investment and which ones would need to be managed around.
He was not asked to evaluate an employee this time.
He was asked to evaluate a system designed to help new hires navigate their first 30 days.
What he said in that evaluation quietly exposes one of the most important things most professionals will never hear directly from the person above them.
The gap that ends careers early is almost never a skills gap.
It is a communication gap.
And he had seen it happen on his own team, more than once, before anyone named it clearly.
When you are new in a role, your attention goes inward.
Am I learning fast enough?
Am I asking too many questions?
Am I too quiet in meetings?
That inward focus makes sense. It feels responsible. It feels like conscientiousness.
But while you are focused on your own performance, your manager is watching something else entirely.
Not your output. Not yet.
Something harder to measure and easier to get wrong.
How you communicate.
How you manage expectations.
Whether you understand the hierarchy you just entered, not just the org chart, but the unwritten one.
When Arend was asked what new hires most often get wrong in the first 30 to 60 days, he did not say technical skills or ramp-up speed.
He said:
"Communication, definitely. Also expectation management."
Two words. Simple. Devastating.
Because those two things are almost never on the list of things a new hire thinks they need to work on.
Most people walk in confident they can do the job.
They never ask whether they know how to move within the organisation that hired them.

Here is what most onboarding programs will not tell you.
Technical competence is the price of entry.
It is why you got hired.
But it is not what gets you trusted, included, and moved forward.
What does that is your ability to read the room, manage expectations upward, and communicate in a way that makes your manager's job easier instead of harder.
Arend sees this play out differently depending on the type of hire.
For senior and leadership positions, the gap is the most consequential.
Walking into an established company at a senior level and not understanding hierarchy and communication styles means you can actively damage your standing before anyone has had a chance to see what you are genuinely capable of.
For technical professionals, the gap is often more specific.
He has built his career in technical environments. He knows what he is talking about when he says:
"Communication isn't the strongest thing for developers. So it would be a good resource to share with them so they adapt better with non-technical people."
A developer who cannot translate their work into the language of a non-technical stakeholder is not just a communication problem.
They are a bottleneck.
They create friction.
They get bypassed in decisions because the effort of interpreting them outweighs the value of including them.
That is not a technology problem.
That is a perception problem.
And perception is almost always fixable, if you know what you are dealing with before your reputation locks in.

He was looking at it as someone who has sat on the other side of the evaluation.
Someone who has made the silent judgments that decide who gets trusted with more responsibility and who quietly gets moved around.
His assessment was direct.
"It captures very well how to move within an organisation, especially in corporate. A lot of the mentions and strategies would be helpful for even a senior staff member to navigate better."
That last part is worth stopping on.
Even a senior staff member.
Not just the nervous graduate in their first role.
Not just the mid-level professional wondering why they keep getting overlooked.
A senior staff member, navigating an established organisation, who still needs to understand how to move within the hierarchy rather than bump against it.
He also pushed back on something most people assume about systems like this.
That they are only for beginners.
"For senior and leadership positions, especially in an established company, this would be vital to understanding hierarchy and communication styles."
Vital.
Not helpful. Not useful.
Vital.
That word comes from someone who has watched what happens when that understanding is absent in a fast-moving, high-stakes environment.

They are deciding how much of their own attention and political capital they are willing to invest in you.
When you communicate clearly, flag things proactively, and demonstrate that you understand the expectations above your own role, a manager like Arend reads that as:
This person will not become a problem I have to manage.
This person will represent me well in rooms I am not in.
This person is worth investing in.
When you communicate poorly, miss expectations quietly, and stay in your own lane without signalling upward, the read is different.
Not necessarily incompetence.
Someone who does not yet understand the game.
And in most organisations, especially at senior or leadership levels, someone who does not understand the game eventually gets moved around it.
Arend put it this way:
"I would recommend this for any significant hire in the company to make sure the new hire understands and learns how to move within your company efficiently."
Not the most junior hire.
Not the easiest role to fill.
The significant hire.
The person the organisation actually invested in.
The one where the stakes of getting the first 30 days wrong are highest.

"I would not make it required but more as a resource they can have access to."
That is a more valuable endorsement than a mandate.
Because mandatory resources get skimmed.
Resources that exist for the people who seek them out get used properly.
He is drawing a line between the juniors who are still being actively shaped by on-the-job management, and the senior hires and leaders who need to arrive with their own understanding of how to navigate a company, not wait to be taught.
"For senior and leadership positions, especially in an established company, this would be vital."
If you are a significant hire, a newly promoted leader, or a technical professional stepping into a role that requires you to operate across departments and reporting lines, you are in the category he is talking about.
The category where this is not optional.
Where getting communication and expectation management right in the first 30 days determines whether the organisation keeps investing in you or quietly starts working around you.

You might not be a CTO.
But you report to one, or to someone who thinks the way Arend does.
And here is what that means practically.
The person above you is watching your communication before they are watching your output.
They are forming a picture of whether you understand the hierarchy, not just the job description.
They are deciding whether you are someone who will make their team better or someone who will require careful management.
Most of that picture forms in the first 30 days.
And almost none of those criteria appear in your job description.

The system Arend reviewed is built around one uncomfortable truth.
Your first 30 days in any significant role are not a grace period.
They are an invisible audition.
You are being evaluated on things no one articulates out loud.
How you communicate under pressure.
How you manage expectations when something is unclear.
Whether you understand the hierarchy you entered, not just the formal one.
Whether you make the person above you feel more confident or less confident in their decision to hire you.
The New Job Survival System addresses all of that.
Not with theory.
With a week-by-week tactical structure built around the specific moments where communication, perception, and positioning are won or lost.
Week 1 covers first impressions and intro tactics. The exact language and behaviour that signals competence and cultural intelligence from day one.
Week 2 covers recovery and reset protocols. What to do when something has gone sideways and you need to quietly correct the narrative before it solidifies.
Week 3 covers visibility and contribution tactics, including manager pulse check questions that flip you from reactive to proactive without making you look like you are performing.
Week 4 covers long-game positioning. How to stop thinking about survival and start building the kind of reputation that opens doors before they appear on any org chart.
These are not soft skills.
They are the skills a CTO who built a multi-million dollar company says would be vital for any significant hire, at any level.

You do not have to be in tech or green energy for this to apply.
Arend leads developers and non-technical staff side by side in one of the most fast-moving, cross-functional environments in modern business.
He has watched communication failures cost careers across both groups.
If you are entering a new role, recently promoted into one, or new to a company at a senior level and already feeling the friction of an environment you have not fully decoded yet, this system was built for exactly that moment.
Not because you are bad at your job.
Because doing your job and moving within your organisation are two different skills.
And only one of them was covered in your job description.
The manager above you already knows the difference.
Now you do too.


He knew how to do the work. Pouring slabs, running crews, dealing with delays and last-minute changes. None of that scared him.

I had something to say. A good point, actually. But I hesitated half a second too long, someone else jumped in, and the moment passed. Did staying quiet make me look disengaged? Or worse invisible?
Privacy Policy | Terms of Use | Advertising Disclosure
This is an advertorial and not a guarantee of workplace outcomes. Individual results may vary depending on role, organisation, manager, team culture, and execution. The article may include affiliate or promotional links.
© 2026 New Job Survival System.