TubeSum

Building Trust in New Roles — Full Transcript & Summary

How to Build Trust in a New Technical Role

0h 00m video Published May 16, 2026 Transcribed Aug 12, 2026 F freeCodeCamp.org
Beginner 1 min read For: Professionals starting new technical roles who need to understand the importance of interpersonal trust.
AI Trust Score 35/100
🚫 Clickbait / Waste of Time

"Title promises a technical guide but delivers a brief, generic reminder about soft skills—thin on substance."

AI Summary

This video discusses the critical role of building trust when starting a new technical role. It explains that without trust, colleagues may not help you, leading to significant financial waste. The core advice is to be a person people want to work with.

[00:00]
Trust is essential from day one

In any organization, you must build trust because you can't do the technical work without people's help. You lack permissions and system knowledge on day one.

[00:14]
Consequences of failing to build trust

If you don't build trust, colleagues won't share knowledge or make your life easier. This can lead to the organization wasting $10,000 to $50,000 as people resist your efforts.

[00:42]
Be someone people want to work with

Avoid acting like you know everything. Be a person people want to work with to gain cooperation and support.

Study Flashcards (3)

Why is building trust essential on day one?

easy Click to reveal answer

Because you lack system knowledge and permissions, so you need colleagues to guide you.

00:14

What is the potential cost of failing to build trust?

medium Click to reveal answer

They may waste $10,000 to $50,000 to sabotage your efforts.

00:30

What is the key advice for building trust?

easy Click to reveal answer

Be a person people want to work with—avoid acting like you know everything.

00:42

💡 Key Takeaways

💡

Trust is a prerequisite for technical work

Highlights that technical success depends on interpersonal trust, not just skills.

📊

Cost of failed trust

Provides a concrete financial impact ($10k-$50k) of not building trust.

00:30
⚖️

Be someone people want to work with

Offers a simple, actionable principle for new hires.

00:42

[00:00] almost every org you work at, you're going to have to build trust because you won't be able to do the technical piece without the people there. So it's not because you won't have the permissions to the systems that you need to access.

[00:14] You don't know how the system works because you're day one. So if you can't build trust, they're not going to tell you or make your life easier to figure out how to help them, Which seems counterintuitive because it's like they hired you to be there and now they're not going to help you solve the problem.

[00:30] They're going to waste $10,000 to $50,000 to sabotage your – and they will. They may. Like if you're a jerk and you show up and you're like, I know everything. I build every system.

[00:42] I work for Google. I don't know. Like they won't want to work with you. So you got to be a person you want to work.

More from freeCodeCamp.org

View all

⚡ Saved you 0h 00m reading this? Transcribe any YouTube video for free — no signup needed.