project engineer?

Somewhere between "Technical Lead", and "Technical Project Manager"... the former tends to focus more on driving the technology, the latter more on driving the overall development process.

Circuit Board Design Architect?

John :-#)#

Well, "project engineer" is as good as any - there are many titles.

The key is the job description, for which the description you provide (after some cleanup) would suffice.

I assume that this person must physically come to work every day. This should be made clear.

What should also be made clear is the minimum required experience level, by type and years - this cannot be a kid at all. Nor are academic degrees necessarily important, although there is likely a minimum.

Given that people of that experience level are widely sought, what is your case to them?

Joe Gwinn

Do you have enough of that work to justify a full time position?

Could call the position Product Development Engineering Manager (or engineer).

A PCB designer would be a different function. We need one of them too.

A good tech could do this. Nobody teaches this, or likely mentions this, in an EE curriculum.

Pay, benefits, location, fun projects, lots of variety, low bureaucracy, cabin in Truckee.

Yes. Just got hammered yesterday on another one. "The Guillotine Box."

PD engineer isn't bad.

Thanks

This person wouldn't guide technology - too many people want to do that already - but get individual projects done. Nobody would report to them. Done well, it is a very valuable function.

The deliverable on each project is the top assembly drawing and its BOM, and all that they imply.

Maybe specify senior or whatever level of experience you're looking for.

Un bel giorno John Larkin digitò:

It seems you are mixing two different job descriptions, "project leader" and "project manager".

Not easy to find people that can do both equally well.

I've known techs like that, but mostly this is usually an engineer.

If you say engineer, enterprising techs may also apply.

Yep. But the ad needs to address such things, or the right applicants don't call.

As for large companies with large bureaucracies, I always tell the young engineers is that while I have many bureaucracy-run-amuck stories, when people ask why work there, the answer is always because the toys are very large -- if you want to build ships, the corner machine shop just won't do.

Joe Gwinn

PO Engineer might be better (Pissed Off...)

John ;-#)#

Had me at 'cabin in Truckee'....

I wonder if that person is you. Who better knows what your people can do, and what not. And how fast/at what cost.

I've done too much of that. I want to design circuits, the opposite end of the process. Managing a project is hard work, and tedious to me. Some people like doing this function, like some people enjoy being cooks or bookkeepers or musicians.

Staff Engineer. Designs flagpoles.

Some suggestions (in random order):

1. Figurehead Engineer
2. Fearless Leader of the Engineering Pack
3. Alpha Engineer
4. Project Drift Realignment Engineer
5. Project Driver
6. Herder of Cats and Engineers
7. Macro Engineering Manager (as opposed to Micro Manager)
8. Member of the Engineering Management Staff
9. Engineering Friction Reducer
10. Managing Project Expediter
11. Engineering Team Leader
12. Maker of Tough Decisions
13. Managing Design Generalist
14. Collaboration Architect
15. Keeper of the Faith (from Planet of the Apes)
16. Manager of Everthing Else
17. Executive Assistant and Enforcer
18. Manager of Tedious Tasks
19. Inspector of Mortals
20. Director of the Herd
21. High Priest of the Overtime Tribe etc...