# What Does a Mechanical Engineer Do? | Part 03 | English Learning Podcast

[Watch on tuber](https://tuber.guzus.xyz/video/PRUsT5fb9FE/summary) · [YouTube](https://youtu.be/PRUsT5fb9FE)

**Score: 58/100 · skim**

This is an English-learning podcast episode in which Diego, a mechanical engineer, walks through his job in plain language: daily tasks, teammates, tools, safety, boring routines and lessons learned. In the last third he turns it into a template for describing any job in English, with useful phrases and follow-up questions to ask other people.

- **0:02-1:20** — **What a mechanical engineer actually does.** Diego says this is part three of Mr. English Lab's work series. He describes mechanical engineers as people who design, build, test, improve and maintain machines, from car parts and pumps to heating systems and medical equipment. He stresses that the job is more than drawing: it means thinking, planning, checking information, talking with people and learning, and it splits between desk work and visits to the workshop or production floor.

- **1:21-3:00** — **Diagnosing before fixing.** His first example is a small factory whose machine breaks down several times a week and costs it output. The engineer talks to workers, studies the machine and its history, then picks a fix: a repair, a new part, a change in how it's used, or a redesign. The key point is that guessing too fast wastes money or creates new problems. In a second story, a "small rattle" that people dismissed was getting louder at one point in the process. The workers' observations led the team to a part that wasn't moving smoothly. The lesson: people who use a machine daily notice things you can't see from a desk.

- **3:01-4:58** — **Workplaces, morning routine and the team.** Mechanical engineers work in factories, offices, labs, power plants, transport companies and building sites, either on new products or on existing machines. Diego starts his day with his schedule, messages and notes, then ranks tasks. A safety issue or a stopped machine comes before a routine report. Short team meetings bring together mechanical and electrical engineers, technicians, production workers, managers and safety staff, and each brings different knowledge.

- **4:58-5:42** — **Communication as a core engineering skill.** He changes how he explains things for each listener: repair steps for a technician, cost and time for a manager. He also listens, because managers know the schedule, technicians know how the machine behaves during a shift, and workers know where the delays come from. He offers two questions to use: "Could you show me what happens when the machine stops?" and "When did you first notice this problem?" The second one shows whether a problem is new or has been growing. A design can be correct on paper and still be hard to use, so it has to be safe, practical, reliable and easy to maintain.

- **5:43-7:29** — **Tools, testing and materials.** CAD drawings show a part's shape, size and how it fits with other parts, and they are reviewed by others rather than decided alone. Workshop visits catch problems a screen hides: a tool that can't reach a bolt, too little room for a worker, a part that needs to be stronger or easier to replace. Testing measures movement, temperature, pressure, noise or vibration and compares the results with what was expected. Choosing materials is a tradeoff between strength and weight, heat tolerance, purpose and environment.

- **7:30-8:33** — **Safety and the environment.** Safety applies at every stage: clear instructions, safe work areas, protective equipment and set procedures during repairs. Diego reports unsafe conditions even when a machine seems to be working, because protecting people matters more than speed. On the environmental side, energy-efficient machines lower costs and parts that are easier to repair cut waste.

- **8:34-10:23** — **The unglamorous parts: routine, checking, waiting.** Updating records, re-checking measurements, organizing files and writing reports are repetitive but keep a clear record. Diego once found a measurement he had copied wrongly. Fixing it took minutes, but finding it after the machine was built would have cost far more. His point is that slowing down can save time. He also spends time waiting for parts, tests or reviews, and uses it to prepare, write down questions or help coworkers. When the facts show a first solution was wrong, engineers have to be ready to change the plan.

- **10:24-11:57** — **Rewards and handling disagreement.** The best part for him is seeing a drawing become a working machine that helps people, and learning from technicians and senior colleagues. The hard parts are tight deadlines, breakdowns at bad times, budget overruns and disagreements. When people disagree, he asks each person for their reasoning. Often one is thinking about safety, another about cost, another about repair time. He treats different opinions as possibly showing a risk he missed, not as attacks.

- **11:58-14:57** — **Key skills and the path into the field.** The skills he lists are problem-solving, attention to detail (small measurements affect how parts fit), teamwork, clear communication (especially about safety), organization (knowing which design version is current) and curiosity. Curiosity means asking "what changed before the machine stopped?" so you treat the cause, not just the first sign. The usual path is an engineering education in math, physics, materials and design, plus practical training, and learning continues after you're hired. He admits he once thought senior engineers knew everything. Now he sees that good engineers know how to find reliable information, ask, test and correct mistakes. A patient senior engineer once answered his "too simple" question and made him comfortable asking. He suggests the phrases "I have checked this part, but I am not sure about the next step" and "Could you review this plan with me?"

- **14:58-17:58** — **Advice for aspiring engineers and practice phrases.** Start by being curious about everyday machines: how a fan moves air, why bikes have gears, how a pump moves water. If you can explain a machine simply, you probably understand it. He then models short descriptions such as "I help design, test, and improve machines" and practice sentences ("I am responsible for checking equipment," "One difficult part of my job is meeting a tight deadline"). He also gives a stalling phrase, "That is a good question. Let me think about how to explain it." To handle technical words, start with the main idea ("This part helps the machine move smoothly") or a comparison, such as a bicycle needing regular checks.

- **17:59-20:38** — **How much the field varies, plus the surprises.** Mechanical engineering reaches into transport, buildings (heating and cooling, working with architects), energy, farming and healthcare. The job title can be the same while the tasks differ a lot, and laws, tools and training vary by region, so he asks about local rules when he joins a project. Two things surprise people: how much writing the job involves (reports should be clear, not fancy) and how much time goes into planning goals, costs, materials, schedule and risks. There is a short comic bit about wishing a machine could diagnose itself and order its own parts, and about reports that never end.

- **20:39-24:03** — **Looking back, health, and a template for describing any job.** After each project he reviews what went well, such as communication, and what to improve, such as testing earlier. He takes care of his health by moving, resting and giving his eyes breaks from the screen. He then gives a formula: job title, then main tasks, the people you work with, one thing you enjoy, one challenge, and optionally a short story. He shows it with a teacher and a driver, and suggests follow-up questions like "What is a normal day like for you?" and "What tools do you use?" He closes by saying every job mixes responsibility, teamwork, routine and surprises, and encourages listeners to describe their own work with confidence.

**Practical takeaways:**
1. **To describe your job in English,** use the formula: title, main tasks, coworkers, one thing you enjoy, one challenge, and a short story if you have one.
2. **Find the cause before fixing:** ask the people closest to the problem, using questions like "When did you first notice this?" and "Can you show me what happens?"
3. **Check details early.** One wrong number found before building costs minutes, and found afterward it costs far more.
4. **When people disagree, ask for each person's reasons** (safety, cost, time) so you can compare the options fairly.
5. **Asking for help is a responsible choice,** and a phrase like "I have checked X, but I'm not sure about the next step" makes it easy.

## Audience signal

- No high-signal audience themes available.