First 90 Days 1:1 Question Bank: 50 Prompts for New FAANG Managers to Build Trust

First 90 Days 1:1 Question Bank: 50 Prompts for New FAANG Managers to Build Trust

TL;DR

New FAANG managers must anchor the first 90 days on purposeful 1:1 conversations that surface intent, risk, and performance metrics before any formal roadmap is set. The most effective trust‑building prompts are those that force the direct report to articulate personal success criteria, not the manager’s agenda. Anything less is a waste of senior engineers’ limited calendar bandwidth.

Who This Is For

You are a newly promoted engineering manager at a FAANG company, stepping into a team of senior individual contributors whose average tenure exceeds 3 years and whose compensation packages range from $165,000 base to $250,000 total, including 0.05 % equity. You have a 30‑day onboarding sprint, a 60‑day diagnostic sprint, and a 90‑day alignment sprint, and you need a concrete question bank that converts early 1:1s into measurable trust signals.

How should I prioritize trust‑building topics in the first 90 days of 1:1s?

The priority hierarchy is: personal motivation → project health → team dynamics → career aspirations → risk exposure, and you must follow it strictly for the first six 1:1s.

In a Q2 debrief, the hiring committee asked why the manager’s first three meetings were spent on “roadmap alignment” and we flagged it as a red‑team signal because the manager failed to surface personal drivers early. The framework I call the “Tri‑Layer Trust Funnel” forces you to ask a motivation question in the first meeting, a health question in the second, and a risk question in the third.

Insight 1 – The first counter‑intuitive truth is that agenda‑heavy 1:1s erode credibility faster than silence. When a senior engineer hears “Let’s discuss the sprint plan” before any personal context, they interpret the manager as a process‑driven overseer rather than a partner.

Script example:

• “What part of your work last week gave you the most sense of impact?” (Motivation)
• “Which current blocker would, if removed, double your velocity?” (Health)
• “If you had to flag one hidden risk that no one else sees, what would it be?” (Risk)

Not “I need to hear your status,” but “I need to hear what matters to you.” That distinction shifts the manager from data collector to trusted advisor.

What specific prompts reveal a direct report’s motivations without seeming intrusive?

The most reliable prompts are those that ask the employee to describe their own success metrics, not the manager’s expectations. In a recent senior‑engineer 1:1, I asked, “When you look back in six months, what outcome would make you feel you’ve succeeded?” The answer was a concrete metric (“reduce latency by 30 %”) that later became a key KR in the team OKR.

Insight 2 – The second counter‑intuitive truth is that the most revealing questions are framed as future‑oriented hypotheticals, not past‑focused audits. A question like “What would you change about the current product if budget were unlimited?” surfaces passion without accusing the manager of micromanagement.

Script example:

• “If you could pick any project to own next quarter, which would you choose and why?”
• “What part of our product line excites you enough to stay late without compensation?”

Not “What did you accomplish last week?” but “What do you aspire to accomplish next?” The shift from evaluation to aspiration creates psychological safety and a clear signal of trust.

Which 1:1 cadence and duration maximizes alignment while respecting senior engineers’ time?

A cadence of bi‑weekly 45‑minute sessions for the first 60 days, followed by a weekly 30‑minute check‑in after the 60‑day mark, yields the highest alignment score in my internal metrics. In a Q3 HC meeting, the senior leadership team rejected a candidate who scheduled daily 1:1s because the cadence was interpreted as “micromanagement overload.”

Insight 3 – The third counter‑intuitive truth is that more frequent, shorter check‑ins after a trust baseline is established outperform longer, less frequent meetings. The first two months are for depth; the third month is for velocity.

Script example:

• “We’ll keep these bi‑weekly deep dives for the next six weeks; after that I’ll shift to a quick pulse check each week.”
• “If you ever need a longer slot, just let me know and we’ll schedule it.”

Not “I will dominate your calendar,” but “I will respect your calendar.” The difference signals that the manager values the engineer’s time as a resource, not a hurdle.

