{"id":3310,"date":"2026-11-21T07:59:02","date_gmt":"2026-11-21T07:59:02","guid":{"rendered":"https:\/\/www.rajeshkumar.xyz\/blog\/?p=3310"},"modified":"2026-11-21T08:01:02","modified_gmt":"2026-11-21T08:01:02","slug":"assumptions-section-design-notes-career","status":"publish","type":"post","link":"https:\/\/www.rajeshkumar.xyz\/blog\/assumptions-section-design-notes-career\/","title":{"rendered":"Show Your Thinking: Writing Down Assumptions as a Career Skill"},"content":{"rendered":"<p>If you want your engineering work to stand out when a manager or recruiter skims it, show how you think, not only what you built. One of the simplest ways is to include a short section of written assumptions in every design note, ticket and portfolio project. This post lays out the skill in practical terms, with a Docker-based example, and explains why it is a career asset as much as a habit.<\/p>\n<h2>What hiring managers actually read<\/h2>\n<p>When someone reviews a portfolio repository or a design document, they look for signs of judgment. Does the author understand the limits of the solution? Can they explain when it would stop working? A paragraph that begins &#8220;This design assumes&#8230;&#8221; answers both questions quickly. It tells the reader that you know the edges of your work, which is a trait senior engineers value highly.<\/p>\n<p>It also gives interviewers something concrete to discuss. Instead of a generic question, they can pick a line from your page and ask how you would check it. That is a far better conversation than reciting tool names.<\/p>\n<h2>The three-part line<\/h2>\n<p>Each entry carries three elements, written in plain sentences:<\/p>\n<ul>\n<li><strong>What I am assuming.<\/strong> One claim, specific enough to be wrong.<\/li>\n<li><strong>How sure I am.<\/strong> High, medium or low, with a short reason.<\/li>\n<li><strong>How I would find out.<\/strong> The cheapest check, and what I would change if the answer is no.<\/li>\n<\/ul>\n<p>Resist the urge to polish. Direct, slightly blunt sentences read as confident, and they are easier to update.<\/p>\n<h2>A worked example: containerising a small web service<\/h2>\n<p>Imagine you are packaging a small web application as a container image and writing a one-page design note for a portfolio. Your assumptions section might say:<\/p>\n<ol>\n<li>The application is stateless, and any data it writes can be lost on restart. Confidence: medium. Check: search the code for local file writes; move any found to a mounted volume or external store.<\/li>\n<li>The base image receives security updates often enough for this project&#8217;s needs. Confidence: medium. Check: read the image&#8217;s maintenance notes and plan a rebuild schedule.<\/li>\n<li>Configuration can be supplied through environment variables alone. Confidence: high. Check: list every setting the application reads at start-up.<\/li>\n<li>One replica is enough for the expected load. Confidence: low. Check: run a basic load test and record where response time degrades.<\/li>\n<\/ol>\n<p>Each line connects to the practical advice found in articles such as <a href=\"https:\/\/www.rajeshkumar.xyz\/blog\/docker-best-practices-for-development-and-production-environments\/\">recommended Docker habits for development and production setups<\/a>. You can use that kind of resource to decide what to check, then record the finding on your page. Likewise, a look at <a href=\"https:\/\/www.rajeshkumar.xyz\/blog\/common-docker-mistakes-beginners-should-avoid\/\">slip-ups that newcomers make with Docker<\/a> will suggest more lines: many beginner mistakes are simply unchecked assumptions in disguise.<\/p>\n<h2>Turning the example into interview material<\/h2>\n<p>Take the four lines above and imagine you are asked about the project in an interview. The third line gives you a clean story: &#8220;I assumed configuration could come entirely from environment variables, listed every setting the app reads at start-up and found one value baked into a file. I moved it, and the note records the change.&#8221; That is three sentences, a concrete discovery and a fix. The fourth line gives you a story about testing: &#8220;I guessed one replica was enough, tried a basic load test and saw response times climb at a certain point, so I noted a scaling trigger.&#8221; Both answers show method rather than memorised definitions.<\/p>\n<p>Practise saying them aloud. If a line is hard to explain in under a minute, either the assumption was too vague or you have not yet checked it. Both are useful discoveries before the interview, not during it.<\/p>\n<h2>Why it helps a personal brand<\/h2>\n<p>A personal brand in engineering is a reputation for reliable thinking. Reputations are built from small, visible, repeated signals. A blog post that ends with &#8220;what I assumed and what turned out to be wrong&#8221; signals honesty, which is rarer than skill. A repository README with an assumptions list signals that you expect other people to build on your work. A conference talk or meetup session that reports which beliefs failed signals maturity. None of these requires a famous employer or a large audience.<\/p>\n<h2>Using the habit inside your current job<\/h2>\n<p>You do not need a side project to practise. In your day job, add an assumptions section to your next change request. Reviewers often thank people who do this, because it hands them the questions to ask. Over several months the colleagues around you will notice that your changes rarely cause surprises, and that is the kind of reputation that leads to larger responsibilities. Keep a private copy of the lines you wrote and what became of them; it will furnish true stories for review conversations and interviews.<\/p>\n<h2>What to do about the lines that turn out wrong<\/h2>\n<p>Do not delete them. A wrong assumption, honestly recorded, is some of the best material you will ever publish. Add a short &#8220;what I found&#8221; note: the date, the check you ran and the change you made. Over time, the pattern of your wrong lines also teaches you something about your blind spots. Perhaps you consistently overrate how stateless an application is, or underestimate how long dependency updates take. Spotting that pattern lets you adjust your first guesses in future projects, which is the real career benefit: your judgment improves because you kept the evidence of how it worked.<\/p>\n<h2>Practical rules to keep it credible<\/h2>\n<ul>\n<li>Never fake uncertainty to look humble. Mark confidence the way you really feel it.<\/li>\n<li>Keep every entry testable. If you cannot imagine a check, rewrite the line.<\/li>\n<li>Update the page when you learn something, with a date.<\/li>\n<li>Do not include anything that breaches confidentiality at your employer; generalise or use a personal project instead.<\/li>\n<\/ul>\n<h2>Where structured training fits<\/h2>\n<p>Some engineers like guided study to see how others document decisions. As one reference point, NoOpsSchool, a site from India, shows on its home page <a href=\"https:\/\/noopsschool.com\/\">menu entries for certification, courses, consulting and freelancer and service pages aimed at IT staff<\/a>. Whether you choose a structured route or teach yourself, the assumptions section costs nothing and works in any setting.<\/p>\n<h2>A five-minute starting exercise<\/h2>\n<p>Open the README of your most recent project. Add a heading called &#8220;Assumptions&#8221; and write four lines using the three-part pattern. Push the change with a clear commit message. The next time someone views the repository, they will see not only working code but also the reasoning that surrounds it. That is a small edit with a surprisingly large effect on how your work is read, and you can do it before the end of the evening.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>An assumptions section in every design note shows judgment to reviewers and hiring managers. A Docker example shows the three-part line and how to use it.<\/p>\n","protected":false},"author":6,"featured_media":3311,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[713],"tags":[],"series":[],"class_list":["post-3310","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devops-careers"],"_links":{"self":[{"href":"https:\/\/www.rajeshkumar.xyz\/blog\/wp-json\/wp\/v2\/posts\/3310","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.rajeshkumar.xyz\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.rajeshkumar.xyz\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.rajeshkumar.xyz\/blog\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/www.rajeshkumar.xyz\/blog\/wp-json\/wp\/v2\/comments?post=3310"}],"version-history":[{"count":1,"href":"https:\/\/www.rajeshkumar.xyz\/blog\/wp-json\/wp\/v2\/posts\/3310\/revisions"}],"predecessor-version":[{"id":3415,"href":"https:\/\/www.rajeshkumar.xyz\/blog\/wp-json\/wp\/v2\/posts\/3310\/revisions\/3415"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.rajeshkumar.xyz\/blog\/wp-json\/wp\/v2\/media\/3311"}],"wp:attachment":[{"href":"https:\/\/www.rajeshkumar.xyz\/blog\/wp-json\/wp\/v2\/media?parent=3310"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.rajeshkumar.xyz\/blog\/wp-json\/wp\/v2\/categories?post=3310"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.rajeshkumar.xyz\/blog\/wp-json\/wp\/v2\/tags?post=3310"},{"taxonomy":"series","embeddable":true,"href":"https:\/\/www.rajeshkumar.xyz\/blog\/wp-json\/wp\/v2\/series?post=3310"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}