Show your Backend Engineering Skills To Recruiters - Building a Full Backend Portfolio

Summary

In this video, a backend engineer shares insights on how to build an effective backend engineering portfolio. Rather than simply showcasing live projects, he emphasizes the importance of documenting your process through system design documents, architecture diagrams, and technical papers. He also suggests including books, blogs, videos, and podcasts to demonstrate expertise. The speaker shares personal experiences and advice on how to stand out to recruiters and prove your understanding of backend systems, stressing that a well-rounded portfolio will set you apart in the competitive tech industry.

Takeaways

• 😀 Build a live project and share the link to demonstrate your backend engineering skills, but ensure you can explain and understand how it works beyond just the final product.
• 😀 A system design document is crucial in showcasing your understanding of how your project functions, including architecture, workflows, and design choices.
• 😀 Architectural or system diagrams complement design documents by providing a visual representation of your project's architecture, making it easier to understand the system's interactions.
• 😀 UX/UI diagrams are important for front-end developers to showcase how users interact with the application, but they can also provide insight into the full user experience, not just the backend.
• 😀 Writing white papers on a problem you've solved, especially with technical depth, is an excellent way to demonstrate your knowledge, particularly for students or researchers.
• 😀 Writing books on specialized topics, such as geospatial or backend engineering, can position you as a subject matter expert and strengthen your portfolio.
• 😀 Creating a blog where you write about problems you’ve solved, technologies you’ve used, and your learnings can significantly enhance your professional presence and expertise.
• 😀 Videos are a powerful way to demonstrate your knowledge. As you continue to create content, you'll become more comfortable on camera and be able to express your expertise more clearly.
• 😀 Podcasting is another way to build your portfolio and demonstrate your expertise, especially when paired with videos. A large number of episodes can help showcase your consistent knowledge on a subject.
• 😀 You don't need to do all of the above to have a strong portfolio; picking a few tools like live projects, design documents, blog posts, or videos can still make a powerful impression.

Q & A

What is the main concern about showing backend engineering skills to recruiters?

The main concern is that simply showing a live project does not necessarily demonstrate a deep understanding of the work behind it. Recruiters want to see that a candidate knows the technical details and thought processes behind the project, not just that it works.

Why is sharing only a live project considered an incomplete way of showcasing backend skills?

A live project may show that a project works, but it doesn't demonstrate whether the candidate understands the underlying technologies and design choices. Recruiters want to know how well a candidate understands the systems they build, not just if they can use libraries and tools.

What is the purpose of writing a system design document?

The purpose of a system design document is to describe in detail the architecture of the project, including design choices, workflows, and technical specifications. It helps recruiters understand the candidate’s approach and decision-making process when building the system.

What are the benefits of including architectural or system diagrams in your portfolio?

Architectural diagrams provide a clear, visual representation of how different components of the system interact, making it easier for recruiters to understand the structure and design of the application. It complements written documentation by offering a quick, intuitive overview of the architecture.

How do UX/UI diagrams fit into a backend engineer's portfolio?

While UX/UI diagrams are typically more relevant to frontend engineers, they can be useful for backend engineers who are involved in designing the user experience or interfaces that interact with the backend. It shows an understanding of the end-user experience, even from a backend perspective.

How can writing a research paper help demonstrate backend engineering skills?

Writing a research paper allows candidates to showcase their ability to solve complex problems and dive deep into a topic, which demonstrates expertise in backend engineering. It also shows the ability to communicate technical concepts clearly and engage in critical thinking.

Why is writing books considered a powerful tool for building a backend engineering portfolio?

Writing books on a specific technical subject demonstrates a deep level of expertise and authority in the field. It shows that the candidate is knowledgeable enough to teach others and communicate complex ideas in a structured way, which can greatly enhance their credibility.

What role do blog posts play in a backend engineer’s portfolio?

Blog posts help establish a candidate as a thought leader by sharing insights, solutions to problems, or explanations of technical topics. Writing multiple blog posts demonstrates consistent engagement with the field and helps recruiters see a candidate’s depth of knowledge and communication skills.

How can videos and podcasts contribute to building a backend engineering portfolio?

Videos and podcasts allow backend engineers to share their expertise, discuss technologies, or teach concepts in a more engaging and personal way. They help build visibility and authority in the field, as well as showcase the candidate's communication and presentation skills.

What is the speaker’s advice on how many tools to use for building a portfolio?

The speaker advises not to try using all nine tools at once. Instead, select a few tools that align with your strengths and interests, and focus on doing them well. Quality and consistency are more important than trying to master everything at once.