1 pointby jmoosh349 hours ago4 comments
  • jack_sunsetless8 hours ago
    Knowing how one specific system really behaves. Docs only get you part of the way. Recently I spent a lot of time running an old Microsoft API side by side with its replacement, and a good part of the differences aren't written down anywhere. AI reads docs well, but it can't know what's missing from them.
  • turtleyacht9 hours ago
    As the candidate, ask good questions:

    An Engineering Leader's Behavioral Interview Template (2025) - https://news.ycombinator.com/item?id=43799184

    • jmoosh345 hours ago
      This was actually a great read!
  • andsoitis9 hours ago
    Put yourself in the shoes of someone hiring a software engineer. What do you think you would be looking for?
    • jmoosh349 hours ago
      So my main guess is on basically being able to map business requirements into business logic, but that is also hard to grasp on an interview.
      • andsoitis9 hours ago
        What about system architecture, tradeoffs, handling ambiguity, judgment, communication clarity, domain expertise, testing strategy, etc.?
        • jmoosh345 hours ago
          Yeah those are great points actually
  • spottedmarley9 hours ago
    An entirely new job? Or do you mean a new job as a different type software engineer? I'm afraid that in these days of AI software development the major differences between two capable software engineers is their AI skills and, perhaps, their physical appearance so, brush your hair, dress nice, smile and dazzle them with your ability to steer coding agents.
    • jmoosh349 hours ago
      Yeah, more like the same role on a different project