Engineers design the physical world: bridges, machines, circuits and power systems, balancing what is possible, safe and affordable. This course shows what civil, mechanical and electrical engineers actually do, the math and physics each discipline leans on, and the engineering design process. It maps the routes in (ABET-accredited degrees, the FE exam, supervised experience and the PE licence, plus co-ops, technician roles and community college transfer) and introduces the everyday tools of the profession: calculations with units, codes and standards, and the ethics that put public safety first. It builds on STEM Foundations. It teaches the knowledge; an accredited degree, supervised experience and licensing exams are still required for professional practice.

How civil, mechanical and electrical engineers think, what to study, and the degree, FE and PE route into the field.

Foundations for Engineering & Energy Careers

## Why it matters

"Engineer" covers hundreds of jobs. Before you spend four years on a degree, it helps to know what the work looks like on an ordinary Tuesday, and how the three biggest disciplines differ. This lesson compares civil, mechanical and electrical engineering so you can tell which one fits the problems you like solving.

## The core idea: design under constraints

Scientists ask how the world works. Engineers use that knowledge to **make something that works**, within limits. A bridge must carry its load *and* fit the budget *and* be buildable by the contractor *and* last 75 years *and* meet the building code. Those goals pull against each other, so engineering is a series of deliberate **trade-offs**: stronger usually means heavier and more expensive; cheaper usually means less margin.

The daily loop is similar in every discipline:

1. Understand the problem and the requirements.
2. Sketch options.
3. Model them with math and software.
4. Pick one and justify the choice.
5. Document it so someone else can build, check and maintain it.
6. Test, inspect or monitor it, and improve.

A surprising amount of the job is steps 4 and 5: meetings, calculations packages, drawings, reports and emails. Engineers who write clearly get their designs built.

## Three disciplines, side by side

**Civil engineers** design the built environment: roads, bridges, buildings' structural frames, water and wastewater systems, dams, and the ground everything sits on. Specialties include structural, geotechnical, transportation, water resources and environmental. A typical week mixes design calculations, drawings in CAD, coordination with architects and contractors, and site visits. Many civil projects are public works, which is why licensure (the PE) matters so much in this field.

**Mechanical engineers** design things that move or manage energy: engines, pumps, HVAC systems, robots, medical devices, consumer products, manufacturing equipment. They use mechanics (forces and stresses), thermodynamics and heat transfer, fluids, and materials. A week might include 3D CAD modelling, a stress or thermal analysis, a prototype test, and a conversation with the factory about whether a part can actually be made.

**Electrical engineers** design systems that generate, move and use electricity and signals: power grids, substations, motors and drives, building electrical systems, circuit boards, sensors, control systems and communications. Power engineers work on utilities and large facilities; electronics engineers work on boards and chips; controls engineers make machines behave. A week could include circuit simulation, reading datasheets, writing test procedures, and reviewing a one-line diagram for a new building.

The "energy" in this course's title cuts across all three: civil engineers site wind farms and dams, mechanical engineers design turbines and heat pumps, and electrical engineers connect it all to the grid.

## A worked example: one project, three engineers

Imagine a new community hospital.

- The **civil/structural** engineer sizes the foundations and the steel frame, checks wind and earthquake loads, and designs the parking lot drainage.
- The **mechanical** engineer designs heating, cooling and ventilation, including the special air pressure needed in operating rooms and isolation rooms.
- The **electrical** engineer designs power distribution, lighting and the emergency generators that must start within seconds if the grid fails.

None of them can work alone. The mechanical engineer's air handlers are heavy, so the structural engineer needs their weight. The air handlers need power, so the electrical engineer needs their load. Engineering is a team sport, and the drawings are how the team talks.

## Common mistakes when choosing a discipline

- **Choosing by a single class you enjoyed.** Liking physics in high school does not tell you whether you want to design pipelines or circuit boards. Look at job postings and day-in-the-life interviews.
- **Assuming engineers build things with their own hands.** Most design engineers spend their time at a computer and in meetings. Technicians and tradespeople do most of the hands-on building and installing (and those are excellent careers too; see Module 2).
- **Ignoring the industry.** A mechanical engineer in aerospace and one in building services have very different days. Industry matters as much as discipline.

## Quick recap

- Engineering is design under constraints: safety, cost, time, materials and codes.
- Civil engineers design infrastructure, mechanical engineers design machines and energy systems, electrical engineers design power and signal systems.
- Real projects need all three working together, communicating through drawings and calculations.
- Pick a discipline by looking at the problems and the industry, not just one favourite class.


Compare the daily work of civil, mechanical and electrical engineers: design under real constraints.

What engineers actually do

What is Engineering?: Crash Course Engineering #1

Mechanical Engineering: Crash Course Engineering #3

## Why it matters

Engineering degrees are front-loaded with math and physics, and many students leave in the first two years because of it. Knowing *what* you will need, and *why*, makes the climb easier. The honest advice from working engineers is simple: do not skip the math. Weakness in algebra becomes a ceiling in every later course.

## The shared core

