Video summary

My Honest Career Advice to Aspiring PLC Programmers

Main summary

Key takeaways

Wellness and Self-Improvement

Key career/productivity strategies (and self-discipline takeaways)

  • Realize the “skills gap” is usually smaller than you think

    • Many aspiring PLC candidates can learn ladder logic / Studio 5000 / HMI / comms, etc.
    • The bigger blocker is often confidence, willingness to start, and persistence.

  • Commit early and avoid “waiting to feel ready”

    • People stall because they believe there’s “more time ahead.”
    • In trade roles, overtime + physical strain accumulates—eventually the decision is forced by the body (knees/back) or by layoffs.
    • Controls/PLC work is positioned as a way to shift from physical strain to brain-based work.

  • Build discipline through boring/hard stages

    • Expect difficulty: long hours, fatigue, family responsibilities, weekend downtime.
    • The advice is to push through until the goal is reached, not stop when it gets boring or tiring.

  • Stop using “tutorial loops” as your main learning method

    • Watching many PLC tutorials can feel like progress but often causes freezing when you face a real project.
    • Tutorials don’t automatically transfer to “write from scratch” performance.

  • Use a “build-from-scratch” project method to gain competence

    • Pick one familiar industry process (one machine/one problem).
    • Build a complete project from start to finish using real PLC software (e.g., Studio 5000 if available).
    • Connect to an HMI to visually verify the logic works.
    • Run and troubleshoot it end-to-end to prove you can do the work, not just recognize it.
    • Confidence comes from repeatedly going through the full cycle: design → implement → test → debug.

  • Prepare hiring success as “story + communication,” not just technical skill

    • You get hired on the story: how your skills impacted the team/company.
    • “Most technical person” doesn’t always win—clear communication matters with operators, engineers, and technicians.
    • Use the STAR method to package experiences:
      • Situation
      • Task
      • Action you took
      • Result (what happened)

  • Embrace problems as a core mindset

    • Practice becoming the kind of person who solves problems and follows through.
    • This is framed as increasingly valuable as AI reduces “mindless work.”

  • Follow-through is the differentiator

    • The key question: Can you start and finish?
    • The video’s central claim: people who get roles usually aren’t the most naturally technical—they’re the ones who persist.

Evidence/examples mentioned (student outcomes)

  • Greg Escobar: maintenance tech making ~100K/year with heavy overtime → transitioned to PLC/controls role, +15K pay and fewer hours (example of better work-life fit).
  • Pete: long-time maintenance → moved into a controls engineer trainee path at Caterpillar (controls work framed as less body-intensive).
  • Moha: built PLC projects from scratch with simulators; walked an interviewer through ladder logic (conveyor + traffic light processes) and got an Amazon role despite limited direct industry experience.

Presenters / Sources

  • Presenter: The video narrator (owner/founder of the company described; names of students provided)
  • Company/source referenced: The presenter’s company/program (Confident PLC Programmer Accelerated program)
  • Students/examples mentioned as sources: Greg Escobar, Pete, Moha
  • Employers mentioned: Amazon, Caterpillar
  • Tools/software mentioned: Rockwell Studio 5000 (and related HMI/VFD/PID tools)

Original video