
This article aims to answer the question: what does an engineer actually do? If you come from a non-engineering family, like me, this question is surprisingly difficult to answer. Most guides tend to give general answers like "engineers build things", or "engineering is an art and a science", "engineering is the application of science to make practical things", etc. etc. While those things are certainly true, they don't answer the question of what an engineer actually does on a day to day basis or what roles they play in companies. This article will hopefully answer some of these questions.
Design Engineer
We'll start with the design engineer. This is the stereotypical picture most people have of an engineer: someone in a hardhat scrambling around with blueprints and a slide rule. The design engineer is the person responsible for designing the product the company sells. In the end, this means producing the schematics or other deliverables (i.e. software, firmware, etc.) that will then be used by manufacturing to turn the plans into a real-life product.
Design engineering also involves making (and fixing) prototypes of the product before it gets into manufacturing. This usually involves some lab work, either working on scale models, prototype circuit boards, etc. Mechanical engineers nowadays tend to make a lot of prototype parts using 3-D printers, which is pretty cool. Electrical engineers will make prototype circuit boards. Civil engineers may make scale models and test the structural integrity in a lab.
I would estimate that probably less than half of working engineers are design engineers. There are a whole lot more types of jobs engineers do, and every design engineer needs quite a bit of support. The pros of design engineering is that it is very technically challenging and you will likely receive a lot of training throughout your career. The cons is that it involves a lot of office work. While it is still social and you have to interface with colleagues, you will spend a lot of time in your cube working on your designs.
Project Engineer
The project engineer is responsible for making sure a particular project at the company gets finished to spec, on time, and within the budget. They are responsible for coordinating the efforts of the various engineers involved in a project, making sure all standards are met, dealing with outside vendors, scheduling, budgeting, etc. The upside of project engineering is that it can feel like owning your own small business. You get a budget and in the end have to see a project through. Of course, the catch is that the product engineer is not the manager, they have authority over a project, not people. In most companies it tends to work out, but it is an important distinction to keep in mind. The upsides of project engineering is that its very social and multi-faceted, and you get to see a project from a high-level. The project engineer, however, will not be involved in the low-level design of each component of the project.
Applications Engineer
The applications engineer is not quite designer and not quite salesman, but somewhere in the middle. Applications engineers are the technical 'how-to' people at a company. They will know every nuance of how to take full advantage of a company's product and will interface with customers, helping to solve their customers' problems. A good example is MathWorks, the company that makes Matlab. If you want to use Matlab for a particular application, you can talk to an application engineer at the Mathworks and they will recommend how to use the product to solve the problem you're trying to tackle.
Application engineering tends to involve a fair bit of travel, as they are often flown (or driven) on-site to meet face to face with design engineers at a company. When you're not travelling, you're probably answering emails or talking on the phone. Applications engineers also tend to receive a lot of training on the company's products, so they are the domain experts and can advise customers.
Field Engineer
The field engineer is fairly self-explanatory. They will go out into the field and, well, get things done. This usually means supervising and troubleshooting an installation of a new product (i.e. a new manufacturing machine your company designed and is putting into a factory) or advising and coordinating efforts to fix or replace a product that is already active. Field engineers will usually be supported by design engineers at the home office. The job tends to involve a lot of travel, but can pay quite well. It can also be stressful, as there is often a lot of money on the line and schedules are tight. You're also directly in the cross-hairs if anything goes wrong.
Test Engineer
The role of the test engineer is to take the beautiful baby painstakingly crafted by the design engineers and to do everything in their power to break it. The guys in white coats watching as a car is driven into a brick wall: test engineers. Test engineers will design and execute the testing regimens a new product goes through. They'll make sure it meets all required standards (and there are usually a lot). If anything does break, they give that feedback to the design engineer, who is then tasked with fixing the problem.
Sales Engineer
We now come to the black sheep of the engineering family: the sales engineer. The sales engineer is not quite an engineer anymore, as they are not really involved in making things (unlike the other job types I listed above). However, technical sales are very important, and these jobs are usually staffed by engineers. Sales engineers will usually be involved in selling the company's products to other engineers, or technical people. As such, they need a good science and engineering background, understand the customer's needs, and understand the product being sold. The advantages of a sales engineering position is that it again involves a lot of social interaction, can involve a fair bit of travel, and tends to pay quite well (commission is often involved).
