Feedback, 1:1s & Performance

Feedback Is a Gift (Really)

Start with the frame, because everything else in this module hangs off it: in American workplaces, direct feedback is normal, expected, and routine. Your manager telling you "this PR description wasn't clear enough — I couldn't tell what changed" is not a warning shot. It is not the first step toward firing you. It is Tuesday.

In many professional cultures, a manager criticizing your work in plain words is a serious event — something that happens only when things have gone badly wrong, often after a long period of hints you were supposed to catch. If that's the culture you grew up in, American directness can feel alarming. Recalibrate: here, the feedback itself is the hint and the message, delivered once, in plain language, so you can act on it and move on.

Here's the counterintuitive part most non-US engineers take a year to learn: the absence of feedback is the bad sign. Managers invest feedback in people they believe in. When a manager has quietly given up on someone, the feedback stops — the 1:1s get shorter and more pleasant, the code reviews get rubber-stamped, and everything is "fine" right up until it very much isn't. If your manager is still pushing you on details, they are still betting on you.

Receiving Feedback Well: Thank, Clarify, Act

How you receive feedback is watched at least as closely as the work being critiqued. The move has three beats:

• Thank. Not performatively — a simple "thanks, that's useful" signals that giving you feedback is safe and worthwhile. Defensiveness teaches people to stop telling you things, which is the worst possible outcome.
• Clarify. Make sure you understand the actual behavior and the actual impact. "Just so I act on the right thing — is the issue the missing context in the PR description, or the size of the PR itself?" Clarifying questions read as engagement, not pushback.
• Act visibly. Change the behavior, and let the change be seen. If the feedback was about unclear PR descriptions, your very next PR should have a noticeably better one — and it's completely fine to say "tried the structure you suggested, let me know if this is closer."

That third beat is the one people underrate. Acting on feedback fast is one of the strongest reputation builders that exists. Managers talk about it in calibration rooms in exactly these words: "I gave them feedback once and it was fixed by Friday." It marks you as coachable, and coachable engineers get the stretch projects, because giving them work is low-risk.

The 1:1: The Most Misunderstood Meeting in America

Every US-style company gives you a recurring 30 or 45 minutes alone with your manager, and most engineers — American ones included — waste it. The single biggest misunderstanding: the 1:1 is your meeting, not your manager's. You own the agenda. Your manager is the resource; you are the customer.

Which means the cardinal sin of 1:1s is turning them into a status report. Status belongs in writing, before the meeting — a few bullets in Slack or your team's update doc, exactly as the Overcommunication module teaches. If you spend the 1:1 narrating what you did this week, you are reading your manager information they could have skimmed in ninety seconds, and burning the only time slot in your week where you have their full, private attention.

What to Actually Bring

A good 1:1 agenda draws from five buckets. You don't need all five every week — two or three items is a full meeting.

And if you have nothing? Then say so honestly and ask a bigger question — "what's worrying you about the quarter?" or "what does the team need that nobody's doing?" — rather than defaulting to status. Silence in 1:1s wastes the highest-leverage 30 minutes of your week. It is also, quietly, a signal: engineers who bring nothing to 1:1s for months read as disengaged, even when they're shipping.

Ask for Feedback Before It's Offered

The single highest-return habit in this entire module: proactively ask for feedback in your 1:1, on a regular cadence. Not "any feedback for me?" — that question is too easy to deflect with "no, you're doing great." Ask a version that forces a real answer:

"One thing" gives your manager permission to name something small without it being a big conversation. Asking "this month" makes it recurring and normal. And here is the unwritten rule underneath: managers remember who asks. When review season comes and your manager writes about your growth mindset, the engineers who asked for feedback all year are the ones with the evidence trail.

Self-Advocacy: Nobody Is Tracking Your Wins for You

This is the norm that surprises non-US engineers the most, so we'll say it without cushioning: in American workplaces, visibility of your work is your responsibility. There is no fairness system quietly logging your contributions. Your manager sees maybe 20% of what you do, is context-switching across eight people, and will remember, at review time, roughly what was surfaced to them — no more.

Many of us come from cultures where good work is supposed to speak for itself, and talking about your own achievements is distasteful — the nail that sticks out. Carry that instinct into a US workplace and here is what happens: modesty reads as absence. Not humility — absence. The teammate who mentions their wins matter-of-factly isn't seen as arrogant; they're seen as someone doing visible, valuable work. And you, doing equal or better work silently, are seen as... fine. Quiet. Hard to write a promotion case for.

The Mechanics: Visibility Without Bragging

The good news: American self-advocacy is not chest-beating, and actual bragging lands badly here too. The norm is stating facts with outcomes, in a neutral tone, in the channels where work is discussed anyway:

• Fact + outcome, no adjectives. "I shipped the new import pipeline — it cut sync failures by 30%." No "I'm proud to announce," no "single-handedly," no trumpets. The number does the talking.
• Surface wins in standups and written updates, matter-of-factly. A win is a status item like any other. "Shipped X, early data shows Y" takes one line and ten seconds of mild discomfort that fades with practice.
• Credit generously and specifically. "Priya's review caught the race condition" costs you nothing and makes your factual self-reports more credible, not less. Advocates who share credit are trusted; win-hoarders are noticed too, in the other direction.
• Keep a brag document. The backbone of the whole practice — see below.

Performance Reviews: How the Machine Actually Works

