Beyond the degree title · 6 min read

I have an engineering degree, but I do not want to be an engineer. What next?

Separate the discipline from the work you dislike. Compare technical, customer-facing and operational routes with practical tasks and realistic skill gaps.

Written by Nivaan, founder of OffLadder · Last reviewed 10 October 2026 · Sources listed at the foot of this page

Perhaps you enjoyed the project and hated the placement. Perhaps you liked understanding the system but did not want to spend another afternoon modelling it. Or perhaps the degree was a choice made years ago by a version of you with less information.

You are allowed to use the new information. It just helps to be precise about what it says.

Diagnose the mismatch at task level

Describe three recent pieces of work: one you enjoyed, one you tolerated and one you would rather not repeat. Include the conditions. “I hated engineering” is less informative than “I liked finding why the prototype failed, but the site schedule and constant travel were not workable.”

A change of employer, sector or working arrangement may solve a conditions problem. It will not necessarily solve a dislike of the core task. Conversely, leaving the profession entirely may discard useful capability when the real problem was one narrow setting.

Ask a practitioner in a different kind of role what they actually do. Do not compare your most frustrating experience with an idealised version of another career.

Keep your discipline visible without making it a cage

A mechanical graduate may have useful preparation in design, materials, production or physical systems. An electrical or electronic graduate may bring experience with circuits, control, computation or connected systems. A chemical graduate may have worked with processes, scale, flows and production constraints. Individual courses and projects differ, so name your actual experience rather than claiming every skill associated with the degree.

Prospects’ separate guides identify adjacent possibilities including technical sales, technical communication, project work and business-related roles, with different options by discipline. They are starting points for investigation, not a guarantee that switching requires no additional training.

The useful question is which part of that preparation you want to keep using.

Route one: stay close to technical work, but change the output

Suppose you enjoy understanding a system but not spending most of your time designing it. Investigate technical documentation, training, implementation or support roles where the main output is another person’s ability to understand or use something.

For a safe first task, choose an ordinary product whose user manual is publicly available. Do not open equipment, bypass safety instructions or experiment with electrical or hazardous systems. Write a one-page guide to finding and interpreting three pieces of information in the manual, with exact page references and unresolved questions.

Then ask a consenting adult to locate the information using your guide. You are testing explanation, not certifying the product or providing maintenance instructions beyond your competence. Notice whether translating the technical detail feels satisfying or like an unwelcome interruption to the “real” work.

The gaps to investigate may include documentation tools, accessibility, user research or the employer’s specific technology. Technical understanding is valuable only if the recipient can use what you produce.

Route two: move closer to the customer’s problem

Technical sales or solutions work may appeal if you enjoy asking questions, explaining trade- offs and connecting capabilities to a practical need. Check how much the job involves commercial targets, travel, prospecting and demonstrations. It is not simply engineering with more conversation.

Try this fictional brief. A community group needs equipment to display presentations in two rooms. Room A seats twenty people and has daylight. Room B seats six and can be darkened. The group has a fixed budget but has not specified an amount. Volunteers with limited technical knowledge will set up the equipment. Storage and support arrangements are unknown.

Write the questions you would ask before recommending anything. Prioritise budget, room conditions, setup, accessibility, compatibility and support rather than producing a shopping list. Then explain two possible solution approaches and the information that would determine the choice, without inventing specifications or prices.

If the questioning interests you, investigate customer-facing technical roles. If the idea of commercial targets is the thing you are trying to escape, inspect the offer carefully rather than relying on the word “solutions.”

Route three: work on the operation around the system

You may enjoy organising work, resolving constraints and improving handovers more than calculating the technical design. Investigate project, operations, procurement or quality- related routes, checking their requirements and the boundaries of your competence.

Here is a fictional non-safety-critical assembly exercise. A small workshop can complete ten units a day at preparation, six at assembly and eight at packing. Assume one unit uses each stage once, there is no opening stock and the simplified capacities apply over the same working day. What questions would you ask before promising eight finished units a day?

Assembly is the apparent bottleneck at six units under those assumptions. Increasing preparation alone does not establish higher finished output. You would need information about work-in-progress, variation, staffing, defects and the feasibility of changing the limiting stage. A simple average of the three capacities would not answer the question.

Write a handover note explaining the constraint and what to investigate next. This is a reasoning exercise, not a production recommendation for a real plant. O*NET’s management- analyst profile offers a US example of work concerned with studying and improving organisational processes.

Route four: leave the technical field deliberately

You may test all three and still prefer work in a very different area. That is a possible result, not a failure to appreciate your degree.

Choose the new work on its own terms. A teaching, design, policy or people-support role may require substantial new preparation. Do not assume analytical ability substitutes for subject knowledge, supervised practice or professional credentials.

Equally, do not erase what you have already learned. You can be a beginner in one domain while bringing experience of structured problem-solving, projects or explaining complex ideas. Demonstrate those capabilities with honest examples rather than announcing that engineers are naturally good at everything.

Compare evidence, not imagined prestige

For each route, record the task you tried, the part that held your attention, the skill gap, the working conditions and one real entry route to verify. Eliminate options that violate a hard constraint, such as frequent travel you cannot manage. Do not give them extra points for sounding impressive.

Speak to people at the level you might realistically enter. A director’s account of strategic work will not tell you what the first year contains. Ask what new entrants struggle with and what evidence would make someone with your background credible.

Will moving outside engineering mean a pay cut? It depends on the move, employer, location and experience you can carry forward. Compare real roles and total compensation rather than assuming either a guaranteed reset or a guaranteed premium.

Should I finish the degree? That is a separate decision involving remaining time, cost, wellbeing and alternatives. Get course-specific advice and test the destination before making completion or withdrawal a symbolic statement about your whole future.

Keep the useful parts and test the rest

OffLadder helps you explore directions without pretending you are starting from nothing. Use Explore to compare different uses of your experience, ask Laddie to help design a safe task, and keep the results in You. Find a next move beyond the engineering title. The aim is not to escape everything you know. It is to find out which parts you want to carry into a different kind of day.