Role design and job descriptions for EV Charger Manufacturers: power electronics, firmware and field roles
An EV charger firm mixes power electronics, firmware, assembly and field service. Clear role pages say who designs, who tests, who commissions and who answers when a public charger fails.
Not sure what you need? Tell us about your business in six short steps and we will come to the first meeting prepared.
Share your requirementsWhy role design and job descriptions matters in EV charger manufacturers
In a young charger firm, engineers wear several hats. A power electronics engineer fixes firmware bugs, a firmware engineer answers a field call, and an assembly technician is asked to decide on a design change because the engineer is away. When a charger fails at a public site, nobody is sure who owns the fix, and each person remembers the split differently. Hiring suffers too, because adverts copy other firms' titles.
Good looks like a short page for each role: what the person owns, what they hand over and to whom, what decisions they can make alone and what skills they need. Boundaries between hardware, firmware, test and field are plain. The pages guide hiring, pay steps, training and who is called at night.
How to set it up
1. Draw the product path
Sketch the path from design to field: hardware design, firmware, prototype, assembly, burn-in, safety checks, installation, commissioning and service. Mark hand overs.
2. List who owns what at each stage
For each stage, write who owns the work, who reviews it and who is told when it goes wrong. Include field failures and cloud issues, which fall between roles.
3. Write a one page description per role
Include purpose, tasks, tools, decisions they can make, hand overs and skills needed. Ask the person in the role to read and correct it. for a method.
4. Define steps inside roles
Split roles such as assembly technician or field technician into levels, with what each can do alone. Link each level to pay and training. This gives a visible path.
5. Use the pages in hiring and cover
Put the pages in adverts and interviews. Use them to plan cover for absences, naming who steps in for whom. Review after each major product change.
Check these first
Before changing anything, find out what is true today. Use your own records for a defined period and note gaps in the evidence. The review may take longer if records are incomplete or spread across teams.
- Take the last three field failures and see whether you can name who owned each fix.
- List all engineers and the roles they cover beyond their title.
- Read your last engineer advert and compare it with what the engineer does in the first three months.
- Ask an assembly technician what decisions they may make on a design question.
GullyHR can do this with you. Read how we approach role design and job descriptions in general, or share your requirements and we will tell you where to start.
Questions owners ask
Describe the stable parts: what the person owns, who they hand to and what they decide. Leave out tool names that change. Review the page every six months as the product matures.
Yes once the team grows, since the skills differ. In a very small team, one person may cover both, but the page should still list each area and who backs them up.
Name one coordinator and write what they check: partner training, commissioning records and issues raised. Without a named owner, partner quality varies and field failures go unexplained.
We set up the interview and hiring process for EV charger manufacturers
Every business interviews, but few have a written process that works the same way for every role and every interviewer. GullyHR designs yours, from the role brief to the offer, trains your managers to run it, and can run it for you on the roles you hand us.