When dealing with complex systems. The person that sits down and decides what design patterns to use, what tools to implement, what protocols to consider, from my experience, is not something many devs can do right. This is where the architect comes in.
The engineer is someone that actually knows the tooling and uses it to build all the many parts of the system according to design specs. I find a lot of devs fall in this place.
A developer, for me, is just a generic term but also can be used to define someone who has no clue what various roles are required to build a system -- someone who might just Google something on how to solve a problem instead of knowing how to solve the problem and Googling the technicality involved in it.
So architects are good at deciding the ecosystem. Engineers are good at the tooling. General dev are good at general coding.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.