[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"verticals":3,"article-junior-interview-expectations":44,"search-suggestions":198,"related-junior-interview-expectations":244,"comments-01a10c63-59c5-778b-9dad-342d71a1b8bd":308},[4,20,32],{"id":5,"slug":6,"name":7,"tagline":8,"description":9,"accentFrom":10,"accentTo":11,"icon":12,"defaultLocale":13,"locales":14,"features":16,"position":19},"019fe637-3d33-714b-b57f-23e163ffca0c","dev","Web Development","Read it. Run it. Prove it.","A post a day on modern web development — most with an editable playground and a quiz that explains every answer. Free, no account needed.","violet-500","cyan-400","◇","en",[13,15],"fa",{"courses":17,"paths":17,"articles":17,"exams":18,"flashcards":18,"packages":17,"community":17,"certificates":17,"teams":17,"commerce":17},true,false,0,{"id":21,"slug":22,"name":23,"tagline":24,"description":25,"accentFrom":26,"accentTo":10,"icon":27,"defaultLocale":13,"locales":28,"features":30,"position":31},"019fe637-3dc2-754c-8657-0f175bfee7c6","lang","Languages","Learn a language the way you learn a codebase.","Grammar explained the way good documentation explains an API — one idea at a time, each with a quiz.","amber-400","⌘",[13,15,29],"es",{"courses":18,"paths":18,"articles":17,"exams":18,"flashcards":17,"packages":18,"community":17,"certificates":17,"teams":18,"commerce":18},2,{"id":33,"slug":34,"name":35,"tagline":36,"description":37,"accentFrom":38,"accentTo":39,"icon":40,"defaultLocale":13,"locales":41,"features":42,"position":43},"7b3c16f2-931d-410e-802e-e1fa4edab7de","soft","Soft Skills","The half of the job nobody wrote documentation for.","Weekly, on the parts of working life that decide more than your code does — first weeks, meetings, interviews, promotions, and the people around you. Written from what actually happens, and recorded as a podcast you can listen to on the walk.","emerald-400","teal-300","◉",[13],{"courses":18,"paths":18,"articles":17,"exams":18,"flashcards":18,"packages":18,"community":17,"certificates":18,"teams":18,"commerce":18},3,{"id":45,"slug":46,"title":47,"subtitle":48,"excerpt":49,"coverUrl":50,"locale":13,"readingMinutes":51,"publishedAt":52,"viewCount":53,"likeCount":19,"commentCount":19,"author":54,"vertical":59,"topic":60,"tags":63,"_count":76,"playground":48,"body":77,"bodyMd":169,"seo":170,"translationGroupId":173,"series":174,"podcastUrl":48,"verticalId":33,"thread":193,"assessments":195,"translations":196,"quiz":48},"01a10c63-59c5-778b-9dad-342d71a1b8bd","junior-interview-expectations","Junior interviews don't test what they used to, and nobody updated you",null,"You prepped for an entry-level loop and got asked to defend tradeoffs like a senior hire. That's not the interviewer overreaching — the job underneath the title actually changed. Here's what they're listening for now, and the words that show it.","\u002Fmedia\u002Fcovers\u002Fjunior-interview-expectations.png",6,"2026-10-07T06:10:51.193Z",35,{"id":55,"name":56,"username":57,"avatarUrl":48,"headline":58},"019fe637-3c25-7088-9034-39c9f15dc3c8","Parsa Jiravand","parsa","Frontend engineer · building bestpractic",{"slug":34,"name":35,"accentFrom":38,"accentTo":39},{"slug":61,"name":62},"interviews","Getting hired",[64,67,70,73],{"slug":65,"name":66,"color":48},"career","Career",{"slug":68,"name":69,"color":48},"discuss","Discuss",{"slug":71,"name":72,"color":48},"beginners","Beginners",{"slug":74,"name":75,"color":48},"productivity","Productivity",{"assessments":19},{"blocks":78,"version":168},[79,83,87,90,93,96,100,103,106,109,112,115,118,121,124,127,130,133,137,140,143,146,149,152,155,162,165],{"id":80,"html":81,"type":82},"b1","\u003C!-- hello:start -->","paragraph",{"id":84,"html":85,"type":86},"b2","\u003Cp>👋 \u003Cstrong>I'm Parsa Jiravand — I work in IT, and this is Best Practice.\u003C\u002Fstrong> One article every day, one soft-skills episode every week. It all lives at \u003Cstrong>\u003Ca href=\"https:\u002F\u002Fbestpractic.org\u002F\">bestpractic.org\u003C\u002Fa>\u003C\u002Fstrong> — come join us.\u003C\u002Fp>\n","quote",{"id":88,"html":89,"type":82},"b3","\u003C!-- hello:end -->",{"id":91,"html":92,"type":82},"b4","\u003Cp>You're in a loop for a role with "junior" or "entry-level" somewhere in the title, and the interviewer just asked you to walk through how you'd design something, then pushed back on your first answer, then asked what would make you change your mind. You came in ready to explain a for-loop and got cross-examined like you're six years into this. You leave thinking you bombed it, or that you're underqualified for a job that was supposed to be the easy one.\u003C\u002Fp>",{"id":94,"html":95,"type":82},"b5","\u003Cp>You didn't bomb it. The job changed underneath the title, and nobody sent out a memo.\u003C\u002Fp>",{"id":97,"html":98,"text":98,"type":99,"level":31},"b6","What the junior job actually used to be","heading",{"id":101,"html":102,"type":82},"b7","\u003Cp>For a long time, "junior engineer" meant a specific, boring, valuable thing: you wrote the CRUD endpoint, you scaffolded the test file, you fixed the bug where the date was off by one, you wrote the first draft of the documentation nobody else wanted to write. It wasn't glamorous. It was also real work that needed doing, and doing it badly for a year or two was how you learned to do it well — with someone more senior checking your output line by line, which was its own kind of training you didn't even notice was training.\u003C\u002Fp>",{"id":104,"html":105,"type":82},"b8","\u003Cp>Here's the uncomfortable part: that specific list of tasks is almost exactly what AI tooling now does fastest and cheapest. Boilerplate, scaffolding, first-pass tests, routine fixes, a documentation draft — a senior engineer with a model open in another tab can produce all of that themselves, in less time than it takes to explain it to a new hire. So the tasks that used to justify a junior headcount got absorbed upward, into the senior engineer's own workflow. What's left, the part that didn't get absorbed, is judgment — noticing when the obvious approach is wrong, knowing when to stop and ask, catching your own mistake before it ships. That was never really the "junior" part of the job. It was the part you were supposed to grow into over a few years, with somebody checking your work the whole time.\u003C\u002Fp>",{"id":107,"html":108,"type":82},"b9","\u003Cp>That's the piece that broke. Companies still post junior roles. Some of them still mean it. But a lot of the loops are quietly testing for the leftover part — judgment — because that's the only part of the old job description that's still worth a human doing it. Nobody rewrote the posting to say that, because nobody's entirely sure how to word it yet. So you walk in prepared for the old test and get asked the new one.\u003C\u002Fp>",{"id":110,"html":111,"text":111,"type":99,"level":31},"b10","So what are they actually listening for?",{"id":113,"html":114,"type":82},"b11","\u003Cp>Not the right answer. They're listening for whether you can catch yourself.\u003C\u002Fp>",{"id":116,"html":117,"type":82},"b12","\u003Cp>When they ask you to walk through an approach, don't just state the answer — narrate the decision. "Here's what I'd try first, and here's the thing that would make me stop and try something else instead." That one sentence does more work than a correct solution delivered with no visible thinking, because it shows you have a way of checking your own output. That's the skill that used to get built by someone else checking it for you. Showing you already do some of that yourself is the whole signal.\u003C\u002Fp>",{"id":119,"html":120,"type":82},"b13","\u003Cp>When you genuinely don't know something — and in a junior loop you will hit one of these — say it plainly and show the next step: "I don't know that off the top of my head. I'd start by checking X, and if that didn't explain it I'd go look at Y." That's not a weaker answer than a guess. A confident wrong guess is the single worst thing you can do in this kind of loop right now, because it reads as exactly the failure mode they're trying to screen out: someone who needs a person standing over them to catch the thing they didn't know they didn't know.\u003C\u002Fp>",{"id":122,"html":123,"type":82},"b14","\u003Cp>And when they ask about a time something went wrong — even a small, practice-project, nothing-at-stake kind of wrong — give them the moment you noticed, not just the fix. "I noticed the numbers looked off before I'd even run the test, because they were too round" tells them something a fixed bug alone doesn't: that you were paying attention to your own work, not just producing it and moving on.\u003C\u002Fp>",{"id":125,"html":126,"type":82},"b15","\u003Cp>Some loops now ask the blunt version directly: why bring on someone junior at all, when the senior engineers already have the tooling to move fast on their own? Don't argue with the premise — it's half true. The honest answer is closer to: "Because someone still has to be the person who eventually doesn't need the tooling checked, and that only happens by doing the work now, badly at first, with someone watching." You're not claiming to be faster than the alternative. You're naming the thing you're actually there to become, which is a different pitch than the one the posting was written for a few years ago.\u003C\u002Fp>",{"id":128,"html":129,"text":129,"type":99,"level":31},"b16","Where this backfires",{"id":131,"html":132,"type":82},"b17","\u003Cp>Push this too far and you walk in performing total self-sufficiency — no hesitation, no "I'd want a second opinion on this," every answer delivered like you've never needed help. That's not what judgment looks like either. Judgment includes knowing the edge of what you know, and an interviewer who's actually any good can tell the difference between someone who's thought it through and someone who's just not admitting to any gaps. The honest "here's where I'd want someone more experienced to sanity-check me" is not a weaker answer. For a role with "junior" in the title, it's often the correct one — it shows you know the limit exists, which is most of the judgment they're testing for in the first place.\u003C\u002Fp>",{"id":134,"html":135,"text":136,"type":99,"level":31},"b18","The part that isn't fair, and I'll say it plainly","The part that isn't fair, and I'll say it plainly",{"id":138,"html":139,"type":82},"b19","\u003Cp>If you are genuinely new to this — no internship, no bootcamp project that shipped to real users, nothing — this bar is not fair to you yet, and pretending otherwise would be a lie dressed up as encouragement. Judgment about when to double-check your own work is something people build through reps, and if the industry quietly moved the goalposts on how many reps you're owed before you're expected to have it, that's not a gap in you. It's a gap in how the pipeline was supposed to work. You can still show up and demonstrate the small amount of judgment you do have — plenty of people have some, built from school, from side projects, from just paying close attention — but if you don't get the offer, it is worth knowing the test itself shifted, and not every company re-leveled their expectations to match. Some of what happens next is you finding the ones that did. And some of it, like most hiring, is luck and timing you don't control — who else applied that week, whether the team had budget that quarter, whether the interviewer had a good morning. Naming that doesn't mean the preparation doesn't matter. It means the preparation isn't the whole story, and you shouldn't carry the parts that aren't yours to carry.\u003C\u002Fp>",{"id":141,"html":142,"text":142,"type":99,"level":31},"b20","Monday",{"id":144,"html":145,"type":82},"b21","\u003Cp>Before your next interview, pick one technical decision from something you've actually built — a side project, a class assignment, anything — and practice saying it out loud, start to finish, including the part where you'd check yourself: what you'd try first, and the specific thing that would make you stop and reconsider. Say it to your phone, play it back. You're not rehearsing the answer. You're rehearsing the sentence that shows you'd catch your own mistake, because that's the sentence the room is actually listening for now.\u003C\u002Fp>",{"id":147,"type":148},"b22","divider",{"id":150,"html":151,"type":82},"b23","\u003Cp>🚀 \u003Cstrong>Want more like this?\u003C\u002Fstrong> Every guide, playground, and quiz lives on \u003Cstrong>\u003Ca href=\"https:\u002F\u002Fbestpractic.org\u002F\">bestpractic.org\u003C\u002Fa>\u003C\u002Fstrong> — open it and \u003Cstrong>\u003Ca href=\"https:\u002F\u002Fbestpractic.org\u002F\">sign up free\u003C\u002Fa>\u003C\u002Fstrong> so the next one finds you.\u003C\u002Fp>",{"id":153,"html":154,"type":82},"b24","\u003Cp>\u003Cem>Thanks for reading! Let's stay connected:\u003C\u002Fem>\u003C\u002Fp>",{"id":156,"type":157,"items":158,"ordered":18},"b25","list",[159,160,161],"⭐ \u003Cstrong>GitHub\u003C\u002Fstrong> — follow me and star the projects: \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fparsajiravand\">github.com\u002Fparsajiravand\u003C\u002Fa>","💬 \u003Cstrong>Discord\u003C\u002Fstrong> — join the frontend best-practices community: \u003Ca href=\"https:\u002F\u002Fdiscord.gg\u002Fd9KRhuAwQ\">discord.gg\u002Fd9KRhuAwQ\u003C\u002Fa>","📸 \u003Cstrong>Instagram\u003C\u002Fstrong> — frontend best practices, daily: \u003Ca href=\"https:\u002F\u002Fwww.instagram.com\u002Fbestpractice___\u002F\">@bestpractice___\u003C\u002Fa>",{"id":163,"html":164,"type":82},"b26","\u003Cp>🤝 \u003Cstrong>Want to make something with us?\u003C\u002Fstrong> Write a piece, come on the podcast, or bring an idea that should exist — \u003Cstrong>\u003Ca href=\"https:\u002F\u002Fbestpractic.org\u002Fcollaborate\">bestpractic.org\u002Fcollaborate\u003C\u002Fa>\u003C\u002Fstrong>.\u003C\u002Fp>",{"id":166,"html":167,"type":82},"b27","\u003Cp>\u003Cem>And if this one helped, send it to the person you know who needs it this week. That's what keeps these coming.\u003C\u002Fem>\u003C\u002Fp>",1,"\u003C!-- hello:start -->\n\n> 👋 **I'm Parsa Jiravand — I work in IT, and this is Best Practice.** One article every day, one soft-skills episode every week. It all lives at **[bestpractic.org](https:\u002F\u002Fbestpractic.org\u002F)** — come join us.\n\n\u003C!-- hello:end -->\n\nYou're in a loop for a role with \"junior\" or \"entry-level\" somewhere in the title, and the interviewer just asked you to walk through how you'd design something, then pushed back on your first answer, then asked what would make you change your mind. You came in ready to explain a for-loop and got cross-examined like you're six years into this. You leave thinking you bombed it, or that you're underqualified for a job that was supposed to be the easy one.\n\nYou didn't bomb it. The job changed underneath the title, and nobody sent out a memo.\n\n## What the junior job actually used to be\n\nFor a long time, \"junior engineer\" meant a specific, boring, valuable thing: you wrote the CRUD endpoint, you scaffolded the test file, you fixed the bug where the date was off by one, you wrote the first draft of the documentation nobody else wanted to write. It wasn't glamorous. It was also real work that needed doing, and doing it badly for a year or two was how you learned to do it well — with someone more senior checking your output line by line, which was its own kind of training you didn't even notice was training.\n\nHere's the uncomfortable part: that specific list of tasks is almost exactly what AI tooling now does fastest and cheapest. Boilerplate, scaffolding, first-pass tests, routine fixes, a documentation draft — a senior engineer with a model open in another tab can produce all of that themselves, in less time than it takes to explain it to a new hire. So the tasks that used to justify a junior headcount got absorbed upward, into the senior engineer's own workflow. What's left, the part that didn't get absorbed, is judgment — noticing when the obvious approach is wrong, knowing when to stop and ask, catching your own mistake before it ships. That was never really the \"junior\" part of the job. It was the part you were supposed to grow into over a few years, with somebody checking your work the whole time.\n\nThat's the piece that broke. Companies still post junior roles. Some of them still mean it. But a lot of the loops are quietly testing for the leftover part — judgment — because that's the only part of the old job description that's still worth a human doing it. Nobody rewrote the posting to say that, because nobody's entirely sure how to word it yet. So you walk in prepared for the old test and get asked the new one.\n\n## So what are they actually listening for?\n\nNot the right answer. They're listening for whether you can catch yourself.\n\nWhen they ask you to walk through an approach, don't just state the answer — narrate the decision. \"Here's what I'd try first, and here's the thing that would make me stop and try something else instead.\" That one sentence does more work than a correct solution delivered with no visible thinking, because it shows you have a way of checking your own output. That's the skill that used to get built by someone else checking it for you. Showing you already do some of that yourself is the whole signal.\n\nWhen you genuinely don't know something — and in a junior loop you will hit one of these — say it plainly and show the next step: \"I don't know that off the top of my head. I'd start by checking X, and if that didn't explain it I'd go look at Y.\" That's not a weaker answer than a guess. A confident wrong guess is the single worst thing you can do in this kind of loop right now, because it reads as exactly the failure mode they're trying to screen out: someone who needs a person standing over them to catch the thing they didn't know they didn't know.\n\nAnd when they ask about a time something went wrong — even a small, practice-project, nothing-at-stake kind of wrong — give them the moment you noticed, not just the fix. \"I noticed the numbers looked off before I'd even run the test, because they were too round\" tells them something a fixed bug alone doesn't: that you were paying attention to your own work, not just producing it and moving on.\n\nSome loops now ask the blunt version directly: why bring on someone junior at all, when the senior engineers already have the tooling to move fast on their own? Don't argue with the premise — it's half true. The honest answer is closer to: \"Because someone still has to be the person who eventually doesn't need the tooling checked, and that only happens by doing the work now, badly at first, with someone watching.\" You're not claiming to be faster than the alternative. You're naming the thing you're actually there to become, which is a different pitch than the one the posting was written for a few years ago.\n\n## Where this backfires\n\nPush this too far and you walk in performing total self-sufficiency — no hesitation, no \"I'd want a second opinion on this,\" every answer delivered like you've never needed help. That's not what judgment looks like either. Judgment includes knowing the edge of what you know, and an interviewer who's actually any good can tell the difference between someone who's thought it through and someone who's just not admitting to any gaps. The honest \"here's where I'd want someone more experienced to sanity-check me\" is not a weaker answer. For a role with \"junior\" in the title, it's often the correct one — it shows you know the limit exists, which is most of the judgment they're testing for in the first place.\n\n## The part that isn't fair, and I'll say it plainly\n\nIf you are genuinely new to this — no internship, no bootcamp project that shipped to real users, nothing — this bar is not fair to you yet, and pretending otherwise would be a lie dressed up as encouragement. Judgment about when to double-check your own work is something people build through reps, and if the industry quietly moved the goalposts on how many reps you're owed before you're expected to have it, that's not a gap in you. It's a gap in how the pipeline was supposed to work. You can still show up and demonstrate the small amount of judgment you do have — plenty of people have some, built from school, from side projects, from just paying close attention — but if you don't get the offer, it is worth knowing the test itself shifted, and not every company re-leveled their expectations to match. Some of what happens next is you finding the ones that did. And some of it, like most hiring, is luck and timing you don't control — who else applied that week, whether the team had budget that quarter, whether the interviewer had a good morning. Naming that doesn't mean the preparation doesn't matter. It means the preparation isn't the whole story, and you shouldn't carry the parts that aren't yours to carry.\n\n## Monday\n\nBefore your next interview, pick one technical decision from something you've actually built — a side project, a class assignment, anything — and practice saying it out loud, start to finish, including the part where you'd check yourself: what you'd try first, and the specific thing that would make you stop and reconsider. Say it to your phone, play it back. You're not rehearsing the answer. You're rehearsing the sentence that shows you'd catch your own mistake, because that's the sentence the room is actually listening for now.\n\n---\n\n🚀 **Want more like this?** Every guide, playground, and quiz lives on **[bestpractic.org](https:\u002F\u002Fbestpractic.org\u002F)** — open it and **[sign up free](https:\u002F\u002Fbestpractic.org\u002F)** so the next one finds you.\n\n*Thanks for reading! Let's stay connected:*\n\n- ⭐ **GitHub** — follow me and star the projects: [github.com\u002Fparsajiravand](https:\u002F\u002Fgithub.com\u002Fparsajiravand)\n- 💬 **Discord** — join the frontend best-practices community: [discord.gg\u002Fd9KRhuAwQ](https:\u002F\u002Fdiscord.gg\u002Fd9KRhuAwQ)\n- 📸 **Instagram** — frontend best practices, daily: [@bestpractice___](https:\u002F\u002Fwww.instagram.com\u002Fbestpractice___\u002F)\n\n🤝 **Want to make something with us?** Write a piece, come on the podcast, or bring an idea that should exist — **[bestpractic.org\u002Fcollaborate](https:\u002F\u002Fbestpractic.org\u002Fcollaborate)**.\n\n*And if this one helped, send it to the person you know who needs it this week. That's what keeps these coming.*",{"title":47,"canonical":171,"description":172},"https:\u002F\u002Fbestpractic.org\u002Fblog\u002Fjunior-interview-expectations","You prepped for an entry-level loop and got asked to defend tradeoffs like a senior hire. That's not the interviewer overreaching — the job underneath the title actually changed. H","01a10c63-59c5-778b-9dad-39087eb54373",{"name":35,"part":175,"total":175,"items":176},4,[177,182,187,192],{"slug":178,"title":179,"publishedAt":180,"readingMinutes":181},"first-week-at-a-new-job","Nobody tells you the question window is closing","2026-08-25T08:53:57.723Z",7,{"slug":183,"title":184,"publishedAt":185,"readingMinutes":186},"speaking-up-in-meetings","You're not quiet in meetings, you're editing","2026-09-02T10:58:23.112Z",9,{"slug":188,"title":189,"publishedAt":190,"readingMinutes":191},"code-review-comments","Why your code review comments sound harsher than you meant","2026-09-30T06:11:19.028Z",8,{"slug":46,"title":47,"publishedAt":52,"readingMinutes":51},{"id":194,"locked":18},"01a10c63-5a10-743e-aca9-a2c43854fa2b",[],[197],{"locale":13,"slug":46},[199,203,207,211,215,219,223,227,231,235,238,241],{"slug":200,"name":201,"articles":202},"webdev","Webdev",127,{"slug":204,"name":205,"articles":206},"javascript","Javascript",105,{"slug":208,"name":209,"articles":210},"frontend","Frontend",80,{"slug":212,"name":213,"articles":214},"tutorial","Tutorial",49,{"slug":216,"name":217,"articles":218},"css","Css",40,{"slug":220,"name":221,"articles":222},"typescript","Typescript",18,{"slug":224,"name":225,"articles":226},"performance","Performance",16,{"slug":228,"name":229,"articles":230},"react","React",15,{"slug":232,"name":233,"articles":234},"browser","Browser",12,{"slug":236,"name":237,"articles":234},"node","Node",{"slug":239,"name":240,"articles":186},"html","Html",{"slug":242,"name":243,"articles":191},"accessibility","Accessibility",{"items":245,"meta":307},[246,257,275,291],{"id":45,"slug":46,"title":47,"subtitle":48,"excerpt":49,"coverUrl":50,"locale":13,"readingMinutes":51,"publishedAt":52,"viewCount":247,"likeCount":19,"commentCount":19,"author":248,"vertical":249,"topic":250,"tags":251,"_count":256,"playground":48,"hasQuiz":18,"hasPlayground":18},36,{"id":55,"name":56,"username":57,"avatarUrl":48,"headline":58},{"slug":34,"name":35,"accentFrom":38,"accentTo":39},{"slug":61,"name":62},[252,253,254,255],{"slug":65,"name":66,"color":48},{"slug":68,"name":69,"color":48},{"slug":71,"name":72,"color":48},{"slug":74,"name":75,"color":48},{"assessments":19},{"id":258,"slug":188,"title":189,"subtitle":48,"excerpt":259,"coverUrl":260,"locale":13,"readingMinutes":191,"publishedAt":190,"viewCount":261,"likeCount":19,"commentCount":19,"author":262,"vertical":263,"topic":264,"tags":267,"_count":274,"playground":48,"hasQuiz":18,"hasPlayground":18},"01a0ec73-1496-7457-92a3-031fc4cd640c","A review comment loses your tone on the way, and the author fills it back in — usually with a worse one, at the exact moment they're most attached to the work. Here's how to put the weight back into what you write, the words to use, and when to stop typing.","\u002Fmedia\u002Fcovers\u002Fcode-review-comments.png",100,{"id":55,"name":56,"username":57,"avatarUrl":48,"headline":58},{"slug":34,"name":35,"accentFrom":38,"accentTo":39},{"slug":265,"name":266},"people","The people around you",[268,269,272,273],{"slug":65,"name":66,"color":48},{"slug":270,"name":271,"color":48},"codereview","Codereview",{"slug":71,"name":72,"color":48},{"slug":68,"name":69,"color":48},{"assessments":19},{"id":276,"slug":183,"title":184,"subtitle":48,"excerpt":277,"coverUrl":278,"locale":13,"readingMinutes":186,"publishedAt":185,"viewCount":279,"likeCount":19,"commentCount":19,"author":280,"vertical":281,"topic":282,"tags":285,"_count":290,"playground":48,"hasQuiz":18,"hasPlayground":18},"01a05274-fd83-71ed-9890-3cc8c1004104","The reason you don't speak up isn't confidence. Everyone else is thinking out loud while you wait for your thought to be finished — and a good point at minute thirty is worth less than a rough one at minute twelve. Here's how to land it on time.","\u002Fmedia\u002Fcovers\u002Fspeaking-up-in-meetings.png",217,{"id":55,"name":56,"username":57,"avatarUrl":48,"headline":58},{"slug":34,"name":35,"accentFrom":38,"accentTo":39},{"slug":283,"name":284},"meetings","Meetings and rooms",[286,287,288,289],{"slug":65,"name":66,"color":48},{"slug":68,"name":69,"color":48},{"slug":74,"name":75,"color":48},{"slug":71,"name":72,"color":48},{"assessments":19},{"id":292,"slug":178,"title":179,"subtitle":48,"excerpt":293,"coverUrl":294,"locale":13,"readingMinutes":181,"publishedAt":180,"viewCount":295,"likeCount":19,"commentCount":19,"author":296,"vertical":297,"topic":298,"tags":301,"_count":306,"playground":48,"hasQuiz":18,"hasPlayground":18},"01a037b3-d788-7645-99a4-a90f94ed0e61","In your first week you get to ask anything and it costs nothing. That window shuts quietly, usually around week three, and nobody announces it. Here's how to use it before it goes.","\u002Fmedia\u002Fcovers\u002Ffirst-week-at-a-new-job.png",500,{"id":55,"name":56,"username":57,"avatarUrl":48,"headline":58},{"slug":34,"name":35,"accentFrom":38,"accentTo":39},{"slug":299,"name":300},"starting","Starting somewhere new",[302,303,304,305],{"slug":65,"name":66,"color":48},{"slug":71,"name":72,"color":48},{"slug":74,"name":75,"color":48},{"slug":68,"name":69,"color":48},{"assessments":19},{"page":168,"perPage":181,"total":175,"totalPages":168},{"locked":18,"total":19,"comments":309},[]]