System design is the process of determining the optimal high-level technical approach to a problem. It's a staple in both the interview process and actually doing your job as a software engineer. We have created a video series to act as a system design primer for software engineers.
Hello Everyone,
I am new to Taro.
I wanted to ask if the Taro Book Club Event is recorded, if yes where can I access the recordings?
How do you keep up with everything that is happening on the team with different projects, doc designs and code reviews?
When working on a new task, I often find myself asked to estimate how long a task may take. Luckily, my team is pretty forgiving, but a critical step will be to start more accurately estimating tasks.
How do you get better at breaking down tasks to understand what needs to get done, and then giving proper estimations for how long those tasks will take?
I am good at LeetCode style problem solving and can also manage system design, but I never get interview calls when I apply through the company portals. Also recruiters barely accept LinkedIn requests and even those who accept them do not respond when reached out to for an open position.
I've been asked to write a design doc for my project; Samsara even has a structure to follow for these. After I understand how the overall system works, I will tackle. I want to make sure that there's a strong storytelling element in my doc, avoiding as much jargon as possible.
System design is a necessary process at software companies to design architectures that can be compatible with different requirements.