[Mvandenbergh]

Sure, he's an engineer. Most people who have computer science degrees work in software engineering jobs and wouldn't think of themselves as "computer scientists" since that is a scientific/mathematical academic discipline. (A very small percentage of software engineers are doing work that is both advancing theoretical computer science and building practical engineering solutions but they probably still think of themselves as engineers)

[forgetsusername]

>Sure, he's an engineer.

How is someone an engineer without an official engineering designation?

It's funny that Zuckerberg is dismissed as a computer scientist, but accepted as an engineer, proving how arbitrary these titles are.

[Mvandenbergh]

The software world has always been different. If you want to be precise, he's obviously not an engineer in the sense that mechanical, civil, electrical etc. engineers have professional licensing bodies with education requirements, licensing exams, and legally protected titles. On the other hand, by those standards there are almost no software engineers since even if parallel licensing regimes exist for them, almost nobody cares.

If we're using titles that describe what they do rather than professional licensing (which doesn't apply to software) then these people build software and lead teams that build software. That's software engineering. If you don't like the use of the word 'engineer' for someone who isn't a Professional Engineer then,

a) Tough, that boat has sailed.

b) Pick a different word, "software builder", "coding guy", whatever.

No matter how you slice it, they are not computer scientists.

[LordHumungous]

It's not that arbitrary. Computer scientists typically have PhDs and they publish papers on the theory of computer science. It doesn't mean "smart and works with computers."

[ZanyProgrammer]

Its the problem with software engineering in general-its accepted that one doesn't need a BS in computer science or software engineering.