How I Achieved EngTech as a Placement Student

During my year in industry, Engineering Technician registration — EngTech — was put in front of me as something I might be able to achieve before graduating.

I had heard of Chartered Engineer, but I did not know much about EngTech or how professional registration actually worked. I assumed it was probably something for people who had already been working for years, rather than somebody still completing a degree and a placement.

After looking into it, I realised that EngTech is based on the engineering competence and responsibility you can demonstrate. There is no rule saying that you have to wait until you graduate or reach a particular age.

I decided to give it a go, and I have now achieved EngTech through the Institution of Engineering and Technology (IET).

This post is a practical account of what I did, how the UK-SPEC competence framework works, what sort of evidence I used and what I would tell another placement student considering an application.

A note before starting: this is my own experience of applying through the IET in 2024. Processes and fees can change, so check the current IET and Engineering Council guidance before applying.

What is EngTech?

EngTech stands for Engineering Technician. It is one of the professional registration titles awarded through the Engineering Council, alongside Incorporated Engineer (IEng) and Chartered Engineer (CEng).

You do not apply directly to the Engineering Council. You apply through a licensed professional engineering institution, such as the IET. The institution assesses your qualifications, experience, competence and professional commitment against the relevant UK standard. If you are successful, it submits your registration to the Engineering Council.

In simple terms:

• the Engineering Council sets the UK standard and maintains the professional register;
• the IET is the professional institution I joined and applied through;
• UK-SPEC describes the competence and commitment I needed to demonstrate;
• Career Manager is the IET system I used to work on and submit my application.

EngTech is aimed at people who apply proven engineering techniques and procedures to practical engineering problems. It is not awarded simply because somebody has a particular job title or qualification. You need to show how you have applied engineering knowledge, worked safely, accepted responsibility, communicated with others and behaved professionally.

Why I applied during my year in industry

I did not begin my placement with a detailed plan to become professionally registered. EngTech was more or less waved in front of me as an opportunity that placement students could work towards.

That got my attention.

A year in industry gives you something university cannot provide on its own: evidence of how you work when engineering decisions affect real equipment, real projects, other people and, in my case, work in a highly regulated environment.

During my placement, I was gaining experience in areas including:

• reviewing engineering drawings and technical information;
• selecting between possible engineering approaches;
• contributing to design changes;
• completing plant surveys;
• preparing and following test documentation;
• considering safety, cost, quality and security;
• communicating with engineers, operators and other stakeholders;
• recording decisions and producing controlled documents;
• taking responsibility for my own work;
• continuing my professional development.

Once I looked at the EngTech requirements properly, I realised that I already had useful evidence. The main challenge was not finding fifteen completely separate projects. It was understanding what each experience demonstrated and explaining my own contribution clearly.

Joining the IET

I applied through the IET because it was relevant to my area of engineering and provided a route to EngTech registration.

At the time, student membership cost me around £20, which made joining an easy decision. Student fees change, and some universities or employers may already pay for membership, so it is worth checking before paying for it yourself.

The basic process was:

1. Create an account on the IET website.
2. Apply for student membership.
3. Enter my course and expected completion details.
4. Wait for the membership to become active.
5. Log in and access Career Manager.
6. Start looking at the professional registration and UK-SPEC sections.

The exact menus may change, but the important step is getting access to Career Manager. It is not only an application form. It can also be used to record CPD, assess yourself against UK-SPEC and identify areas where you need stronger evidence.

Current starting points:

• IET student membership
• Technician professional registration for students
• How to apply for EngTech

Understanding UK-SPEC

The part that initially looks most complicated is UK-SPEC: the UK Standard for Professional Engineering Competence and Commitment.

It is easier to understand once you stop treating it like a large academic document.

UK-SPEC is essentially the assessment framework. It tells you what somebody operating at EngTech, IEng or CEng level should be able to demonstrate. The same five broad areas are used for all three titles, but the expected depth, responsibility and complexity increase at each level.

The five areas are:

For EngTech, these five areas are divided into fifteen competence statements.