Every ABET-accredited engineering program in the US requires a common base. The exact list varies, but expect:

- **Algebra and trigonometry**: rearranging formulas, working with angles and right triangles. This is the daily tool.
- **Calculus I and II**: rates of change (derivatives) and accumulation (integrals). Speed is the derivative of position; the total water that flowed into a tank is the integral of the flow rate.
- **Calculus III (multivariable)** and **differential equations**: quantities that change in space and time, such as heat spreading through a wall or a circuit charging.
- **Linear algebra**: systems of many equations at once, which is how structural and circuit software solve large problems.
- **Probability and statistics**: loads, material strengths and test results all vary; statistics tells you how much margin to leave.
- **Physics I and II** (calculus-based): mechanics (forces, motion, energy) and electricity and magnetism.
- **Chemistry**: at least one course, because materials corrode, cure and burn.

## What each discipline leans on

| Discipline | Heaviest math and physics | Example use |
|---|---|---|
| Civil | Statics, mechanics of materials, fluids, soil mechanics, statistics | Sizing a beam; designing a storm drain |
| Mechanical | Dynamics, thermodynamics, heat transfer, fluids, materials | Cooling an engine; picking a gear ratio |
| Electrical | Circuits, electromagnetism, differential equations, complex numbers, signals | Designing a filter; sizing a transformer |

Notice that **statics** (forces on things that do not move) appears for civil and mechanical, and **differential equations** appear everywhere, because so many physical systems are described by how fast something changes.

## A worked example: units first

Most engineering math is not exotic. It is algebra plus careful units. Suppose a small pump lifts water 10 m and you want to know the power needed to lift 2 kg of water every second.

Power equals the rate of doing work, and the work to lift a mass is weight times height:

```text
P = m_dot x g x h
  = 2 kg/s x 9.81 m/s^2 x 10 m
  = 196.2 kg*m^2/s^3
  = 196.2 W   (because 1 W = 1 kg*m^2/s^3)
```

Two habits are doing the work here. First, every number carries its unit, so the units multiply out and prove the formula is set up correctly. Second, you can sanity-check: 200 W is roughly a few bright old-style light bulbs, which seems plausible for a small pump. A real pump wastes energy, so if its efficiency is 60%, the motor needs about 196.2 / 0.6 = 327 W.

## A worked example: where calculus appears

A tank fills at a flow rate that rises steadily from 0 to 4 L/min over 10 minutes. How much water went in? The flow is not constant, so you cannot just multiply. The total is the area under the flow-versus-time graph: a triangle, so 1/2 x 10 min x 4 L/min = 20 L. That "area under the curve" *is* an integral. Calculus generalises this to curves that are not straight lines.

## Common mistakes

- **Dropping units mid-calculation.** Most wrong answers in engineering classes (and some expensive real failures) come from unit errors, not hard math.
- **Memorising formulas instead of understanding them.** Exams give you a reference handbook; what they test is knowing which relationship applies and why.
- **Skipping the estimate.** Always ask "is this answer reasonable?" before you move on.
- **Waiting to fix weak algebra.** If you struggle to rearrange `V = I x R` for `R`, fix that now with practice; it will not get easier when the formulas get longer.

## How to prepare now

Work through algebra, trigonometry and pre-calculus until they feel routine (the Math for Tech & STEM course on this platform covers them). Take the hardest math and physics your school offers. Practise with problem sets that show worked solutions, so you get feedback on every step. You do not need to be a genius; you need steady practice.

## Quick recap

- The shared core is calculus, differential equations, linear algebra, statistics, physics and some chemistry.
- Civil leans on statics and fluids, mechanical on dynamics and thermal science, electrical on circuits and electromagnetism.
- Most daily engineering math is algebra with careful units and a sanity check.
- Integrals are "area under the curve": totals of things that change.


List the math and physics each engineering discipline uses, and why algebra and units come first.

The math and physics that matter

Understanding Calculus (for engineers)

Write the problem in one sentence, then list 2-3 measurable requirements and 2-3 constraints (materials, time, size).

Decide exactly how you will test success (for example: count coins added one at a time until the bridge sags more than 1 cm).

Sketch at least three different design options on paper before building anything.

Make a weighted decision matrix with at least three criteria and use it to pick one option. Write one sentence on why it won.

Build the chosen prototype within your time limit.

Test it at least three times and record each result in a small table.

Change one feature only, based on what failed, then retest three times and record the results.

Write a short summary: requirements, chosen design, test results before and after the change, and what you would try next.

## Why it matters

Engineers rarely get a design right the first time, and they do not expect to. What makes engineering reliable is the **process**: a repeatable way to go from a vague need to a tested solution. You will see versions of it in every engineering class, every design competition and every job interview question that starts "Tell me about a project...".

## The core idea: a loop, not a line

Different organisations draw it with five, seven or ten boxes, but the steps are the same:

