Introducing Tech Pulse: Your Guide to Acing Software Engineering Interviews and Thriving in Your Tech Career

What is Tech Pulse?

Welcome to Tech Pulse, a new publication for all things related to software engineering interviews, career success, and professional growth in the tech industry. This publication’s goal is to:

• Share real technical interview experiences.
• Evaluate offer letters and compensation.
• Provide resources to help you prepare for interviews, including guides on how to solve difficult technical questions, how to find companies to apply for, and how to do well in behavioral interviews.

We also want to go beyond the interview, by providing resources and tips for topics like:

• How to get promoted at your current role.
• Common issues like dealing with technical debt or estimating project timelines.
• When and how to leave your current role.

Why start this publication?

Having personally gone through rounds and rounds of software engineering interviews and tons of late nights preparing, I wanted to share my experiences with readers to help them prepare for their upcoming interviews. However, after I signed an offer, I don’t plan on interviewing again for a while — but I want to continue delivering software engineering interview and career-related content to readers.

Existing interview experience posts do exist (e.g. on Leetcode forums or TeamBlind), but often vary in quality and consistency, making it challenging to find reliable and useful information. Algorithm guides are often incorrect and job success tips are often misleading. Our editors will curate relevant articles, standardize the formatting to make it easier for our readers to follow, and select high-quality content we think our readers will find useful.

Want to contribute?

• Email techpulsepub@gmail.com with a link to the *draft* of your story. Learn how to do this here.
• If we think your story meets our standard, we’ll add you as a writer. Then, please submit a story following these instructions.
• If needed, we’ll make small edits to the content or format of your story.

Here’s a sample of posts we’re interested in (not exhaustive):

• Interview experiences. These should be end-to-end experiences, from the HR screen to the offer or rejection. Don’t share the exact questions you received unless you’re legally allowed to (most companies make you sign an NDA preventing you from doing this), but do share how difficult you thought the questions were or topics you think other candidates can prepare for. If you got an offer, it’s up to you if you want to share the compensation numbers.
• Algorithm guides. These should be easy to read and provide sufficient context to a reader who might not know what the algorithm is. Provide sets of questions on Leetcode the reader can then go practice this on, if relevant.
• Career tips and stories. For example, how you got promoted to a senior level engineer and a guide on how to do so.

Thank you for joining this community!