A — Knowledge and understanding

A1: Selecting suitable techniques, procedures and methods

This is about showing that you do not blindly follow the first option placed in front of you. You review the task, consider possible approaches and choose a suitable method.

Evidence might include:

• comparing two possible design approaches;
• selecting an appropriate test method;
• identifying a better way to complete a task;
• recognising a problem and deciding how to investigate it;
• interpreting and following a test procedure.

A2: Applying scientific, technical or engineering principles

This is where you show that your decisions are based on engineering knowledge rather than guesswork.

Evidence might include:

• using electrical or mechanical calculations;
• applying technical standards;
• interpreting test results;
• comparing performance data;
• using manuals, datasheets or other technical information correctly.

B — Design, development and solving engineering problems

B1: Identifying problems, finding causes and achieving a solution

This is not limited to inventing a new product. Troubleshooting, improving a process and contributing to a design can all provide evidence.

A good example normally explains:

1. what was wrong;
2. how you investigated it;
3. what you found;
4. what action you took;
5. whether the solution worked.

B2: Organising and using resources effectively

This asks whether you can complete engineering tasks while considering more than the technical answer alone.

That may include:

• cost;
• quality;
• safety;
• security;
• environmental impact;
• time;
• availability of people, equipment or information.

For me, working in a regulated environment made this particularly relevant. A technically possible solution is not automatically the right solution if it creates unnecessary risk, cost, complexity or disruption.

C — Responsibility, management and leadership

C1: Working reliably without close supervision

You do not need to pretend that you never ask for help. In fact, recognising the limits of your knowledge and asking the right person for advice is part of being competent.

This area is about showing that you can:

• understand the task;
• identify the standards or procedures that apply;
• complete work reliably;
• raise uncertainties rather than making unsafe assumptions;
• know when something falls outside your own competence.

C2: Accepting responsibility for your own work or the work of others

Examples could include:

• checking drawings and instructions before starting;
• confirming that equipment and the work area are ready;
• checking work completed by another person;
• accepting ownership of a deliverable;
• finding and correcting an issue before work proceeds.

C3: Accepting, allocating or supervising tasks

You do not need to be a line manager. This could include giving somebody a clearly defined technical task, helping a less experienced colleague, checking their work or explaining what needs to be done.

The important point is showing that you understood the scope, communicated it properly and remained responsible for the result.

D — Communication and interpersonal skills

D1: Communicating technical information effectively

Engineering is full of communication. Useful evidence can come from:

• contributing to meetings;
• writing technical documents;
• producing drawings or reports;
• explaining an issue to a non-specialist;
• presenting findings;
• recording actions and decisions.

D2: Working effectively with colleagues, clients, suppliers or the public

This is about more than saying that you are a team player.

A stronger example explains how you:

• worked towards a shared objective;
• resolved a disagreement;
• gathered information from different people;
• explained a recommendation;
• dealt constructively with a supplier or stakeholder;
• helped the team complete a task.

D3: Personal and social skills, including diversity and inclusion

This asks whether you understand your own strengths and limitations, adapt to different people and situations, and contribute to a respectful working environment.

Possible evidence includes mentoring, STEM outreach, adapting your communication style or supporting colleagues with different needs and backgrounds.

E — Personal and professional commitment

E1: Following relevant codes of conduct

This includes understanding the professional conduct expected by your institution and acting with integrity, confidentiality and respect.

E2: Working safely

Safety should not be a sentence added to the end of an example. Explain what you actually did:

• reviewed a risk assessment;
• followed a permit or safe system of work;
• selected suitable PPE;
• confirmed isolation or test conditions;
• stopped or queried work where something was unclear;
• considered safety during the design itself.

E3: Applying sustainable development

This does not mean every applicant needs to design a renewable energy system.

It can include:

• reducing waste;
• reusing an existing design where appropriate;
• reducing unnecessary material or energy use;
• considering the whole-life impact of a decision;
• balancing environmental and operational requirements.

E4: Recording and carrying out CPD