1. **Define** the problem. Who needs what, and why? Write **requirements** (what it must do) and **constraints** (limits such as budget, size, materials, time, safety and codes). Decide how you will measure success.
2. **Research.** What already exists? What do the relevant standards say? What failed before?
3. **Ideate.** Generate several options without judging them yet. Quantity first; ten rough sketches beat one polished idea.
4. **Select.** Compare options against the requirements, often with a **decision matrix** (below).
5. **Build** a prototype or a model. Early prototypes can be cardboard, a spreadsheet or a simulation.
6. **Test** against the success measures you defined in step 1. Record the results honestly, including failures.
7. **Iterate.** Use what you learned to improve the design, then test again. Communicate the final design with drawings and a short report.

The arrow from "test" back to "define" or "ideate" is the most important one. A failed test is information, not a disaster.

## A worked example: a phone stand

**Define.** Need: hold a phone upright for video calls on a desk. Requirements: holds a phone at about 60-70 degrees from horizontal; does not tip when the screen is tapped; charging cable still fits. Constraints: one sheet of cardboard, tape, scissors; 30 minutes; no glue.

**Ideate.** Three options: (A) a folded triangle prism, (B) two interlocking slotted pieces, (C) a rolled tube with a slot cut in it.

**Select** with a weighted decision matrix. Score each option 1-5 per criterion, multiply by the weight, and add:

| Criterion | Weight | A: triangle | B: slotted | C: tube |
|---|---|---|---|---|
| Stability | 3 | 4 (12) | 5 (15) | 2 (6) |
| Cable access | 2 | 2 (4) | 4 (8) | 3 (6) |
| Ease of building | 1 | 5 (5) | 3 (3) | 4 (4) |
| **Total** | | **21** | **26** | **16** |

Option B wins, but the matrix also tells you *why*: stability carried the most weight.

**Build and test.** Tap the screen ten times with one finger. Result: the stand tipped backwards twice. **Iterate:** extend the rear leg by 3 cm and retest: zero tips in ten taps. That one cycle of test and change is the engineering method in miniature.

## Requirements versus constraints

Students often mix these up. A **requirement** describes what the design must achieve ("holds a phone at 60-70 degrees"). A **constraint** limits how you may achieve it ("one sheet of cardboard"). Good requirements are measurable. "Sturdy" is not testable; "does not tip in ten taps" is.

## Common mistakes

- **Jumping to the first idea.** The first idea is rarely the best; generate options before choosing.
- **Vague success criteria.** If you cannot test it, you cannot know whether you met it.
- **Changing several things at once.** If you change the leg length and the angle together and it improves, you do not know which change helped.
- **Hiding failed tests.** In industry, test records are part of the design evidence. A test that failed and led to a fix is a strength in a portfolio.
- **Skipping documentation.** A design only helps if someone else can build it from your sketches and notes.

## Quick recap

- The design process is a loop: define, research, ideate, select, build, test, iterate.
- Write measurable requirements and clear constraints before sketching.
- Use a weighted decision matrix to choose between options and explain the choice.
- Change one thing at a time, record every test, and treat failure as data.

## Try it

Open the **Do** tab and run one full design loop on a small, safe problem using paper, cardboard or household items.


Apply define, ideate, build and test to a small problem, and see why iteration beats a perfect first try.

The engineering design process

STEMonstrations: Engineering Design Process

The Engineering Design Process: A Taco Party

What engineers do, the math and physics behind it, and the design process.

The Engineering Mindset

## Why it matters

Engineering is one of the most regulated STEM fields, because a mistake in a bridge, a pressure vessel or a building's electrical system can kill people. In the United States, the right to offer engineering services to the public and to seal (sign and stamp) engineering drawings is controlled by **state licensing boards**. If you know the licensing route *before* you choose a school, you avoid an expensive detour later.

This lesson describes the general US route. Details (experience years, exam rules, which degrees count) vary by state and change over time, so always confirm with your state board and the official bodies linked below.

## Step 1: an ABET-accredited degree

**ABET** accredits college programs in engineering, engineering technology, computing and applied science. Accreditation means the program has been reviewed against published criteria for curriculum, faculty, facilities and student outcomes. Two commissions matter here:

- **EAC (Engineering Accreditation Commission)** accredits *engineering* programs (for example, a BS in Civil Engineering).
- **ETAC (Engineering Technology Accreditation Commission)** accredits *engineering technology* programs, which are more applied.

