The First 90 Days at a Global Company: Ownership, Ambiguity and the Onboarding That Doesn’t Exist

Getting the offer is roughly 10% of the journey. The first 90 days is where the other 90% starts, and it is the stretch most people are least prepared for.

The core surprise is structural. If you are hired by a large corporation, you land into KPIs, SOPs and a documented onboarding path. If you are hired by a US startup of 10 to 100 people, which is what most companies hiring internationally actually are, there is often no onboarding at all. You are not executing a plan. You are part of the conversation that builds it.

Nobody warns you about that. So the first 90 days feels like a void, and the natural response, waiting for instructions, is the exact wrong move.

What “ambiguity” actually means at a startup

The word comes up constantly in international hiring, and it is rarely defined.

Ambiguity means the plan does not exist yet, and part of your job is to help write it. In a large company, structure tells you what to do and what to achieve. In a small one, you sit with the CEO or CTO and connect the dots: here is what we need, here is what we should achieve, here is how we get there.

You are not being told what to do. You are part of the strategy.

That is uncomfortable for about three weeks and then becomes the best career accelerator available to you.

“Imagine you are a football player and you join Barcelona or Real Madrid. You’ll be playing with the best people, but you’ll be just another one. To stand out will be really hard. But if you go to a club that is not top, top, top, you can be the number one, and it’s going to bring a lot of things for you. So I see ambiguity as an opportunity.” — Lucas Albuquerque, Head of Engineering at Hubble, speaking at Beyond Hire

Structure protects you and hides you at the same time. Ambiguity exposes you and promotes you.

The single behavior that separates people in the first 90 days

Ownership. Not effort, not hours, not technical brilliance. Ownership.

Here is the same blocker, handled two ways.

The passive route	The ownership route
“I don’t have my access yet.”	“I don’t have my access yet. I messaged IT, they said Wednesday, I’ll follow up Wednesday. Meanwhile I’m reviewing the codebase.”
Wait	Message the right person
Deliver nothing	Set a clear deadline
Explain it wasn’t your fault	Escalate proactively before it’s too late
Fail	Ship

Both people were blocked by the same thing. Only one of them will be there in a year.

“I’ve had people saying ‘I don’t have my access yet, I’ve messaged X, Y and Z, they told me to wait until Wednesday, by Wednesday I’ll follow up with that person.’ This is showing ownership. They are not sitting and waiting for things to happen. They are making things happen.” — Beatriz França, People and Culture leader, 10+ years

The reason this matters more remotely: on a distributed team, nobody can see that you are stuck. Your silence looks identical to your productivity. If you do not surface the blocker, it does not exist to anyone but you.

Never sit in confusion

The second failure mode is assumption. It runs in both directions and it is expensive on both sides.

You cannot join a company assuming they will do something for you because you did not ask. They cannot hire you assuming you know something because you implied it.

“It’s never too late to ask until it’s too late.” — Beatriz França

Practical version: if anything is uncertain in your first 90 days, ask within 48 hours. Not after a month of quiet interpretation. The cost of one clarifying question is thirty seconds. The cost of six weeks of building the wrong thing is your first performance conversation.

Ask about:

• What “delivered” means for this task, specifically
• Which of the things on your plate is the actual priority this week
• Whether your update cadence works for your manager or should change
• What the team considers a blocker worth escalating

That fourth one is the sleeper. Teams have wildly different thresholds, and guessing wrong in either direction reads badly.

Read the signs before you ask for the review

Most people wait for a scheduled feedback moment. The signals arrive much earlier and are easy to miss.

“There are signs everywhere. They either started asking you to mentor new hires or asked you to review the code of someone else. These are clear signs that they are trusting what you’re doing. Perfect opportunities for you to go there and say: I noticed you’re doing this. Is there any specific behavior you’d like me to keep leveraging on to add more value?” — Beatriz França

Being asked to review someone else’s work, onboard a new person, or represent the team in a meeting is a trust signal. Treat each one as an opening to ask for direction, not just as extra work.

When you get it wrong, and you will

Two of the most experienced engineers at Beyond Hire described their biggest early mistakes, and neither was technical in the way you would expect.

The wrong tech stack. One team chose a stack that turned out to be wrong for the project, realized it mid-project, and changed course. The project eventually became very successful.

“It was not only about ambiguity, but also about doing the wrong choice and being able to drive accordingly based on a bad decision. We changed the target mid-course, and we adapted.” — Lucas Pinto, 2020 Engineering Emmy winner, leading data engineering at a Fortune 100 media company

The recoverable mistake was not the stack. It would have been refusing to admit it and shipping the wrong thing for another quarter.

Ignoring the relationship. Another engineer joined a company as a contractor, put his head down and pushed code, and watched someone hired after him become CTO within three months.

“This guy became the CTO of the company because he built the relationship. After this I learned the biggest asset I can have is the relationship with the founders, and I started working on this a lot.” — Lucas Albuquerque, Head of Engineering at Hubble

On a remote team, the relationship does not build itself in a hallway. If you do not deliberately invest in it, it does not happen.

A 90-day plan that works in an unstructured environment

Days 1 to 15: map the void. Find out what does not exist. No onboarding doc, no test strategy, no deploy runbook. Write the list. Do not fix anything yet.

Days 16 to 30: ship something small and visible. Not the big refactor. Something that lands, gets reviewed, and proves you can move through the whole pipeline from local to production.

Days 31 to 60: pick one gap from your map and close it. This is the highest-leverage move of the entire 90 days. You now have a documented contribution nobody asked you for, which is the definition of ownership.

Days 61 to 90: ask for calibration explicitly. “Here is what I’ve delivered. Here is what I think the priorities are. Am I reading it right?” Do not wait for a review cycle to find out.

Throughout: surface blockers within 48 hours, always with the action you already took.

Frequently asked questions

What should I do in the first 90 days of a remote job at a startup? Map what does not exist in the first two weeks, ship something small and visible by day 30, close one process gap you identified by day 60, and ask for explicit calibration by day 90. Surface every blocker within 48 hours along with the action you already took.

What does “comfortable with ambiguity” mean in a job description? It means the company has no documented plan for your role and expects you to help build one. In large companies, KPIs and SOPs tell you what to do. In startups of 10 to 100 people, you sit with leadership and define what needs to happen. You are part of the strategy, not the execution of someone else’s.

How do I show ownership at work when I’m blocked? Do not wait. Message the person who can unblock you, set a clear deadline, escalate proactively before the deadline damages the delivery, and communicate what you are doing in the meantime. The passive route ends with a correct explanation of why nothing shipped, which does not help anyone.

How do I get feedback if my manager never gives any? Ask directly, and use trust signals as your opening. If you are asked to review someone’s code, mentor a new hire, or represent the team, respond with a question about what to keep doing more of. Do not wait for a scheduled review cycle to learn where you stand.

Is it normal for an international startup to have no onboarding? Yes, and it is the norm rather than the exception at companies of 10 to 100 people. The absence of process is not a sign the company is disorganized in a way that should worry you. It is a sign that building the process is part of the job.

Keep reading

• The Job Interview Is a Negotiation, Not an Audition  [→ https://tookn.io/blog/interview-is-a-negotiation]
• Cultural Translation: What Nobody Warns You About  [→ https://tookn.io/blog/cultural-translation-global-teams]
• From Mid-Level to Senior on a Global Team  [→ https://tookn.io/blog/mid-level-to-senior-global-teams]
• The company-side view: Why Nearshore Hires Leave in Six Months  [→ https://tookn.io/blog/why-nearshore-hires-leave]

The hire is just the beginning. The first contract is not the finish line.