[draaglom]

I can't speak for others, but as a hiring manager I prefer the latter because:

* It suggests the person understands the bigger picture behind what they're doing (rather than just "punching tickets")

* If your code sits in a 'financial critical path', this usually implies stricter requirements in your engineering in some respects -- you'll probably have had to think harder about reliability, cover more edge cases & co-ordinate with others more around requirements

[sokoloff]

I also prefer the second. Tech specifics aren’t anywhere near as important as the ability to be part of a team that finds value.

If you are a perfect fit tech skills-wise and can’t think/talk about the business side, you can make progress on our ticket backlog (and so we can still hire you), but if you’re moderately skilled at software in general but can connect that to the business problems, we can definitely use in a variety of spots.