{
    "componentChunkName": "component---src-templates-blog-template-js",
    "path": "/blog/tips-to-succeed-at-a-systems-design-interview",
    "result": {"data":{"markdownRemark":{"html":"<p><span\n      class=\"gatsby-resp-image-wrapper\"\n      style=\"position: relative; display: block; margin-left: auto; margin-right: auto; max-width: 1042px; \"\n    >\n      <a\n    class=\"gatsby-resp-image-link\"\n    href=\"/static/d8be9ecfa42a8d566af0a1d76f17153f/5819f/cover.png\"\n    style=\"display: block\"\n    target=\"_blank\"\n    rel=\"noopener\"\n  >\n    <span\n    class=\"gatsby-resp-image-background-image\"\n    style=\"padding-bottom: 64.0625%; position: relative; bottom: 0; left: 0; background-image: url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAANCAYAAACpUE5eAAAACXBIWXMAAAsTAAALEwEAmpwYAAABT0lEQVQ4y32T63KCMBCF8/4v1dL2j4ptxwfwArVFFELIRQzo6ex2mIkU2Zkzmwnh20s2AoHdbrc7f71eUZYSpaxYWpt/Z4YmhqBevala4+X1DbP5Ar7t0HXdNHAI641+lFLieCoYKisFbcxo8FBiCGrbFsYYaK3hnEPTNLznvWc/FjxcixBkrWUYQR6VFMKoijBjYohK1TjkRyTpF46nE2cyVVIoqiJJEqRpiizLoJSCUNrg6TlCvHyHsWfO0PsLZzklghVFgTiOEUURVqsV91youoZ1Ds6dkR1yBtK4DHs0FBn1uCxLVp7nfxmG/WmaMx8KL4Pgj6wPHM6tGJs9ajYBq4oGWoI+0V7bdfB+Osjd2AzBdEFJusd6s8Vmu2O///5B23YPWyHGnl2/pox2SYrlxyfmi5gvb73dTb4WMTVnlKGxDs3Fsy7ew1o3CfwFH434E0ViaAIAAAAASUVORK5CYII='); background-size: cover; display: block;\"\n  ></span>\n  <img\n        class=\"gatsby-resp-image-image\"\n        alt=\"cover\"\n        title=\"cover\"\n        src=\"/static/d8be9ecfa42a8d566af0a1d76f17153f/5819f/cover.png\"\n        srcset=\"/static/d8be9ecfa42a8d566af0a1d76f17153f/72799/cover.png 320w,\n/static/d8be9ecfa42a8d566af0a1d76f17153f/6af66/cover.png 640w,\n/static/d8be9ecfa42a8d566af0a1d76f17153f/5819f/cover.png 1042w\"\n        sizes=\"(max-width: 1042px) 100vw, 1042px\"\n        style=\"width:100%;height:100%;margin:0;vertical-align:middle;position:absolute;top:0;left:0;\"\n        loading=\"lazy\"\n      />\n  </a>\n    </span></p>\n<p>At Loadsmart, the <a href=\"https://github.com/loadsmart/culture/blob/main/hiring/interviewing.md\">hiring process</a> consists of four steps:\nA screening interview, with one of our recruiters, a coding exercise, done through HackerRank, a system’s design interview, and, finally, a soft-skills interview.\nBut what to expect from a system’s design interview, and how to succeed at it?\nFirst of all, the system’s design, also known as the “architectural” interview has slightly different formats depending on the position you are applying for.\nIt will, however, always require you as a candidate to explain how you would approach a given problem, proposing a solution and then iterating over it as more requirements or variables are added.\nIt usually comes with a whiteboard so you can visually explain your thoughts and keep track of what you’ve built so far.\nWe evaluate not only your technical acumen but also your communication and ability to explain your ideas, according to the seniority of the position you have applied to.\nThere are no right or wrong answers, but there are solutions that would work all the time, there are solutions that could work most of the time and there are solutions that would not work at all.\nHere are 5 tips for you to convince the interviewer your solution falls under the first case.</p>\n<h3>Tip 1: Pay attention to the problem scope</h3>\n<p>One of the most common mistakes candidates make on architectural interviews is to go beyond what was asked in the problem statement.\nImagine that the scope is closed, every requirement is there.\nLater on, more variables and requirements will be added, so we will evaluate your ability to adapt your solution to this new scenario.\nAdding by yourself new requirements to the problem might indicate that you are not comfortable with the actual requirements and are trying to run away from them.\nSo the first tip is: Stick to the problem scope.</p>\n<h3>Tip 2: Do not over-engineer</h3>\n<p>We want to evaluate your ability to create complex systems, but also simple ones.\nIn a real-world scenario, you would unlikely start a project with dozens of servers and top-notch tools to intercommunicate them.\nStart lean, paying attention to the scope, and then evolve your solution as variables such as requests per minute are added.\nIf you’re in doubt, ask the interviewer.</p>\n<h3>Tip 3: Understand what you are proposing</h3>\n<p>In our industry, we are bombarded with new technologies each day, but if you pay attention, just a few of them really lasts.\nIf you propose using a technology X, Y, or Z, you are expected to explain why you think this technology is appropriate beside any personal preference.\nThis is what differentiates someone who knows that a tool exists from those who really understand the pros and cons of using it against an alternative.\nYou don’t need to be an expert on the low-level implementation of every technology, but in a real-world scenario, you would have to convince your peers why using X is better than Z for <em>that specific problem</em>.</p>\n<h3>Tip 4: Be decisive</h3>\n<p>If you can incorporate the 3rd tip this one will be easy.\nWe certainly have a lot of possibilities to solve each problem, but it is your role to decide on what is best and explain why.\nYour final answer cannot be “we could use X… or even Y… or perhaps Z”.\nDemonstrate confidence in saying “we should use Y for this problem because of this and that”.\nThere are cases that more than one solution applies, and that’s OK.\nIf you don’t know what to use, that’s perfectly fine, be honest and tell the interviewer you would need deeper research on the topic.\nNo one knows everything, and neither do interviewers, that’s why we need you to precisely explain the reasons that brought you to think the way you do.</p>\n<h3>Tip 5: Don’t be afraid to think</h3>\n<p>We do not expect you to have all the answers on the top of your head.\nSometimes you will need more time to think about the variables and circumstances your problem is subject to, and then decide how to tackle it.\nTake your time to reflect on the possibilities, and then explain the rationale behind your answer.\nThe interviewer will not rush you.</p>\n<h3>Final remarks</h3>\n<p>Hopefully, these tips will help you extract your best during the interview, which I can assure is a fun and friendly meeting.\nRemember it is not only about the <em>hard</em> skills, but also the <em>soft</em> ones, so take advantage of this challenge to exercise your communication, teach and learn new things.\nIf you think I forgot something, feel free to use the comments section and share your tips too, I’m sure it’ll help someone.</p>\n<p>Felt interested after those tips?\nTake a look at our <a href=\"https://jobs.lever.co/loadsmart\">careers page</a> for our open opportunities, and good luck!</p>","excerpt":"At Loadsmart, the hiring process consists of four steps:\nA screening interview, with one of our recruiters, a coding exercise, done through HackerRank, a system’s design interview, and, finally, a soft-skills interview.\nBut what to expect from a system’s design interview, and how to succeed at it?\nFirst of all, the system’s design, also known as the “architectural” interview has slightly different formats depending on the position you are applying for.\nIt will, however, always require you as a…","frontmatter":{"date":"February 23, 2022","path":"/blog/tips-to-succeed-at-a-systems-design-interview","title":"Tips to succeed at a system’s design interview","comments":true,"author":"Luiz Rosa"},"fields":{"readingTime":{"text":"4 min read"}}}},"pageContext":{}},
    "staticQueryHashes": ["63159454"]}