<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[The Authority Playbook]]></title><description><![CDATA[The Authority Playbook]]></description><link>https://theauthorityplaybook.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Wed, 18 Nov 2026 16:56:11 GMT</lastBuildDate><atom:link href="https://theauthorityplaybook.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Keep the floor, keep the credit: authority scripts for South Asians in tech]]></title><description><![CDATA[You arrive prepared. Your recommendation is clear. Then someone talks over you, repeats your idea, or treats your answer as tentative until another person…]]></description><link>https://theauthorityplaybook.hashnode.dev/keep-the-floor-keep-the-credit-authority-scripts-for-south-asians-in-tech</link><guid isPermaLink="true">https://theauthorityplaybook.hashnode.dev/keep-the-floor-keep-the-credit-authority-scripts-for-south-asians-in-tech</guid><category><![CDATA[career advice]]></category><category><![CDATA[Soft Skills]]></category><dc:creator><![CDATA[Mr Smith]]></dc:creator><pubDate>Fri, 13 Nov 2026 00:34:26 GMT</pubDate><content:encoded><![CDATA[<p>You arrive prepared. Your recommendation is clear. Then someone talks over you, repeats your idea, or treats your answer as tentative until another person says it.</p>
<p>The useful response is not to become the loudest person in the room. It is to make the decision, the evidence, and your ownership harder to lose.</p>
<p>This is for South Asians in tech who want practical language without being told to erase an accent or act like somebody else. South Asians are not one personality type. Use whichever of these situations fits your experience; none is a claim about how an entire community behaves.</p>
<ol>
<li>Put your role in the opening, not in a defensive introduction.</li>
</ol>
<p>You do not need to recite your resume. Say what you own and what the room needs to decide:</p>
<p>"I own the API migration. Today we need to choose between a staged rollout and a full cutover. I recommend the staged rollout."</p>
<p>That is easier to use than a long build-up. It also gives people a clear place to put their questions. If you are contributing rather than owning the work, name that accurately:</p>
<p>"I tested the rollback path. There is one failure case we should address before launch."</p>
<p>Precision reads better than inflated credit.</p>
<ol start="2">
<li>Recover the floor once, clearly.</li>
</ol>
<p>If someone interrupts before the point is complete, try:</p>
<p>"Let me finish the recommendation, then I'll come to that."</p>
<p>Or:</p>
<p>"One sentence to close this point: the rollback is not yet tested."</p>
<p>Then finish. Do not turn the recovery into a second speech about being interrupted. If interruptions keep happening, ask the meeting lead for structure:</p>
<p>"Can we take the options in order so each owner can finish?"</p>
<p>These are tools, not obligations. If a direct response feels unsafe because of hierarchy or past treatment, use the written follow-up or ask an ally to help protect speaking turns.</p>
<ol start="3">
<li>Correct attribution with the work attached.</li>
</ol>
<p>When an idea you raised returns under somebody else's name, avoid guessing intent. Restore the record and move the decision forward:</p>
<p>"Yes, that's the staged approach I proposed in the design doc. The remaining question is who owns the rollback test."</p>
<p>If the idea changed through discussion, acknowledge that:</p>
<p>"That builds on my original proposal. Priya's retry change addresses the failure case we found."</p>
<p>Authority includes giving other people accurate credit. Make your own contribution equally visible in design docs, tickets, and review summaries. Describe what you did, not a bigger role you wish you had played.</p>
<ol start="4">
<li>Keep your accent. Clarify the content.</li>
</ol>
<p>You do not owe colleagues a different identity. If somebody misses a word, repeat the term, spell an identifier, or put it in chat. That is ordinary technical communication.</p>
<p>"The service is ledger-sync. I'll put the exact name in chat. My concern is duplicate processing after a retry."</p>
<p>If the feedback is vague, ask for an example:</p>
<p>"Which part was unclear: the term, the pace, or the recommendation?"</p>
<p>Specific feedback can help. "Sound more local" is not a useful engineering requirement. Clear communication is shared work: listeners can ask questions, and teams can use captions and written context.</p>
<ol start="5">
<li>Close with a record that others can correct.</li>
</ol>
<p>Send a short summary in the team's normal channel:</p>
<p>"Decision: staged rollout. I own the migration plan; Priya owns the rollback test. Open issue: duplicate processing after retries. Please correct anything I missed."</p>
<p>Only name owners and decisions that were actually agreed. If the meeting did not reach agreement, write that instead:</p>
<p>"No decision yet. The open question is whether the rollback test must pass before the pilot."</p>
<p>A precise record is more useful than a performance of certainty.</p>
<p>One honest caveat: scripts cannot fix a workplace that repeatedly dismisses you. If the pattern continues, keep factual notes and consider a conversation with a trusted manager, mentor, or an appropriate workplace support channel. The responsibility for fair treatment is not yours alone.</p>
<p>Commanding authority should mean making good judgment easier to hear, not making somebody else feel small. Say what you know. Mark what you do not know. Keep your name attached to your work, and leave room for others to do the same.</p>
]]></content:encoded></item><item><title><![CDATA[Color without the complexion rules: a workwear guide for South Asians in tech]]></title><description><![CDATA["Can I wear this color with brown skin?" is the wrong starting question for a work wardrobe. South Asians do not share one skin tone, one undertone, one…]]></description><link>https://theauthorityplaybook.hashnode.dev/color-without-the-complexion-rules-a-workwear-guide-for-south-asians-in-tech</link><guid isPermaLink="true">https://theauthorityplaybook.hashnode.dev/color-without-the-complexion-rules-a-workwear-guide-for-south-asians-in-tech</guid><category><![CDATA[career advice]]></category><category><![CDATA[Soft Skills]]></category><dc:creator><![CDATA[Mr Smith]]></dc:creator><pubDate>Fri, 13 Nov 2026 00:33:38 GMT</pubDate><content:encoded><![CDATA[<p>"Can I wear this color with brown skin?" is the wrong starting question for a work wardrobe. South Asians do not share one skin tone, one undertone, one style, or one relationship to color.</p>
<p>A better question is: does this outfit work for the setting, and do I like how I look in it?</p>
<p>This is a practical way to choose color for office days, interviews, and video calls without turning your complexion into a restriction. These are styling experiments, not scientific rules or promises about how other people will judge you.</p>
<ol>
<li>Start with two anchors you already enjoy.</li>
</ol>
<p>Pick two colors from clothes you actually wear. They might be navy and cream, charcoal and burgundy, black and olive, or brown and pale blue. There is no correct pair for South Asian skin.</p>
<p>Use those anchors to make combinations easier. If your trousers, shoes, and outer layer already work together, a different shirt does not require rebuilding the entire outfit.</p>
<p>Do a closet test before a shopping trip: lay out three combinations using what you own. Photograph them if that helps you remember. Keep the ones you would happily wear on a busy morning.</p>
<ol start="2">
<li>Judge the garment, not the color name.</li>
</ol>
<p>A thin white shirt, a textured cream knit, and an ivory cotton tunic are different objects. Fabric, opacity, cut, and condition matter alongside hue.</p>
<p>Check a light fabric in the lighting where you will wear it. Check whether you are comfortable with its coverage while seated and moving. Notice whether a dark item attracts lint or looks worn at the seams.</p>
<p>An outfit that needs constant monitoring is a poor tool for a long review meeting, however good its color looks in a photograph.</p>
<ol start="3">
<li>Test contrast on the actual camera.</li>
</ol>
<p>Open a private preview in the video-call app you use. Wear the top you are considering, with your usual background and lighting. Look at the full frame rather than only your face.</p>
<p>Can you see the outline of your shoulders? Is the pattern distracting to you? Does the camera make the fabric look different from real life? Try a plain alternative and compare.</p>
<p>If you blend into a dark background, change the top, the background, or the light. That is a setup problem, not a problem with your complexion. You do not need to lighten your skin or change your features to make a work call look clear.</p>
<ol start="4">
<li>Give a strong color a simple setting if you want one.</li>
</ol>
<p>Try a burgundy top with charcoal trousers, an emerald layer over a simple base, or a cobalt shirt with dark denim. If you prefer several strong colors together, that is a valid style too.</p>
<p>The point of a simpler combination is to make a decision easier, not to make you smaller. You can also keep cultural prints, embroidery, or jewelry in the outfit. Decide what you enjoy and what is practical for the day.</p>
<p>Do not confuse "I would style this differently" with "this is unprofessional." The latter should refer to a real, relevant workplace requirement, not somebody's personal taste.</p>
<ol start="5">
<li>Ask for useful feedback, not permission to exist.</li>
</ol>
<p>Instead of "Does this color suit brown people?" ask:</p>
<p>"Does this jacket work with these trousers?"</p>
<p>"Is the pattern distracting on this camera?"</p>
<p>"Would this meet the event's stated dress code?"</p>
<p>Specific questions produce something you can act on. A sweeping rule about your ethnicity does not.</p>
<p>If a colleague comments on your skin instead of the clothes, you can set a boundary without starting a debate:</p>
<p>"I'm comfortable with the color. Let's keep the feedback about the outfit."</p>
<p>The takeaway: keep the combinations that make getting ready easier and feel like you. Clothes can help you feel prepared; they cannot guarantee authority, erase bias, or substitute for your engineering judgment. You are choosing a palette, not applying for permission to be visible.</p>
]]></content:encoded></item><item><title><![CDATA[The tech-office outfit system: dress with authority without losing yourself]]></title><description><![CDATA[You have a design review at ten, lunch at your desk, and a customer call at three. You need one outfit that works for all of it, not a costume change…]]></description><link>https://theauthorityplaybook.hashnode.dev/the-tech-office-outfit-system-dress-with-authority-without-losing-yourself</link><guid isPermaLink="true">https://theauthorityplaybook.hashnode.dev/the-tech-office-outfit-system-dress-with-authority-without-losing-yourself</guid><category><![CDATA[career advice]]></category><category><![CDATA[Soft Skills]]></category><dc:creator><![CDATA[Mr Smith]]></dc:creator><pubDate>Fri, 13 Nov 2026 00:32:47 GMT</pubDate><content:encoded><![CDATA[<p>You have a design review at ten, lunch at your desk, and a customer call at three. You need one outfit that works for all of it, not a costume change between meetings.</p>
<p>For South Asians in tech, there is another question worth separating from the clothes: am I dressing for the work, or trying to make myself less noticeable? You do not owe anyone a less South Asian version of yourself. A useful wardrobe makes the day easier. It should not become an apology.</p>
<p>Here is a practical system. Treat these as starting points to test in your workplace, not rules about who gets to look professional.</p>
<ol>
<li>Build around your actual week.</li>
</ol>
<p>Write down the rooms you enter: home office, engineering floor, customer meeting, conference stage. Pick clothes for those rooms rather than an imagined executive lifestyle.</p>
<p>For an ordinary office day, try straight-leg trousers or dark jeans, a plain top, and an optional overshirt or cardigan. For a customer meeting, swap in tailored trousers and a structured layer. For a talk, rehearse in the entire outfit, including shoes and microphone placement.</p>
<p>The principle works across gender presentation. A blouse, knit, shirt, tunic, skirt, dress, or trouser combination can do the job. Choose what lets you work comfortably and feels like you.</p>
<ol start="2">
<li>Run the movement test before the mirror test.</li>
</ol>
<p>Sit down. Reach for a whiteboard. Put on your backpack. Walk up stairs. Check whether a waistband digs in, a neckline needs constant adjustment, or a sleeve fights you.</p>
<p>A fitted garment is not necessarily a tight garment. You want enough shape to look deliberate and enough room to forget about it. Religious dress, mobility needs, sensory comfort, and weather belong in this test from the start.</p>
<p>If one seam or hem is the problem, ask a tailor what is possible before replacing the item. You do not need a new wardrobe to make an existing one more useful.</p>
<ol start="3">
<li>Use a three-part outfit formula.</li>
</ol>
<p>Choose a base, a layer, and footwear. For example:</p>
<p>Office: charcoal trousers, a cream knit, and clean sneakers.</p>
<p>Customer review: the same trousers, a collared shirt or blouse, and loafers or another comfortable polished shoe.</p>
<p>Cold commute: the same base, a cardigan or jacket, and weather-appropriate boots.</p>
<p>These are options, not a dress code. Check your employer's actual expectations and any safety requirements. A lab or hardware floor may need a different answer from a software office.</p>
<ol start="4">
<li>Leave room for identity.</li>
</ol>
<p>A kurta, a dupatta, a turban, a hijab, jewelry, or a fabric you love does not need to be disguised to count as workwear. If you want to combine a familiar cultural piece with simpler separates, do that because you like the combination, not because your identity needs toning down.</p>
<p>If someone makes your clothes the topic when you are trying to discuss the work, a short redirect is enough:</p>
<p>"Thanks. On the architecture question, my recommendation is option B."</p>
<p>You can enjoy the conversation later. You do not have to host it during your presentation.</p>
<ol start="5">
<li>Prepare the outfit and the opening sentence together.</li>
</ol>
<p>Set out tomorrow's clothes, check for stains or repairs, and write the first sentence of your most important meeting:</p>
<p>"Today I need a decision on the migration plan. I recommend a staged rollout because it gives us a clear rollback point."</p>
<p>The outfit removes a distraction. The sentence gives the room a reason to listen.</p>
<p>One honest caveat: no jacket fixes bias, and nobody earns respect by meeting a clothing standard. Good work still needs recognition, fair management, and clear ownership. Use this system to spend less attention getting dressed and more attention on the decision you came to make.</p>
]]></content:encoded></item><item><title><![CDATA[How to disagree in a technical meeting without losing the room]]></title><description><![CDATA[Every engineering meeting has a moment where someone says something you think is wrong. The migration timeline is fantasy. The cache invalidation plan has…]]></description><link>https://theauthorityplaybook.hashnode.dev/how-to-disagree-in-a-technical-meeting-without-losing-the-room</link><guid isPermaLink="true">https://theauthorityplaybook.hashnode.dev/how-to-disagree-in-a-technical-meeting-without-losing-the-room</guid><category><![CDATA[career advice]]></category><category><![CDATA[Soft Skills]]></category><dc:creator><![CDATA[Mr Smith]]></dc:creator><pubDate>Fri, 13 Nov 2026 00:31:33 GMT</pubDate><content:encoded><![CDATA[<p>Every engineering meeting has a moment where someone says something you think is wrong. The migration timeline is fantasy. The cache invalidation plan has a hole in it. The incident review is about to pin the outage on the wrong cause.</p>
<p>Thanks for reading The Authority Playbook! Subscribe for free to receive new posts and support my work.</p>
<p>Subscribed</p>
<p>What you do in the next ten seconds is a career decision.</p>
<p>The default move for a lot of good engineers is to stay quiet, nod, and take it offline. Sometimes that is the right call. But in many North American engineering cultures, well-framed disagreement in the room is read as engagement, and consistent silence can cost you influence over decisions that shape your work.</p>
<p>Context comes first. Pushback lands differently depending on who is in the room, how much standing you have built, and what is actually at stake. If you are two weeks into a new job, or the decision is low-stakes and reversible, staying quiet and following up privately can be the smarter play. The goal is not to disagree everywhere. It is to have the skill ready when the decision matters.</p>
<p>When you do disagree in the room, a three-part structure keeps it constructive: name the shared goal, state your view, offer a path.</p>
<ol>
<li><p>Name the shared goal. Anchor to what everyone wants before you differ: "I want this migration to ship on time too."</p>
</li>
<li><p>State your view plainly, at an honest confidence level: "I see it differently: the timeline assumes the backfill runs clean, and the last two needed rollback windows." If you are not sure, say so and commit to an answer: "I do not know yet whether the index rebuild fits the window. I will have numbers by Thursday."</p>
</li>
<li><p>Offer a path. A disagreement with an alternative attached is a contribution; without one it reads as a complaint: "Can we cut the reporting schema from scope and migrate it in phase two?"</p>
</li>
</ol>
<p>Put together: "I want this migration to ship too. I see it differently: the timeline assumes the backfill runs clean, and the last two did not. Can we cut the reporting schema to phase two?"</p>
<p>Sometimes the room decides against you. That is normal. If the risk you raised is material - a data-loss risk, a compliance issue, a deadline the team will visibly miss - a short follow-up note is worth sending: "Happy to move ahead with the plan. Flagging for visibility: my concern is the backfill window, glad to revisit if we see issues in staging." Used selectively, a note like that documents your judgment without relitigating the decision. Used on every small call, it reads as covering yourself. Save it for the ones that matter.</p>
<p>If you get talked over, and in a loud room full of strong opinions you will, do not raise your voice. Hold the floor with a name and a bridge: "Let me finish this thought, then I want yours." Then finish the thought in one sentence. Calm persistence reads as seniority. Retreating mid-sentence reads as "never mind, it was not important."</p>
<p>One habit makes all of this easier: say something in the first ten minutes of the meeting, even something small. Ask the framing question ("what problem are we solving with this cache?"), build on someone's point, take an action item. If your disagreement is the first sound the room hears from you, it lands heavier than it should.</p>
<p>None of this guarantees agreement, and it will not fix a team that punishes dissent for the wrong reasons. That is a different problem, with different tools. But for the ordinary case - a decent room and a technical decision you genuinely see differently - this structure keeps both your point and your working relationships intact.</p>
<p>This is a free excerpt adapted from The Authority Playbook, a practical guide for South Asian and Asian engineers in North America, by Mr Smith. Subscribe to get the next one.</p>
<p>Thanks for reading The Authority Playbook! Subscribe for free to receive new posts and support my work.</p>
<p>Subscribed</p>
]]></content:encoded></item><item><title><![CDATA[Take up space: body language that reads as authority]]></title><description><![CDATA[Before you say a word in a meeting, the room has already read you. Where you sat down, what your hands are doing, whether you look settled or braced to…]]></description><link>https://theauthorityplaybook.hashnode.dev/take-up-space-body-language-that-reads-as-authority</link><guid isPermaLink="true">https://theauthorityplaybook.hashnode.dev/take-up-space-body-language-that-reads-as-authority</guid><category><![CDATA[career advice]]></category><category><![CDATA[Soft Skills]]></category><dc:creator><![CDATA[Mr Smith]]></dc:creator><pubDate>Wed, 11 Nov 2026 23:29:28 GMT</pubDate><content:encoded><![CDATA[<p>Before you say a word in a meeting, the room has already read you. Where you sat down, what your hands are doing, whether you look settled or braced to leave - people collect all of it in seconds, and they do it without deciding to.</p>
<p>Authority is partly spatial. It shows in how much space you comfortably occupy. This is trainable, and it matters more for people who were raised to be polite, deferential, and small - which describes a lot of us.</p>
<ol>
<li>Sit at the table. In a full meeting room, the wall chairs are where influence goes to wait. If there is a seat at the table, take it. If you present often, arrive early enough that you are choosing your seat rather than accepting the leftover one.</li>
<li>Plant yourself. Feet flat on the floor, both of them. Uncross your arms. Keep your hands visible - on the table, holding a pen, resting on your notebook. Hands under the table or clenched in your lap read as bracing. Visible, relaxed hands read as having nothing to hide.</li>
<li>Be still. Watch the most senior person in your next meeting. They are almost always the stillest - no pen clicking, no leg bouncing, no phone checking, no constant repositioning. Fidgeting leaks nervous energy into the room, and the room reads it as discomfort. Stillness reads as the person nothing in this room can rattle. If you take one habit from this article, take this one.</li>
<li>Move on purpose. Still does not mean statue. One deliberate movement is punctuation: lean in when you make your key point, lean back when you are listening. The contrast is what registers. Constant shifting registers as noise.</li>
<li>Hold eye contact one beat longer. When you are making a point, pick a person and finish the sentence to them. Then move to the next person for the next sentence. Sweeping the room mid-sentence, or addressing the table in front of you, thins out everything you say. One beat longer than comfortable is usually exactly right.</li>
<li>On video, manage the frame. Camera at eye level. Frame yourself from mid-chest up - looming two inches from the lens reads as anxious energy, and a camera pointing up your chin costs you presence in every call. Look into the camera, not at the grid of faces, when you land your most important sentences; to everyone watching, that is eye contact. And if your own video makes you self-conscious, hide self-view. You cannot be natural while watching yourself be natural.</li>
<li>Arrive like you belong. Rushing in three minutes late, apologizing, and dropping into the nearest chair spends your authority before the meeting starts. On time, unhurried, seated deliberately - the first thirty seconds of a meeting are a posture too.</li>
</ol>
<p>One caveat, and it matters: none of this is about performing dominance or copying some alpha-male stereotype. Taking up space is not about intimidating anyone. It is about removing the small signals of discomfort so the room is judging your ideas instead of your fidgeting. Stay yourself - just the settled version.</p>
]]></content:encoded></item><item><title><![CDATA[Stop over-explaining: how to answer like a senior engineer]]></title><description><![CDATA[Junior answers start at the beginning of the story. Senior answers start with the answer. Watch what happens when a director asks a room "Are we shipping…]]></description><link>https://theauthorityplaybook.hashnode.dev/stop-over-explaining-how-to-answer-like-a-senior-engineer</link><guid isPermaLink="true">https://theauthorityplaybook.hashnode.dev/stop-over-explaining-how-to-answer-like-a-senior-engineer</guid><category><![CDATA[career advice]]></category><category><![CDATA[Soft Skills]]></category><dc:creator><![CDATA[Mr Smith]]></dc:creator><pubDate>Wed, 11 Nov 2026 23:04:45 GMT</pubDate><content:encoded><![CDATA[<p>Junior answers start at the beginning of the story. Senior answers start with the answer.</p>
<p>Watch what happens when a director asks a room "Are we shipping Friday?" The junior answer: "So, on Monday we found an issue in the migration, and then we tried a few things, and the backfill was slower than expected, and..." The senior answer: "Yes, we ship Friday. The risk was the migration window; we cut scope to fit. Happy to walk through the tradeoffs if you want them."</p>
<p>Same facts. Completely different read. The first answer makes the listener dig for the part they asked for. The second gives it to them in three seconds and keeps the reasoning on tap. That pattern - headline first, detail on request - is one of the clearest signals of seniority there is, and it is a habit, not a personality trait.</p>
<p>In meetings, use a three-part shape: answer, reason, offer. Answer the question in one sentence. Give the one reason that matters. Offer more depth without forcing it: "I can go deeper if useful." If they want the journey, they will ask.</p>
<p>In writing, put the ask in the first line. The most common Slack message in engineering is three paragraphs of context ending in "so... could you possibly take a look?" Flip it. "Need your review on the auth PR by Thursday - context below." Then the context. Busy people decide in the first two lines whether a message is for them. If your request is in line twelve, you have made them mine for it, and mining feels like work.</p>
<p>In status updates, use three lines: Done. Blocked. Next. What moved, what is stuck and who unsticks it, what happens next. Nobody needs the screenplay. The update that fits in three lines is the one that gets read, and the one that gets read is the one that gets you unblocked.</p>
<p>When you do not know, stop walking toward an answer. The junior move is to start talking and hope the answer arrives mid-sentence. It rarely does, and the ramble costs more than the gap. "I do not know - I will find out by 3pm" is a complete senior answer. It is honest, it is fast, and it comes with a commitment.</p>
<p>Why do good engineers over-explain? Usually because the work was hard and they want it seen. That instinct is understandable and backwards. The place for the full story is the design doc, the postmortem, the demo. In the answer, the work speaks through the result. Saving the reasoning for people who ask does not hide your work - it signals you are confident the result holds up.</p>
<p>One caveat: some rooms genuinely want the reasoning. Design reviews, incident retros, mentoring a junior engineer - there, the journey is the point. Senior is not "always short." Senior is choosing the depth the audience needs: a director gets the headline, a teammate debugging with you gets the journey. The skill is telling the two apart.</p>
]]></content:encoded></item><item><title><![CDATA[Slow down: the speaking habits that make you sound senior]]></title><description><![CDATA[Two engineers give the same correct answer in a meeting. One sounds senior. One does not. The difference is almost never vocabulary. It is pace. Fast…]]></description><link>https://theauthorityplaybook.hashnode.dev/slow-down-the-speaking-habits-that-make-you-sound-senior</link><guid isPermaLink="true">https://theauthorityplaybook.hashnode.dev/slow-down-the-speaking-habits-that-make-you-sound-senior</guid><category><![CDATA[career advice]]></category><category><![CDATA[Soft Skills]]></category><dc:creator><![CDATA[Mr Smith]]></dc:creator><pubDate>Wed, 11 Nov 2026 22:52:13 GMT</pubDate><content:encoded><![CDATA[<p>Two engineers give the same correct answer in a meeting. One sounds senior. One does not. The difference is almost never vocabulary. It is pace.</p>
<p>Fast speech reads as nervous, and nervous reads as junior. When you rush, listeners hear someone trying to finish before they get interrupted - which tells the room that being interrupted is what you expect. Slow, even speech says the opposite: I expect you to listen until I am done.</p>
<ol>
<li><p>Pause instead of filling. Every "um," "like," and "you know" is a place where silence would have sounded better. Silence reads as thinking. Filler reads as stalling. The next time you feel a filler coming, close your mouth and let half a second pass. It feels longer to you than to anyone else. To the room, it sounds like weight.</p>
</li>
<li><p>Land your sentences. Ending a statement with a rising tone turns it into a question: "I think we should index that column?" You have asked the room whether your own statement is true. Let your pitch fall at the end of declarative sentences. Statements should sound like statements.</p>
</li>
<li><p>Cut the hedge stack. "I just think maybe we could possibly consider..." is four apologies before one idea. If you are genuinely unsure, use a single honest hedge and commit to closing the gap: "I am not certain yet - I will confirm by Thursday." If you are sure, say the thing: "The index fixes this."</p>
</li>
<li><p>Buy time out loud. When a hard question lands, do not start talking to fill the air. Say "Let me think about that for a second," then actually think. Senior people take time in public. Juniors sprint into an answer and spend the next two minutes walking it back.</p>
</li>
<li><p>Slow your first ten seconds. The opening of anything you say sets the pace for the rest. Before your first sentence in a meeting, a standup update, or an interview answer, take one breath. Start at three-quarters of the speed that feels natural. Nervous energy always pushes you faster than you think you are going.</p>
</li>
</ol>
<p>Practice is unglamorous but simple: record yourself answering one technical question out loud, once a week. Count the fillers. Listen for whether your statements land or float. Two or three weeks of this changes habits that years of meetings did not.</p>
<p>Two honest caveats. First, this is not about hiding an accent or performing a voice that is not yours. Accent is identity, and North American engineering is full of people who sound like the world. The levers are pace, pauses, and structure - those are trainable, and they are what rooms actually judge. Second, do not overcorrect into a slow robotic delivery. The goal is calm and deliberate, not a hostage video.</p>
]]></content:encoded></item><item><title><![CDATA[Dress for authority: how engineers get taken seriously before they speak]]></title><description><![CDATA[People decide how much authority to grant you before you finish your first sentence. That first read is mostly visual: fit, grooming, and how deliberate…]]></description><link>https://theauthorityplaybook.hashnode.dev/dress-for-authority-how-engineers-get-taken-seriously-before-they-speak</link><guid isPermaLink="true">https://theauthorityplaybook.hashnode.dev/dress-for-authority-how-engineers-get-taken-seriously-before-they-speak</guid><category><![CDATA[career advice]]></category><category><![CDATA[Soft Skills]]></category><dc:creator><![CDATA[Mr Smith]]></dc:creator><pubDate>Wed, 11 Nov 2026 22:25:53 GMT</pubDate><content:encoded><![CDATA[<p>People decide how much authority to grant you before you finish your first sentence. That first read is mostly visual: fit, grooming, and how deliberate you look. Two engineers walk into a design review with the same idea. The one who looks put-together gets the benefit of the doubt. The other one spends the meeting earning it.</p>
<p>This is not about fashion, and it is not about money. It is about signal. Clothes are the one part of your presence you can fully control, and most engineers leave that value on the table.</p>
<ol>
<li><p>Fit beats everything. A $40 shirt that fits beats a $400 shirt that does not, every time. Shoulder seams on your shoulders, sleeves ending at the wrist, pants that do not pool at the shoe. Find a tailor near you. Adjusting a shirt or a pair of pants costs $15 to $25, and it is the highest-return money you can spend on your career this year.</p>
</li>
<li><p>Dress one level up from the room. Look at what the median person in your office wears and go one step sharper, not five. In most tech offices that means clean dark jeans or chinos, a plain knit or an oxford shirt, and real shoes. A suit in a hoodie office does not read as authority; it reads as not understanding the room. One level up reads as the person who is going somewhere.</p>
</li>
<li><p>Build a uniform. Five to seven interchangeable pieces in neutral colors - navy, grey, black, white, olive - that all work together. You remove a daily decision, and you create consistency. Consistency reads as seniority. When people can picture what you wear, you have become a person with a presence, not a rotating cast of outfits.</p>
</li>
<li><p>Shoes and grooming carry more weight than you think. People look at shoes more than they admit. Keep them clean and in good repair; replace them before they collapse. Get a haircut on a schedule instead of when you notice you need one. If you have facial hair, make it look chosen - trimmed lines - rather than neglected.</p>
</li>
<li><p>On video, only three things show. Your top half, your lighting, and your background. Wear a collar or a clean knit on camera days. Put a light in front of you, not behind you. Raise the camera to eye level - a laptop camera pointing up at you costs you presence in every call. Keep the background quiet and boring.</p>
</li>
</ol>
<p>The common mistakes are all versions of not deciding: the free conference t-shirt at work, the wrinkled shirt that says you dressed in the dark, the giant logo that makes you look like a walking sponsor board, the overstuffed backpack from college. None of these are moral failures. They are just signals you did not choose.</p>
<p>One honest caveat: clothes do not make you competent, and no outfit rescues a bad idea. What good dressing does is remove a tax. It makes sure nobody's first impression of you is something you have to spend the meeting arguing with. Your ideas should be the most noteas should be the most noticeable thing about you. Dress so that they are.</p>
]]></content:encoded></item></channel></rss>