Influencing a technical decision without authority

Evidence status — rewritten from Lucid resume production evidence: Confluent→Kafka/MSK migration with $1M+ annual infrastructure savings and platform ownership transfer, plus daily partnership across Sales/Service/Commerce/Supply Chain clusters. Peer names and exact adoption curves stay private. This replaces the blocked vpeetla-ai “standards across my own repos” narrative, which was not influence without authority.

Expected question

"Tell me about a time you influenced a technical decision when you did not own the teams involved and could not escalate your way to a mandate."

Variant forms

Interviewers often probe the same competency with different framing — recognize the archetype and answer with your story:

"Tell me about a time you influenced people without authority."
"Describe getting another team to adopt your design via RFC/docs/tooling rather than mandate."
"Tell me about resolving a cross-team technical disagreement without escalating to leadership."
"How do you make the right architecture the easiest path for other teams?"
"Tell me about aligning incentives so other teams wanted your proposal for their OKRs."
"Describe a platform migration where product teams had to change how they published and consumed events."
"Tell me about a time influence failed the first time — what did you change?"
"Walk me through Staff-level leadership: how you drove a decision across org boundaries."

The question, as it might actually be asked

"Tell me about a time you influenced a technical decision when you did not own the teams involved and could not escalate your way to a mandate." Staff+ signal is durable cross-team alignment via artifacts and incentives — not title, not a hallway win that reverts Monday.

Candidate-owned evidence prompts

Private notes before naming people or exact timelines:

Which non-reporting product/platform teams had to cut over from Confluent?
What competing proposal existed (stay on Confluent, dual-run forever, per-team brokers)?
What adoption evidence remained after you left the critical path?
What may be said publicly about savings attribution and partners?

Author reference (do not memorize)

Anonymize peer/team names in public rehearsal. Do not claim a reporting-line mandate you did not have.

Situation

At Lucid I led architecture across Sales, Service, Commerce, and Supply Chain — principal scope over six concurrent efforts, partnering daily with business and cross-cluster engineering (P, resume). Streaming sat on Confluent with recurring cost and ownership friction. I didn't own every product team that produced or consumed those events. Keeping Confluent forever was the path of least resistance for teams that just needed "Kafka that works."

Task

Move the org to Kafka/MSK with clear platform ownership transfer and durable savings — without pretending an architecture title was a mandate over every producer/consumer roadmap. Resume outcome on resume: $1M+ annual infrastructure savings with ownership transfer (P). Spoken default without private baseline: "seven-figure annual run-rate reduction with ownership transferred in-house."

Action

Influence, for me, meant making the right path cheaper than the wrong one:

Wrote the decision as an owned platform boundary, not a preference memo. MSK + clear ownership transfer vs continued vendor-operated cost and weaker internal control.
Partnered cluster by cluster — Sales, Service, Commerce, Supply Chain — on cutover sequencing, dual-run windows, and who owned schemas/topics after transfer. ADRs and roadmaps, not "because architecture said so."
Tied it to their OKRs: cost, operability, and changing event contracts without a vendor ticket. Same ownership logic as the EDI modernization story.
Migrated by wave. Net-new work landed on the target path first so adoption was the default, not a tax mid-launch.

What I rejected: escalate for a blanket mandate. That gets compliance theater and shadow Confluent residual. I'd rather have partial honest adoption than fake universal conversion.

Result

Kafka/MSK migration transferred platform ownership in-house; resume cites $1M+ annual savings (P). Bring the annualization math privately — don't upgrade a resume line into a finance audit in the room.
Cross-cluster teams moved onto an owned event plane instead of staying permanently coupled to the prior vendor operating model.
Honest limit: influence was uneven on older residual paths. Staff+ answers admit partial adoption instead of claiming everyone converted.
What stuck: ownership transfer + wave migration + written decision records — not persuasion meetings alone.

The follow-up question you should expect

"What did you do when a team still refused?" Narrow the ask to the next greenfield producer. Offer pairing on the first topic/schema cutover. Document residual risk and cost of staying on the old path. Forcing a political win that reverts after the meeting isn't influence — it's a meeting.

Staff+/Principal signal rubric

Mid-level: convinced their own squad.
Senior: cross-team agreement with a concrete proposal.
Staff+: mechanism (waves, defaults, ownership transfer) and durable adoption without mandate.
Principal: org-level platform economics + honest limits of influence.