For the most direct path to a PE licence, most states expect an EAC-accredited bachelor's degree. Some states accept engineering technology degrees or non-accredited degrees with extra years of experience, and some do not. Check before you enrol: search the program on ABET's site. Official site: [abet.org](https://www.abet.org). Checked on 2026-10-23.

## Step 2: the FE exam

The **Fundamentals of Engineering (FE)** exam is written and administered by **NCEES** (the National Council of Examiners for Engineering and Surveying). It tests the core of an undergraduate degree in your discipline (there are versions for civil, mechanical, electrical and computer, and others). It is computer-based and taken at approved test centres, and you may use the NCEES reference handbook during the exam. Many students take it in their final year or soon after graduating, while the material is fresh.

Passing the FE (plus meeting your state's requirements) typically earns the designation **Engineer in Training (EIT)** or **Engineer Intern (EI)**. It is a signal to employers that you are on the licensure track. Exam specifications, fees and registration rules change, so read them on [ncees.org](https://ncees.org) rather than relying on any copy. Checked on 2026-10-23.

## Step 3: qualifying experience

Most states require around **four years of progressive engineering experience**, typically under the supervision of a licensed PE, before you can be licensed. "Progressive" means your responsibility grows over time. Keep a running record of your projects, your role and who supervised you; you will need references from licensed engineers on your application.

## Step 4: the PE exam and licence

The **Principles and Practice of Engineering (PE)** exam, also from NCEES, tests competence in a specific discipline (for example, PE Civil: Structural, or PE Electrical and Computer: Power). After passing and meeting experience and reference requirements, your **state board** issues the licence. Only then can you call yourself a "Professional Engineer" and seal drawings in that state. Licences must be renewed, usually with continuing education. Some states have additional licences for certain work, such as the Structural Engineer (SE) for significant structures. Find your board through NCEES's list of member licensing boards. Checked on 2026-10-23.

## Who actually needs a PE?

Not every engineer. A rough guide:

- **Usually needed:** civil engineers in consulting or public works, engineers who sign building design drawings (structural, mechanical and electrical building systems), power utility design, and anyone who wants to lead a consulting firm.
- **Often optional:** engineers in manufacturing, aerospace, electronics and many product companies, where an "industrial exemption" in many state laws covers work for an employer's own products.

Even when it is optional, the FE is cheap insurance: it keeps the door open.

## A worked example: two paths

- **Maria** wants to design bridges. She chooses an EAC-accredited civil program, takes the FE in her final semester, works four years at a consulting firm under a PE, passes PE Civil: Structural, and is licensed. She can now seal bridge drawings.
- **Dev** wants to design circuit boards for consumer products. He takes an EAC-accredited electrical program and joins an electronics company. He takes the FE anyway, in case he later moves into power or building design. His employer does not require a PE.

## Common mistakes

- **Not checking accreditation before enrolling.** A non-accredited degree can add years to the licence route, or block it, depending on the state.
- **Waiting years to take the FE.** The material fades quickly after graduation.
- **Not logging experience as you go.** Reconstructing four years of projects from memory is painful.
- **Assuming one state's rules apply everywhere.** Licences are issued by states; working in another state usually means applying there too (comity).

## Quick recap

- ABET (EAC) accredited degree, then the NCEES FE exam (EIT/EI), then about four years of supervised experience, then the NCEES PE exam, then a state licence.
- State boards issue licences; rules vary, so check yours.
- A PE is essential for public-facing design sign-off and often optional in product industries.


Map the route from an ABET-accredited degree through the FE exam and supervised experience to the PE licence.

Degrees, accreditation, and licensure (FE/PE)

How To Become An Engineer: Crash Course Engineering #45

The path to becoming a P.E.

Pick a small design problem from your life, a class or a club (for example: a shelf bracket, a drainage fix for a garden bed, a battery-powered LED night light).

Write the problem statement, at least two measurable requirements and two constraints.

Write down one calculation or estimate the project will need, with units (for example: load on the bracket, volume of water, battery life in hours).

Describe how you will test it and what result counts as success.

Choose a free CAD or schematic tool and note which drawing or model you will produce for the portfolio.

List 10 organisations in your target discipline and region (include at least two public agencies or smaller firms) and note where each posts internships.

Find the student chapter of one professional society at your school or nearby (ASCE, ASME, IEEE or similar) and note its next meeting or event.

Write a two-line resume bullet for the project as if it were finished, with a number in it.

## Why it matters

Grades show that you passed the classes. Employers hiring engineering interns and graduates want to know something else: **can you design?** Can you take a fuzzy problem, make sensible assumptions, calculate, draw, build or simulate, test, and explain your choices? The strongest way to show that is evidence: documented projects, CAD work and supervised experience.

## Three kinds of evidence

**1. Design projects.** A good portfolio project follows the design process from Module 1 and shows your reasoning, not just a photo of the result. Each one should answer:

- What was the problem and who was it for?
- What were the requirements and constraints?
- What options did you consider, and why did you pick this one?
- What calculations or simulations did you do?
- How did you test it, and what happened?
- What would you change next time?

Projects can come from classes, design competitions (concrete canoe, steel bridge, Formula SAE, robotics, solar car), clubs, or your own ideas. Small and well-documented beats large and vague.

**2. CAD and technical drawings.** Engineering is communicated in drawings. Free or student versions of CAD tools (for example Onshape's free plan, FreeCAD, or student licences of commercial tools through your school) let you model parts and produce drawings with dimensions and tolerances. Electrical students can show schematics and simulations from free circuit tools. Include one or two clean drawings in your portfolio; a reviewer should be able to read them without you explaining.

**3. Internships and co-ops.** Supervised real-world work is the strongest signal of all, and for licensure the experience can matter later too. An **internship** is usually a summer role. A **co-op** alternates semesters of full-time paid work with semesters of study, often adding a year to the degree but giving you a year or more of experience by graduation (more on this in the next lesson).

## A worked example: one project write-up

**Project:** Rainwater collection for a community garden shed.

- **Problem:** the garden has no water tap near the beds.
- **Requirements:** collect enough water for one week of hand watering (about 200 L); overflow safely away from the shed's foundation.
- **Constraints:** budget of $150; no plumbing permit needed; must be removable.
- **Calculation:** roof area 2.4 m x 3.0 m = 7.2 m^2. Each 1 mm of rain on 1 m^2 yields 1 L, so a 10 mm rainfall gives about 7.2 x 10 = 72 L (less some losses). About three such storms (3 × 72 ≈ 216 L before losses) fill the 200 L target; a two-storm week gives roughly 140 L.
- **Test:** measured the level after the first three rain events and compared with the rain gauge.
- **Result and next step:** collected about 85% of the predicted volume; the gutter leaked at one joint, which was resealed.

That page tells an interviewer more about you than a transcript line.

## Planning an internship search

- **Start early.** Many large engineering employers recruit for summer internships in the autumn before.
- **Target by industry and discipline.** List 15-20 organisations: consulting firms, utilities, manufacturers, contractors, state transportation departments and city public works.
- **Use your school's resources.** Career fairs, co-op offices, and student chapters of professional societies (ASCE, ASME, IEEE, SWE, NSBE, SHPE) connect students to employers.
- **Tailor your resume.** Lead with projects and skills that match the posting. Quantify where you can ("reduced part mass by 18%").
- **Follow up.** A short thank-you note after a conversation or interview is remembered.

## Common mistakes

- **Portfolios of photos only.** Show reasoning, calculations and tests, not just the finished object.
- **Team projects with no clear role.** Say exactly which part you did.
- **Applying only to famous companies.** Smaller firms and public agencies often give interns more real responsibility.
- **Waiting until senior year.** Experience compounds; one early internship makes the next easier to get.

## Quick recap

- Evidence beats grades: documented projects, readable drawings and supervised work.
- Write projects up using the design process: problem, requirements, options, calculations, tests, results.
- Search for internships and co-ops early, targeted by industry, using your school and professional societies.

## Try it

Open the **Do** tab to plan one portfolio project and a short, targeted internship list.


Plan a design project you can show an employer, and a targeted internship or co-op search.

Building design evidence: projects, CAD, and internships

How to Start Building Your Student Engineering Portfolio

## Why it matters

The "four years at a university, then a job" route is not the only way into engineering work, and for many people it is not the best one. Cost, family responsibilities and the wish to earn while learning all push people toward other routes. Some of those routes lead to a PE licence; others lead to excellent technician careers that do not need one. Knowing the difference lets you choose on purpose.

## Route 1: community college and 2+2 transfer

Many students complete their first two years (calculus, physics, chemistry, English, and some introductory engineering courses) at a community college, then transfer to a university's engineering program for the final two years. This is called **2+2 transfer**.

**Why it works:** tuition is usually much lower, class sizes are smaller, and you can live at home. The degree you finish with is the university's accredited engineering degree, so the licensure route is the same.

**What to check before you start:**

- An **articulation agreement** between the college and the university, which lists exactly which courses transfer and count toward the engineering degree (not just as general electives).
- The math sequence. Engineering programs expect you to be well into calculus by transfer; falling a semester behind in math can delay graduation by a year.
- Transfer admission requirements for the engineering program specifically, which may be stricter than the university's general requirements (minimum grades in key courses).

Meet a transfer adviser in your **first** semester, not your last.

## Route 2: co-op programs

A **cooperative education (co-op)** program alternates full-time paid work terms with study terms. A typical pattern gives three or more work terms before graduation. The degree may take five years instead of four, but you graduate with a year or more of real engineering experience, a network, and often a job offer from a co-op employer. The pay helps cover tuition. Co-op experience is also logged experience you can describe in a future licence application (check how your state board counts pre-graduation experience).

## Route 3: engineering technician (associate degree)

**Engineering technicians** work alongside engineers: they build and test prototypes, run lab tests, take field measurements, draft in CAD, inspect construction and maintain equipment. Common titles include civil engineering technician, mechanical drafter, electrical/electronics technician and survey technician. The usual entry route is a two-year **Associate of Applied Science (AAS)** in an engineering technology field, sometimes with certifications (for example, construction materials testing certifications from NICET or ACI, depending on the job).

Technicians generally do not take design responsibility or seal drawings. It is a skilled, hands-on career in its own right, and some technicians later continue to a bachelor's.

## Route 4: engineering technology bachelor's

A **BS in Engineering Technology** (accredited by ABET's ETAC) is more applied than an engineering BS, with less theoretical math (often less calculus and differential equations) and more lab time. Graduates are called technologists and often work in manufacturing, construction management, field engineering and testing.

The catch: in many states the licensure route for engineering technology graduates is longer (more years of experience) or not available at all for the PE. If a PE is your goal, check your state board's rules before choosing this degree.

## A worked comparison

| Route | Typical time | Leads to | PE route |
|---|---|---|---|
| University engineering BS (EAC) | 4 years | Engineer | Most direct |
| 2+2 transfer into an EAC BS | 4+ years | Engineer | Same as above |
| Co-op engineering BS | 4-5 years | Engineer with experience | Same as above, experience may count |
| AAS engineering technology | 2 years | Technician | Not on its own |
| BS engineering technology (ETAC) | 4 years | Technologist | Longer or unavailable, varies by state |

Rules vary by state. Check your state board via NCEES ([ncees.org](https://ncees.org)) and program accreditation on [abet.org](https://www.abet.org). Checked on 2026-10-23.

## Common mistakes

- **Taking courses that do not transfer.** Without an articulation plan, a semester can be lost.
- **Confusing "engineering technology" with "engineering".** They are different degrees with different licensure outcomes.
- **Treating the technician route as second-best.** It is a respected career with steady demand, and a good fit if you prefer hands-on work.
- **Ignoring co-op because it adds time.** The experience and pay often outweigh the extra semesters.

## Quick recap

- 2+2 transfer saves money and leads to the same accredited degree, if you follow an articulation agreement and stay on track in math.
- Co-ops trade time for paid experience and job offers.
- Technicians (AAS) and technologists (ETAC BS) are applied careers; the PE route from technology degrees is longer or closed, depending on the state.


Compare 2+2 transfer, co-op programs, and engineering technician and technology routes into engineering work.

Co-ops, technician routes, and community college

Engineering vs Engineering Technology | Degree Differences Explained

Degrees, licensure, design evidence, co-ops and alternative routes in.

From School to the Field

## Why it matters

Engineers calculate constantly: loads, flows, currents, temperatures, costs. For decades those calculations lived on paper pads and in spreadsheets. Today many engineers also use short Python scripts, because a script is easy to check, easy to rerun when an input changes, and easy to hand to a colleague. You do not need to be a software developer; you need a few habits that make calculations trustworthy.

## The core idea: a calculation is a mini design document

A good engineering calculation, on paper or in code, always shows:

1. **Inputs** with units and where they came from.
2. **Assumptions** stated plainly ("water at 20 C, density 1,000 kg/m^3").
3. **Formulas** with a reference (textbook, code section, datasheet).
4. **Results** with units.
5. **A sanity check**: an independent estimate that shows the result is reasonable.

Code makes points 1, 3 and 4 explicit by its structure. Points 2 and 5 are up to you.

## Habit 1: put the unit in the name

Python numbers carry no units, so `length = 3` could be metres, feet or millimetres. Put the unit in the variable or function name instead:

```python
span_m = 6.0           # beam span in metres
load_kn_per_m = 4.5    # distributed load in kN per metre
total_load_kn = span_m * load_kn_per_m
print(total_load_kn)   # 27.0 kN
```

When you read `span_m * load_kn_per_m`, the units visibly multiply to kN. If you ever wrote `span_ft * load_kn_per_m`, the mismatch would jump out. (There are libraries, such as `pint`, that attach real units to numbers. They are worth learning later; naming is the habit that works everywhere.)

## Habit 2: one formula per function

Small functions with clear names are easy to check against the textbook:

```python
G = 9.81  # m/s^2

def weight_kn(mass_kg):
    # Weight in kN from mass in kg: W = m * g, newtons to kN
    return mass_kg * G / 1000.0
```

A reviewer can confirm `W = m x g` and the newton-to-kilonewton conversion in five seconds.

## Habit 3: build in a sanity check

Before trusting a result, compare it with something you know. One cubic metre of water has a mass of about 1,000 kg, so it weighs about 9.81 kN (roughly one tonne-force). If your tank function says a 1 m cube of water weighs 9,810 kN or 0.0098 kN, you have a unit error. You can make the check automatic with `assert`:

```python
assert abs(weight_kn(1000) - 9.81) < 0.01, "1,000 kg should weigh about 9.81 kN"
```

If the assertion fails, Python stops with your message, so a broken calculation cannot quietly produce a wrong number.

## A worked example: will the floor hold the tank?

A 1.2 m x 0.8 m x 1.0 m deep water tank will sit on a floor. Is the average pressure within 4.8 kPa? (That is 100 psf, a typical code design live load for corridors and assembly areas; a real check uses the governing code and a structural engineer.)

```text
Volume  = 1.2 x 0.8 x 1.0      = 0.96 m^3
Mass    = 0.96 x 1,000         = 960 kg
Weight  = 960 x 9.81 / 1,000   = 9.42 kN
Pressure= 9.42 kN / 0.96 m^2   = 9.81 kPa
```

9.81 kPa is about double 4.8 kPa, so the answer is **no**: the tank needs a stronger floor, a spreader platform designed by an engineer, or a different location. Notice that the pressure under a full-depth tank equals the water pressure at the bottom (rho x g x h = 9.81 kPa for 1 m), which is a second, independent sanity check.

This example is a teaching simplification. Real floor checks include the tank's own weight, concentrated loads at its feet, the floor's structure and the governing building code, and they are done or reviewed by a qualified engineer.

## Common mistakes

- **Mixing kN and N, or mm and m.** Factors of 1,000 are the classic engineering error.
- **Hard-coding numbers in many places.** Define constants like `G` once.
- **No sanity check.** A program that runs without errors can still be wrong.
- **Hidden assumptions.** If the density or code value is assumed, write it in a comment.

## Quick recap

- Treat a calculation as a document: inputs, assumptions, formulas, results and a check.
- Put units in names, keep one formula per function, and define constants once.
- Use an independent estimate (and `assert`) to catch unit errors.

## Try it

Open the **Do** tab. The script already runs; you will write the one formula that turns the tank's volume into a load in kN, and the checks will confirm it against the sanity check.


Write a small engineering calculation with units in every name and a built-in sanity check.

Engineering calculations with Python

Engineering Math Pre-Req: Quick and Dirty Introduction to Python

## Why it matters

Engineers do not invent safety rules from scratch for every project. Decades of experience, research and, sadly, failures are written down in **codes** and **standards**. Knowing which ones apply, which edition is in force, and how to read them is a core professional skill. On the FE and PE exams you will be expected to use them; on the job, failing to follow them can cost lives and licences.

## Codes versus standards

The words are often used loosely, but there is a useful distinction:

- A **standard** describes how to do something well: how to test the strength of concrete, the dimensions of a bolt, the method for calculating wind loads, the safety requirements for a machine guard. On its own, a standard is **voluntary**.
- A **code** is a set of requirements intended to be adopted into law, usually by a government. Once adopted, it is **mandatory** in that jurisdiction. Codes often reference standards, which makes those standards mandatory too.

Example: a city adopts the International Building Code (a model code). The building code references ASCE 7 for structural loads and ACI 318 for structural concrete. Through that chain, the load and concrete standards become legally required for buildings in that city.

## Who writes them?

Most US codes and standards are written by private, non-profit **standards developing organisations (SDOs)** using committees of volunteers: engineers, manufacturers, regulators, insurers and users. Many SDOs follow a consensus process accredited by **ANSI** (the American National Standards Institute), with public review and the right to appeal. A few you will meet:

| Organisation | Known for | Discipline |
|---|---|---|
| ICC (International Code Council) | International Building Code (IBC), Residential Code (IRC) | Civil, mechanical, electrical (buildings) |
| ASCE | ASCE 7: minimum design loads (wind, snow, earthquake) | Civil |
| ACI, AISC | Concrete (ACI 318) and structural steel (AISC 360) | Civil |
| ASME | Boiler and Pressure Vessel Code, piping, dimensioning | Mechanical |
| ASHRAE | Ventilation, energy efficiency | Mechanical |
| NFPA | NFPA 70, the National Electrical Code (NEC); fire codes | Electrical, fire |
| IEEE | Power system and electronics standards (for example, the National Electrical Safety Code for utilities) | Electrical |
| ASTM International | Test methods and material specifications | All |
| ISO / IEC | International standards | All |

Government agencies also write mandatory rules directly, such as OSHA workplace safety regulations and state transportation department specifications.

## How a model code becomes law

1. An SDO publishes a new edition of a model code, typically on a three-year cycle.
2. A state or local government **adopts** it, often with local **amendments** (for example, stricter snow loads in mountain areas).
3. Adoption takes time, so jurisdictions are often one or two editions behind the latest one.
4. The local **authority having jurisdiction (AHJ)**, such as the building department, reviews plans and inspects work for compliance.

That is why the first question on any project is: **which code, which edition, with which local amendments?** The answer is on the AHJ's website or from the building department, not on the cover of the newest book. Editions and adoption status change; check the publisher and your AHJ. For example, see the ICC at [iccsafe.org](https://www.iccsafe.org) and NFPA at [nfpa.org](https://www.nfpa.org). Checked on 2026-10-23.

## A worked example

A mechanical engineer is designing a pressure vessel for a factory in Ohio. Questions to answer before calculating anything:

- Does the state require vessels to be built to the ASME Boiler and Pressure Vessel Code? (Most states regulate boilers and pressure vessels through a state inspector.)
- Which section and edition applies?
- Which ASTM material specifications are acceptable for the steel?
- Does the owner (the factory) have its own engineering standards on top of the code?

The design is then documented with references to the exact code clauses used, so a reviewer can check every step.

## Common mistakes

- **Using the newest edition when the jurisdiction adopted an older one** (or the reverse).
- **Treating codes as the goal.** Codes are **minimums**. A design can meet code and still be a poor design.
- **Ignoring local amendments.**
- **Quoting a standard from memory.** Always cite the clause and edition you actually used.

## Quick recap

- Standards are voluntary best practice; codes are written to be adopted into law and then become mandatory, often pulling standards in by reference.
- Most are written by consensus committees at SDOs such as ICC, ASCE, ASME, NFPA, IEEE and ASTM.
- Jurisdictions adopt specific editions with amendments, and the AHJ enforces them.
- Always confirm the code, edition and amendments before designing.


Explain who writes engineering codes and standards, and how a model code becomes law.

Codes and standards

How Codes and Standards Work Together | TCA 12

Code vs Standard: What’s the Difference? (ASME/API Explained for Engineers)

## Why it matters

Engineers make decisions that other people trust with their lives without ever knowing the engineer's name: the people crossing a bridge, working next to a machine, or flipping on a light switch. That trust is why engineering has a formal ethics code, why licensed engineers can lose their licence for misconduct, and why ethics appears on the FE exam. Ethical problems rarely look dramatic at first. They usually start as a small shortcut under schedule pressure.

## The NSPE Code of Ethics

The **National Society of Professional Engineers (NSPE)** publishes a widely used Code of Ethics for Engineers. Its six **Fundamental Canons** say engineers, in the fulfilment of their professional duties, shall:

1. Hold paramount the safety, health, and welfare of the public.
2. Perform services only in areas of their competence.
3. Issue public statements only in an objective and truthful manner.
4. Act for each employer or client as faithful agents or trustees.
5. Avoid deceptive acts.
6. Conduct themselves honourably, responsibly, ethically, and lawfully so as to enhance the honour, reputation, and usefulness of the profession.

The order matters. Canon 1 comes before Canon 4: when loyalty to your employer or client conflicts with public safety, **public safety wins**. The full code, with its detailed rules of practice, is on [nspe.org](https://www.nspe.org); state licensing boards also have their own rules of professional conduct, which are legally binding for licensees. Checked on 2026-10-23.

## A real case: the Hyatt Regency walkway collapse

In 1981, two suspended walkways in the atrium of the Hyatt Regency hotel in Kansas City, Missouri, collapsed during a crowded event, killing 114 people. The original design hung both walkways from continuous steel rods running from the ceiling. During construction, a change was proposed so that the upper walkway hung from the ceiling and the lower walkway hung from the upper walkway, using two shorter rods. That change roughly doubled the load on the connection at the upper walkway, which was already marginal. The change was approved without the calculations that would have revealed the problem.

Investigations found the engineers of record responsible, and they lost their engineering licences in Missouri. The lessons are still taught everywhere:

- **Design changes need the same rigour as the original design.** A "small" detail change can transform the load path.
- **The engineer who seals the drawings is responsible** for what they approve, including shop drawings prepared by others.
- **Communication failures kill.** Responsibility for checking the change fell between the fabricator and the engineers.

## Applying the code: a scenario

You are an EIT at a firm designing a pedestrian bridge. Your supervisor asks you to finish the connection calculations by Friday so the drawings can be issued. On Thursday you find that one connection, as drawn, does not meet the required capacity. Fixing it means a redesign and a one-week delay. Your supervisor says, "Issue it; we'll fix it in the field."

Work through it with the canons:

- **Canon 1:** a connection that does not meet capacity is a public safety issue. It takes priority over the schedule.
- **Canon 2:** as an EIT, you are not the engineer of record; you need your supervising PE to review the problem.
- **Canons 3 and 5:** you cannot misstate or hide the result.
- **Canon 4:** being a faithful agent means protecting the client from a defective design, not helping them issue one.

A good response: document the calculation clearly, raise it in writing with your supervisor, propose a fix and an honest schedule, and, if it is ignored, escalate within the firm (a senior principal or quality manager). NSPE's code also says that if an engineer's judgement is overruled in circumstances that endanger life or property, they shall notify their employer or client and other authority as may be appropriate. Most problems are solved at the first step, when someone states the facts clearly and early.

## Safety is an engineering responsibility

Engineers design for safety with **factors of safety** (designing for loads larger than expected), **redundancy** (more than one load path or backup system), **fail-safe** behaviour (a system that fails into a safe state) and **hazard analysis** (asking "what could go wrong?" before it does). On site and in the lab, engineers also follow workplace safety rules. Visiting a construction site, plant or substation requires the employer's safety training, the right PPE and an escort or supervisor; this course gives awareness only, not that training.

## Common mistakes

- **Thinking ethics is only about bribery.** Most cases involve competence, honesty and safety under pressure.
- **Staying silent because you are junior.** Raising a concern early and in writing is part of the job.
- **Approving what you did not check.** A seal or signature means "I am responsible for this."

## Quick recap

- The NSPE code's first canon is to hold public safety, health and welfare paramount.
- Practise only within your competence, be truthful, be a faithful agent, avoid deception.
- The Hyatt Regency collapse shows how an unchecked design change and unclear responsibility can be fatal.
- When safety is at stake: document, raise it in writing, propose a fix, and escalate if needed.


Apply the NSPE Code of Ethics to a real-world scenario where public safety is at stake.

Foundations for Engineering & Energy Careers

About this course

Course content

The Engineering Mindset

From School to the Field

Engineering Tools

Where this course leads

Next course on the path

Careers that use it