CPD is not only formal training courses. It can include:

• technical events;
• reading standards;
• manufacturer training;
• learning from a difficult task;
• independent study;
• professional volunteering;
• presenting knowledge to colleagues;
• reflecting on feedback.

The important part is recording what you learned and how it improved your competence.

E5: Acting ethically

This covers issues such as honest reporting, data integrity, confidentiality, conflicts of interest, public safety and recognising when an engineering decision could have wider consequences.

You do not need fifteen separate projects

This was one of the most useful things for me to understand.

The fifteen competence statements are not necessarily fifteen separate essays with fifteen unrelated projects. One good engineering task can demonstrate several areas.

For example, imagine that you modified an existing control arrangement:

• reviewing two possible approaches could support A1;
• applying technical knowledge could support A2;
• resolving a design problem could support B1;
• considering cost, risk and available equipment could support B2;
• taking ownership of the work could support C1 and C2;
• discussing the change with engineers and operators could support D1 and D2;
• preparing a risk assessment and test procedure could support E2;
• considering reuse rather than unnecessary replacement could support E3.

The assessment is looking at the overall evidence that you meet the EngTech standard. Some areas will naturally be stronger than others because everybody's role is different.

UK-SPEC itself gives examples of evidence, but those examples are guidance rather than a fixed checklist. Your evidence needs to be relevant to your own role.

The sort of evidence I used

I cannot publish sensitive project or plant information, but the types of work I drew from included:

The details are less important than the structure of each example. Assessors need to understand what I did, not only what the project team delivered.

How I wrote my examples

The easiest way I found to structure an example was:

1. Context: What was the engineering task or problem?
2. Responsibility: What was I personally expected to do?
3. Action: What did I actually do?
4. Reasoning: Why did I choose that method?
5. Outcome: What happened as a result?
6. Reflection: What did I learn or improve?

A weak example would be:

I helped the team test a system and it passed.

That says almost nothing about competence.

A stronger version would be:

I reviewed the drawings and test procedure before testing, confirmed that the required equipment and safety controls were in place, and completed the allocated tests while recording the results. When one result did not match the expected operation, I checked the configuration and traced the issue to an incorrect setting. I corrected the setting, repeated the affected tests and documented the change before the system was accepted.

The second version gives the assessor something to assess. It shows preparation, individual action, problem-solving, safety, recording and an outcome.

A few things I tried to keep in mind were:

• use I when describing my own contribution;
• explain decisions rather than listing duties;
• include an outcome;
• mention relevant standards or procedures where they genuinely influenced the work;
• show when I asked for advice;
• avoid unnecessary jargon;
• remove confidential names, drawing numbers and plant details;
• do not exaggerate responsibility.

Using Career Manager

Career Manager gave me somewhere to organise the application and compare my experience with the UK-SPEC competence statements.

My practical advice is to open it early, even if you are not ready to submit.

Start by:

1. Looking through the EngTech competence statements.
2. Listing the projects and tasks you completed during your placement.
3. Writing one or two lines about your contribution to each.
4. Mapping each task against the areas it could demonstrate.
5. Identifying any obvious gaps.
6. Recording your CPD as you go.
7. Asking a supervisor or mentor to check whether your examples are accurate.

Do not wait until the end of the placement and try to remember everything. Small tasks can provide good evidence, but they are easy to forget once you move onto another project.

The current IET application asks for details of three recently completed technical tasks or projects. It also asks how you planned and recorded the work, how you maintained a safe environment, how you keep your knowledge current and who can support the application.

Getting help from a Professional Registration Advisor

The IET provides access to Professional Registration Advisors, usually called PRAs.

A PRA is useful because they understand the registration process and can help you judge whether your evidence is pitched at the right level. They are not there to invent examples or write the application for you.

Useful questions to ask include:

• Am I applying for the appropriate registration title?
• Does this example demonstrate my own contribution clearly?
• Have I shown enough responsibility?
• Am I describing duties, or am I demonstrating competence?
• Are any of my examples too vague?
• Which areas of UK-SPEC need stronger evidence?
• Have I included enough about safety, CPD and professional commitment?