How can I surface hidden risks in my team during early 1:1s?

The most effective risk‑surfacing prompt is a forced‑choice “What if” scenario that forces the report to reveal dependencies they otherwise hide. In a Q1 debrief, a senior manager confessed that the team’s biggest risk was an undocumented API contract, a fact that had never surfaced in group meetings because the engineer assumed “no one else needs to know.”

Insight 4 – The fourth counter‑intuitive truth is that asking “what could go wrong” directly triggers defensive silence; instead, ask “what could we do better.” The subtle reframing reduces perceived blame while still exposing hazards.

Script example:

• “If you had a magic wand to fix one hidden flaw in our current architecture, what would it be?”
• “What’s one thing you’re hesitant to raise in the larger forum because you think it’s too risky?”

Not “Tell me the risks,” but “Tell me the improvements you see.” The contrast turns the conversation from audit to collaboration.

When should I transition from discovery to performance coaching in the 90‑day window?

Transition after the third 1:1, when the trust funnel has delivered at least three concrete data points on motivation, health, and risk, and you can reference them in a performance discussion. In a recent 90‑day review, I quoted a direct report’s own risk statement (“If our data pipeline stalls, we lose 20 % of throughput”) to set a measurable improvement target, and the senior engineer accepted the coaching plan without resistance.

Insight 5 – The fifth counter‑intuitive truth is that timing the shift on a data milestone, not a calendar date, yields higher acceptance. The manager must anchor the coaching conversation in the employee’s previously expressed language.

Script example:

• “You mentioned the pipeline stall could cost us 20 % throughput; let’s set a target to reduce that risk by 15 % in the next quarter.”
• “Based on what you said last week about impact, I’d like to align your objectives with that metric.”

Not “Now we’ll start performance reviews,” but “Now we’ll act on the risks you identified.” The distinction signals that the manager is responding to the employee’s own narrative, reinforcing trust.

Preparation Checklist

• Review the “Tri‑Layer Trust Funnel” and map each upcoming 1:1 to its corresponding layer.
• Draft the five core prompts from the script library and rehearse them aloud.
• Align each prompt with the team’s current OKR cadence to ensure relevance.
• Schedule the bi‑weekly 45‑minute slots in the shared calendar, blocking them for the first 60 days.
• Work through a structured preparation system (the PM Interview Playbook covers “Strategic 1:1 Question Design” with real debrief examples).
• Identify at least two personal success metrics for each direct report before the first meeting.
• Prepare a risk‑surfacing worksheet to capture “what if” answers during the first three 1:1s.

Mistakes to Avoid

BAD: “Ask “What did you accomplish?” in every 1:1 and take notes on the spreadsheet.” GOOD: “Ask forward‑looking success‑metric questions and capture the employee’s own language for later coaching.”

BAD: “Schedule daily 1:1s and treat each as a status update.” GOOD: “Use bi‑weekly deep dives early, then shift to weekly pulse checks after trust is established.”

BAD: “Wait until the 90‑day review to discuss risks, assuming they’ll surface naturally.” GOOD: “Introduce risk‑surfacing prompts in the third 1:1 and record them for immediate action planning.”

FAQ

How many 1:1s should I conduct in the first 90 days? Conduct six bi‑weekly 45‑minute sessions in the first 60 days, then transition to weekly 30‑minute pulse checks for the remaining 30 days. This cadence balances depth with senior engineers’ limited calendar bandwidth.

What if a direct report refuses to share personal motivations? Reframe the question as a future‑oriented aspiration (“What outcome would make you feel you’ve succeeded?”) and reference their own past achievements. The refusal usually stems from perceived risk; the reframed prompt reduces that perception.

Can I use these prompts for senior engineers outside of FAANG? Yes, the underlying trust‑building principles apply across large‑scale tech firms, but adjust the compensation references and OKR cadence to match the organization’s typical salary bands and planning cycles.

The 0→1 PM Interview Playbook (2026 Edition) — view on Amazon →