Profile picture

1 on 1 Meetings Q&A and Videos

About 1 on 1 Meetings

How can I effectively prepare for unexpected technical interviews that expect me to design a feature and have a working solution ready?

Software Engineer at Taro Community profile pic
Software Engineer at Taro Community

I recently had issues with management at my company and, out of frustration, changed my LinkedIn status to "Open to Work." I saw this as a chance to practice behavioral interviews, as Alex suggested in his course.

After completing some behavioral interviews with recruiters, I’m now scheduled to speak with hiring managers next week. Two companies have moved directly to the technical round based on my recruiter conversations. Most of these interviews are expected to happen over the next two weeks. I did not expect to get any technical interviews because I thought I wasn't good enough. But somehow it worked out better than I expected.

Here’s what I found out about the technical interviews from a follow-up email that I asked :

Both are live sessions.

The first company, which builds secure financial systems, provided this detail:

- "This is a filesystem design question combining design and live coding. The expectation is to present a complete solution, moving beyond pseudocode. Develop an approach/logic that can be fully implemented within the allotted time." - TypeScript & Node.js

The second company, which works in the distributed systems space requires a live coding assignment in Golang but gave no specific details.

I'm unsure how to best prepare. These aren’t straightforward like LeetCode problems, and there's no information on which libraries or resources to use. I haven’t done system design interviews before, and these companies expect a working coded solution. I've been attending system design sessions and group discussions with Taro, but live coding a feature is new to me.

I've done take-home assignments before, where there’s ample time to prepare, but this will be my first time coding a working component from scratch in a live interview. The pressure is higher since someone is constantly observing. I could treat these interviews as practice, but I don’t want to waste these opportunities. There's no guarantee of another chance, and I want to do well. This experience will be invaluable, and I don’t want to regret not giving it my best.

I was also wondering if I should ask more follow-up questions on the specifics of the technical interview like libraries to use, existing examples, resources to practice, etc. Is this too much to ask or is it fine?

Any guidance on preparing for these interviews would be greatly appreciated.

Show more
Posted a year ago
54 Views
2 Comments

Learn About 1 on 1 Meetings

1-on-1 meetings are important for building deep relationships and keeping key stakeholders in sync with the progress on a project. They can be an effective way to build deep relationships. These 1-on-1 meetings should be proactive, and they should ideally occur once a week for 30 minutes. It’s important to realize that there is a lot of value in 1-on-1 meetings because they can provide more depth of conversation than what can be provided in emails or team meetings. One has to be proactive in setting up meetings because it’s easy to wait too long to set up 1-on-1 meetings or consistently cancelling 1-on-1 meetings. The discomfort of discussing deeper, more emotional topics is where the majority of personal and professional growth happens.
It’s important to have a clear plan and agenda when having a 1-on-1 meeting with your manager. It makes the manager’s job easier, and it allows for a more focused conversation about tough topics. The purpose of the 1-on-1 meeting is to have proactive discussions where a manager and individual contributor can solve hanging threads and plan projects ahead. These meetings can be a powerful tool to discuss one’s career goals and seek alignment on solving the most pressing issues that a team faces. Managers can offer guidance, support skill development, and create a path for career advancement.
Remember that it’s important to embrace discomfort and avoid shying away from emotional topics during 1-on-1 meetings. Sharing feedback about what you’ve been doing, how you think things are going, and how you’re feeling can go a long way in building trust with the other person. It’s important to be genuine during these meetings because people are more willing to be vulnerable when they can sense that you are being vulnerable. Discussing what you liked or disliked about a project or meeting can lead to deeper conversations that can address problems from happening in the future.
1-on-1 meetings are an important part of effective management within a tech company. When they are approached with intentionality, these meetings become a necessary tool for fostering professional development, improving team dynamics, and driving overall success among individuals on a team.
Show more