Building Trust With a Skeptical Internal Technical Team as an Outside Consultant

An internal engineering team's first reaction to my being brought in was cold, bordering on hostile. Fair enough — an outside consultant showing up usually means either their work is being questioned or their headcount is being justified against mine. Neither is a comfortable position to be put in by a decision made above them.

My instinct was to prove competence quickly — ship something impressive, demonstrate I knew what I was doing. That approach made things worse, not better, because it read as exactly the turf-encroaching behavior they were already braced for.

A skeptical technical team doesn't need proof you're competent. They need proof you're not there to make them look bad.

What actually worked

• I asked their opinion on the existing architecture before proposing anything, genuinely, and incorporated what they said even when I'd have done it differently.
• I credited their prior decisions explicitly in front of the client, rather than implying the engagement existed because their work needed fixing.
• I shared my findings with them before presenting anything to the client, so they never heard about a problem in their own system secondhand from a stakeholder.
• I asked for code review from their team on anything I shipped into shared infrastructure, even when I didn't technically need their sign-off.
• I was specific and honest about what I didn't know in their stack, instead of performing confidence I didn't have.

None of that was technical. It was entirely about demonstrating, through actions rather than reassurance, that the engagement wasn't a referendum on their competence. By week three the same team was proactively flagging things to me they hadn't told the client, which is the actual signal that trust has transferred — not politeness, but information sharing.

I still think the instinct to lead with technical proof is the wrong first move with any skeptical internal team. Competence is assumed the moment you're in the room; what's actually in question is whether you're safe to work alongside, and that's established through behavior, not deliverables.