Most US tech companies run a review cycle every six or twelve months, and the process is remarkably consistent across the industry. Knowing the machinery matters, because each stage has an unwritten rule that non-US engineers routinely miss.

Stage 1: The Self-Review

You write an account of your own performance — accomplishments, impact, growth areas. The unwritten rule: never sandbag it. Engineers from modesty-forward cultures often write restrained, self-critical self-reviews on the theory that humility will be read as maturity and the manager will fill in the real story. Neither happens. Your self-review is treated as your own best case for yourself; if even you describe your year as unremarkable, that framing sticks.

Write it from your brag document, with concrete outcomes: what you did, why it mattered, what changed because of it, with numbers wherever they exist. Factual, specific, and complete — not inflated, but never shrunken. Name your growth areas honestly too (a self-review with zero growth areas reads as unself-aware), but frame them as trajectories: "working on X, here's what I've changed so far."

Stage 2: Peer Feedback

You'll be asked to review a few teammates, and they'll review you. The unwritten rule here: vague praise helps nobody. "Great teammate, pleasure to work with" is a wasted slot — it gives their manager nothing to argue with in calibration. Substantive peer feedback names specific work and specific impact: "Their review of my migration design caught a data-loss edge case before it shipped; they do this consistently across the team's designs." Write for your peers what you hope they write for you: evidence, not adjectives.

Stage 3: Calibration (the Part You Never See)

After the writing, managers meet — without you — and compare everyone at your level to agree ratings are consistent. This is where the whole year converges, and the mechanic to understand is: your manager argues your case with the evidence you gave them. They are your lawyer in that room. Your self-review, the wins you surfaced in 1:1s, the peer feedback your specific work earned — that is the case file. A manager with a thin file can't invent a strong argument, no matter how much they like you.

Stage 4: Ratings and What They Map To

Out the other end comes a rating — usually a 3-to-5-point scale with labels like "meets expectations" and "exceeds expectations." Two calibration notes for non-US readers: first, "meets expectations" is a genuinely fine rating at most companies, not code for failure — most strong engineers get it most cycles. Second, ratings carry real weight: at US companies they drive raises and promotion eligibility, and for you they are the strongest evidence Hireboard can bring to the table when we advocate for your compensation. That's why everything upstream — the brag doc, the 1:1 wins, the substantive self-review — is worth the effort. It compounds into the rating, and the rating compounds into everything else.

Growing Your Scope — and How Raises Work Here

The American norm is that asking for more is expected — and at Hireboard that norm splits cleanly in two. Scope, responsibility, and growth you pursue directly with your client manager, using everything in this section. Salary and benefits you bring to Hireboard, with the same case in hand. The stronger the case you build on the ground, the harder we can push for you.

The case has a shape. It is evidence, not a wish. "I want more responsibility" is a hope; a case sounds like:

• Scope grown: "When I joined I owned one service; I now own three and the on-call rotation design for all of them."
• Outcomes delivered: "The billing migration landed on time and cut invoice errors 40%" — pulled straight from the brag document.
• Next-level behaviors already shown: the unwritten rule of US promotions is that you get promoted for already operating at the next level, not as a bet that you will. Your case should show you've been doing the next-level job for a while — mentoring, leading designs, owning outcomes beyond your ticket queue.

Timing matters more than people think. Client review cycles and Hireboard's advocacy both work on calendars: raise the growth conversation with your client manager a month or two before their review cycle, and share your case with Hireboard at the same time — so we can push while decisions are still open on both sides. And when the client manager praises your work, ask them to put it in writing; a client's written praise is the strongest card Hireboard can play for you.

When the Answer Is "Not Yet"

Often the answer is not-yet — and how you handle it is itself watched. Don't sulk, and don't drop it either. Extract two concrete things: a gap list ("specifically, what's between me and the next level? Can we write it down?") and a revisit date ("can we check progress against this list in three months?"). A vague "keep doing what you're doing" is not an answer — politely insist on specifics. Then work the list visibly, and bring receipts to the revisit. Managers respect this loop enormously; it converts a rejection into a roadmap.

Giving Feedback Upward & Sideways

Feedback in US workplaces is not a downhill-only river. Giving thoughtful feedback to peers — and yes, to your manager — is welcome and marks you as senior, when done well. The shape matters more than the seniority gap.

The shape is SBI — Situation, Behavior, Impact — the same structure from the Ideas & Feedback module: "In yesterday's planning meeting (situation), the priorities changed twice after we'd started estimating (behavior), and the team left unsure what to commit to (impact)." No mind-reading, no character verdicts, just an observable behavior and its concrete effect. SBI is what makes upward feedback safe: you're not judging your manager, you're reporting an effect they probably can't see.

• Praise publicly and specifically. Public praise is a gift twice over — the person feels seen, and their manager gains calibration evidence. Specific beats generic: "Sam's incident writeup was so clear that support stopped escalating tickets about it" travels; "Sam is great" evaporates.
• Correct privately. Critical feedback goes in DMs and 1:1s, never in the group channel — even when you're right, especially when you're right. Public correction humiliates, and the audience remembers the humiliation long after the content.
• Lead positive — the American frame. The US norm is positive-first: lead with what genuinely worked, then offer the improvement as an addition, not a verdict. The canonical move is "one thing that would make it even better." This is not fake sweetness — it's sequencing that keeps the listener open. Just make the praise real; Americans detect filler praise instantly.

Knowledge Check

Five scenarios from real feedback-and-review life. Check that you'd make the culturally fluent call in each one.