• 0 Posts
  • 105 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle














  • As a senior engineer recently turned manager I hear this type of mentality from most of my junior all the way up to senior devs.

    The only thing I’d suggest to you is spend some time digging into the tools you’re building outside of the project you’re working on. Just to get a general understanding of how the pieces fit together. Definitely do it during work hours, though. I’m in no way suggesting outside of work, here. Once you’ve spent enough time digging, you’ll surprise yourself in how effective you get at answering questions.



  • I’ve never seen a problem with asking people to code in a live session. It’s about the problems they are asked to solve. Leetcode style problems are generally unrealistic and have little to do with the skills that are actually needed.

    If the problems were more focused on the day to day type of work, nobody would complain. “solve x problem without the industry standard library that solves that problem already” is just testing the ability to quickly reinvent wheels.


  • For the goal you have, the best thing to do is find something you’re passionate about and build something for it.

    Ask yourself what do you love to do outside of programming? What is some problem you have that you could solve by writing a a piece of software?

    You are more likely to complete a project that you are passionate about and when you speak about it in an interview your passion will show and excite the interviewer.

    If there is an industry you are interested in, try to attend conventions that are relevant and go speak to the reps at the companies you are most interested in and ask questions about their products. Ask if they have any internship programs coming up and who to speak to after you’ve shown interest in their projects.

    Source: an engineering manager who is not currently hiring