Career Manager also allows applicants to self-assess against UK-SPEC and request development support.

Choosing a supporter

The application requires at least one supporter who can confirm your experience and suitability.

I would recommend asking somebody who:

• knows your work;
• understands the responsibility you were given;
• can confirm that your examples are accurate;
• is willing to respond when contacted;
• ideally understands professional registration.

Ask them early rather than typing their details into the application without warning.

My supporter was the Professional Registration Advisor for the placement programme. They acted as an independent mentor supporting graduates, apprentices and industrial-placement students. I let them know which projects I intended to describe, which made it easier for them to review my evidence and confirm that it represented my contribution honestly.

The IET did not contact my supporter during the assessment, although applicants should still choose somebody who is prepared to respond if asked.

What did it cost?

My IET student membership cost around £20 at the time.

That was the price I paid in 2024, not a current quotation. The IET currently advertises student membership at £36 for the duration of the course, but membership prices and eligibility can change.

There was also a professional registration application fee and, following a successful application, an Engineering Council registration or entrance fee.

Fees change, so I have deliberately not presented the 2024 figures as permanent prices. Check the current pages before applying:

• IET membership fees
• IET professional registration fees

I no longer have a reliable record of the exact application and entrance fees I paid, so I will not guess at the figures. It is also worth checking whether your university or employer will pay the fees. Some already fund student membership or support professional registration applications.

What happened after I submitted?

I started working on the application in January 2024 and developed the evidence in Career Manager alongside my placement. I submitted it in September 2024; I no longer have the exact day recorded.

I did not have an interview. During the assessment, I was asked to add a small amount of supporting information in Career Manager. I supplied the additional detail, and the rest of the process continued without an interview or a further formal stage.

I received an email confirming that I had been successful in October 2024. The overall journey from starting the application to the decision took roughly nine months, although most of that time included developing and recording my evidence rather than waiting for the assessment alone.

I was able to use the EngTech post-nominal after receiving the confirmation email, and I subsequently received a professional registration certificate.

Was it worth doing?

For me, yes.

EngTech did not suddenly make me an expert, and it did not mean I had finished developing. What it did was make me stop and assess the experience I had already gained.

It helped me recognise that professional engineering is not only about calculations. It also includes:

• selecting an appropriate method;
• working within procedures and standards;
• keeping accurate records;
• understanding the consequences of decisions;
• communicating with other people;
• accepting responsibility;
• working safely;
• knowing when to ask for help;
• continuing to learn.

Achieving professional registration while still at university also gave me confidence that my placement had developed real engineering competence, rather than simply giving me a year to add to my CV.

What I would tell another placement student

Do not automatically assume that you are too early in your career.

UK-SPEC does not prescribe a minimum age or a fixed number of years that everybody must complete. What matters is whether you can demonstrate the required competence and commitment at the appropriate level.

My advice would be:

1. Join a relevant professional engineering institution.
2. Open Career Manager early.
3. Read the EngTech section of UK-SPEC.
4. Keep a record of your projects, responsibilities and CPD.
5. Write about what you did.
6. Use two or three strong technical tasks rather than lots of weak examples.
7. Explain your reasoning and the outcome.
8. Include safety and professional responsibility throughout.
9. Ask a supervisor, mentor or PRA for honest feedback.
10. Keep confidential information out of the application unless it is being submitted through an approved secure process and is genuinely necessary.

I nearly dismissed EngTech because I was still a student. In reality, my year in industry was the reason I had the evidence to apply.

If you are completing a placement and being trusted with real engineering work, it is worth opening UK-SPEC and checking how your experience compares. You may already be closer than you think.

Useful links

• Engineering Council: UK-SPEC
• IET: Engineering Technician registration
• IET: How to apply for EngTech
• IET: Technician professional registration for students
• IET: Student membership

This article is an account of my own application and is not official guidance from the IET or Engineering Council. Always check the current requirements before applying.