In some organizations the title of Architect indicates the lead developer in a group. There may be more than one but it indicates the tip of the pyramid, not everyone in the group. I am sure that is not universal (see DJI) but I have seen it a lot.

>At DJI they called us Software Architects and that seemed to fit. Architecture to me implies knowing about aesthetics, function and the realities of construction. It also implies understanding context and pleasing the unique needs - and tastes - of clients.
>
>And while the architect often doesn't have to lay the bricks or wire the building, he'd better understand all those things. The best architects probably know how it feels to lay bricks.
>
>
>>To me, "computer engineering" means you design and build computers, no software. I've never really liked software engineer, but had employers give me the title. Guess I have to do that. The title I picked for myself in my company is "Chief Software Gardener"
>>
>>>I have never liked the phrase "computer engineering." There is a quantum difference between what we do and what engineers do. That's not saying we're a bunch of lugnuts, or that we cannot take a rigorous approach to our work, but they are very different. My younger daughter, who is an engineering major, was just here for a short visit. She brought a take-home midterm, which coincidentally is for a comp sci class they have to take. Holy moley. To me the questions looked very intimidating and made me grateful I am out of school. It's comp sci with an engineering spin. For instance, they study MaxPad, a language I had never heard of. (That's MaxPad, 6 letters <g>). She said it's designed for engineers and has things like functions which perform linear algebra. It gave me a headache just looking at it.