Log in to the online community
It mentions various Expertise to chose from but doesn't talk of what to if these doesn't exactly match one's key areas. Since most of my experience has been interdisciplinary which doesn't fall under a specific category ( e.g. I worked on Engine control units but for Formula 1 which doesn't fall under Automotive(6); Or embedded software can be considered as Software(33) or Computing Software and System(11) depending on application). Specialisms are even more confusing 😟. I tried mapping my skills to the given list but most of the key skills partially overlap making it even harder to decide the one's that should be selected. Another problem is in the Career History section, especially the one that explains what 'Accessors' will be looking at in your application. It describes an Engineering manager's tasks rather than an Engineer's or Senior Engineer's role which makes me wonder if CENG will help me grow professionally as an Engineer. Although I have been involved in some of these tasks but not all mentioned in that section.
It also makes me wonder if CENG is actually something worth pursuing for an embedded software engineer. Also, is there a more detailed/ elaborate explanation of approaching the CENG application ?
I would seriously advice you to apply for CEng. Remember, what is provided is guidelines so can never fit a particular career path.
Do seek out your lical Professional Registration Adviser (PRA). Depending on where you are living/working, a local PRA would be assigned to you who will be able to guide you better.
I would reiterate Kirit's advice and say get a PRA. You can get one local to you, but in the current climate it is really immaterial where the PRA is since all contact is likely to be by email/videoconference.
One thing to set your mind at rest is that the 'expertise' that you choose has no influence on the assessment of your application but rather is used to try to help select interviewers who will understand your work and therefore be able to judge your actions better without having to ask basic questions.
The requirements for CEng are produced by the Engineering Council and of necessity are rather ambiguous as they have to cover all engineering disciplines from major civil engineering constructions (e.g. bridges and dams) to cutting edge technology of microelectronics and software. This is where a PRA is invaluable as they are trained in the requirements and understand how they apply in a variety of different situations.
Thank you for the advice. I will surely get in contact with one of the PRAs.
I have advised software engineers in my organisation on the CEng process and there is often a misconception that they need to be a people manager, but this is not the case. Software Engineers who have experience in providing technical authority over a system element or software sub-system can demonstrate the necessary competencies. If you have had autonomy to make technical decisions related to the software - for example in the architecture, detailed design, selection of tools/standards then these can be used as examples related to competencies A,B and C. For example, applicable achievements for A can include evaluation and selection of appropriate embedded software tools, techniques or approaches. Also consider that embedded software forms part of a wider system and will have interfaces to other components that will required clear definition, integration and validation, all of which provides opportunities to demonstrate competences.