Video summary
What exactly IS Engineering Physics???
Main summary
Key takeaways
Main ideas / concepts conveyed
-
“Physics” as the foundational science
- Physics is framed as the most basic root level of science, grounded in experiments with the real world.
- The speaker contrasts physics with pure math: math could (in theory) be developed without needing a universe, while physics describes what actually happens in reality.
-
“Engineering physics” as an interdisciplinary approach
- Engineering physics is defined as an approach to engineering that aims to understand the common underlying rules across engineering disciplines.
- It’s described as not just engineering for physics, but applying a physics-informed mindset to design and solve engineering problems by understanding root causes.
-
Why study it
- It trains you to see problems from multiple angles.
- It helps solutions be more than the sum of parts by enabling deeper integration across disciplines.
- It addresses the “silo problem” in engineering departments (e.g., mechanical, electrical, and software working separately, then handing results off).
- It aligns with the idea that real engineering problems require knowledge from mechanical + electrical + software + materials + math, etc.
-
“NG” / “ang fizz” as the program (likely Engineering Physics)
- The program is framed as:
- Understanding-first (not memorization or formula-sheet dependency).
- Heavy on theory and conceptual mastery, with applied projects later.
- It emphasizes building a common interdisciplinary core, then using electives for specialization.
- The program is framed as:
-
Achievability and outcomes
- The speaker claims that building a strong foundation within an undergrad timeline is achievable.
- Students complete applied capstone/device projects and demonstrate practical skills such as building imaging/robotic/sensor systems.
The overall theme: learn the “why” and “how” through physics foundations, then apply that understanding to real engineering systems.
Methodology / instruction-like structure (program approach and learning strategy)
1) Build “common core” interdisciplinary literacy (early years)
The curriculum provides grounding in subjects needed across engineering, including:
- Electromagnetism
- Thermal systems / thermal engineering
- Computational dynamics and statics
- Engineering math
- Additional math, including vector-calculus analogs in digital circuits
- Quantum mechanics
- Computational multiphysics
These topics are positioned as the “glue” that helps students understand how areas fit together and supports design thinking.
2) Use the core to create cross-domain transfer (“whole toolbox”)
- Learning is framed as iterative conceptual mapping:
- Learn one domain deeply (e.g., circuits).
- Then recognize other domains (e.g., fluidic systems) can be modeled similarly.
- This reduces time wasted relearning disconnected concepts and increases depth through analogies/comparisons.
3) Delay specialization until you have a strong foundation (flexible electives)
- Early required coursework is described as “light,” creating flexibility for electives.
- Students can:
- Take advanced/upper-year electives earlier if desired.
- Use elective space for research, clubs/teams, and extracurricular development.
- Potentially create minors/pseudo-minors by combining engineering physics tech electives with courses from other departments.
4) Progress from foundational theory to applied projects (upper years)
Third/fourth-year structure includes applied engineering topics and capstone synthesis, such as:
- Active electronics
- Microcontrollers
- Communication and project management / soft skills
- Sensors, actuators, and control
- Numerical methods
- Statistical mechanics (entropy/thermodynamics connection)
- Signals and systems
- Engineering economics
- Capstone design/synthesis project
- Ethics, equity, and law in engineering
5) Ensure employability via broad problem-solving
The repeated claim is that a physics-informed interdisciplinary foundation supports transferable problem-solving skills for:
- technical roles,
- non-technical roles (e.g., project management),
- and research/industry across many sectors.
Examples of device / capstone project outcomes mentioned
- Devices using image recognition to distinguish real vs fake needles and exchange needles
- Devices that identify fingernails, then paint and cure nail polish with UV light
- Phone-ordered drink dispensing and mobile bar systems
- Projection/overlay systems so shadows don’t block images (play games while eating/waving hands)
- Hand/vein imaging overlays using internal hand/vein visualization
- Flying robots that dodge hands and enable playing physical table tennis
- Systems that track eye reaction time to assess impairment for driving decisions
- Voice-controlled robotic assistance
- More general capstone directions referenced:
- robot stair climber
- optical systems
- solar cell fabrication
- labs in a nuclear reactor context (described as possible capstone directions)
Specializations and how the core supports them
-
Research/specialization areas mentioned include (e.g., at McMaster in the narrative):
-
Nanotech engineering
- nano/micro devices
- photonics (light-matter interaction; improving internet speed)
- microdevice fabrication techniques
- solar energy and energy generation
-
Nuclear engineering
- connected to Ontario energy generation and base load power
-
-
These areas are described as linked by the shared need for deep physics grounding.
-
Additional synergy mentioned:
- Biomedical engineering (AI biomed or related cores)
- biosensors
- bio-photonics and sensing/actuation
- diagnosis/treatment via nuclear medicine/radiation physics
- Smart systems engineering
- Quantum computing
- AI / machine learning
- with the note that physicists are often sought after for strong math foundations and problem-solving methods
- Biomedical engineering (AI biomed or related cores)
Career outcomes described (where grads can work)
Example employers / sectors mentioned
- L3 Wescam (infrared optical systems / night vision)
- North (optical systems for motion control)
- Siemens (project management for electromagnetic equipment)
- ATS (systems engineer / automation systems manufacturing)
- Raytheon (assembly and test engineer)
- Canadian nuclear labs (research scientist)
- Renewable energy tech (solar mentioned)
- Dofasco (electrical/automation roles)
- Health Canada (healthcare policy)
- Panasonic (network engineering)
- Rogers (network engineering)
- Shopify (learning systems architect)
Proof point and example trajectory
- A Nobel Prize-winning physics professor is mentioned as a proof point (name not provided).
- An example individual trajectory (“Gabe”):
- Engineering Physics undergrad, later a PhD
- Now at McGill in a lab role (Cobra Lab referenced)
- Described as an “expert generalist” capable of varied applied tasks across tech domains
Speakers / sources featured (as named in subtitles)
- Brendan Kass — infrared optical systems at L3 Wescam
- Paul — optical systems for motion control at North
- Amanda Kelly — project managing electromagnetic equipment at Siemens
- Brendan Wood — systems engineer at ATS
- Jeanette Moore — nuclear systems engineer
- Hany — working at Sanctuary AI
- Jordi Rose — founder of Sanctuary AI (also referenced as another Engineering Physics graduate)
- Lindsey Vasilich — hired into an electrical engineering department
- Jamison — quote: “something… teaches problem-solving… learn how to learn”; now a designer at AMD
- Raimi — mentioned regarding an extended internship
- Gabe — Engineering Physics graduate; later PhD; referenced with work at McGill (Cobra Lab)
Institutions / organizations repeatedly referenced
- McMaster University
- AMD
- Siemens, Raytheon, L3 Wescam, ATS, North, Health Canada, Panasonic, Rogers, Shopify, Dofasco
- Canadian nuclear laboratories / nuclear industry references