There's an old tension in how organisations build teams: do you hire specialists who go deep, or generalists who go wide? For most of the last century, the answer was obvious. Specialise. Industries were stable enough, problems repeated often enough, and tools changed slowly enough that depth compounded.
The hardest part of building software has changed. It used to be the building itself — the months of development, the cost of getting it wrong, the weight of every commitment. When shipping a feature took a quarter, less than ideal prioritisation was easy to hide. Long cycles gave you cover
We don't have software engineers at Opply. Not because we don't write software — we write plenty — but because the title describes the wrong thing. It puts the emphasis on the output rather than the outcome. Job titles shape expectations. Expectations shape behaviour. Call someone a software