Portrait of Patrick Ong

Industrial Engineering Cal Poly SLO Class of 2026

Open to 2026 roles in operations, supply chain, and industrial engineering

Patrick Ong

I build clearer systems for operations, reporting, and AI-assisted automation.

Industrial Engineering student at Cal Poly with KLA experience improving procurement reporting, workflow visibility, and cross-system automation with Python, Power BI, and AI-assisted workflow tools.

  • Seeking 2026 internships and full-time roles
  • Best fit: operations, supply chain, procurement, systems
  • Approach: map the workflow, then automate the repeated work
  • KLA Procurement intern and senior project lead
  • 80% -> 87% Contractor course completion lift
  • 12-15 hrs/mo Manual reporting time removed
  • Python + AI support Automation tooling for finance, ops, and reporting workflows

How I improve a workflow

1. Workflow signals

Bottlenecks Approvals Reporting gaps

Where the friction shows up first

2. System context

Snowflake SAP SharePoint

Where the data, docs, and status already live

3. Automation build

Checks, dashboards, AI support

Python, reporting logic, and repetitive work reduction.

4. Team outputs

Finance Procurement Reporting Ops

Cleaner handoffs and faster visibility

5. Business impact

12-15 hrs/mo back

Less manual reporting and fewer repeated checks.

01

Systems thinking first

I start with the workflow, then connect the systems, then automate the repeated work.

The common thread in my work is reducing friction. I map where information gets stuck, fix the handoffs, and build the reporting or automation layer that helps teams move faster with less manual effort.

Map the workflow first.

Find bottlenecks, handoff gaps, approval friction, and rework before deciding what to automate.

Workflow mapping Root cause Time studies

Connect the systems that already run the work.

Tie together reporting, ERP, data, and workflow tools so teams spend less time chasing updates manually.

Snowflake SAP SharePoint Power BI

Use AI where it removes real repetitive work.

Apply Codex, Claude agents, and automation tooling after the workflow is clearly defined, so AI supports the system instead of replacing the thinking.

Codex Claude agents RPA

02

Recent experience

Operational work with measurable outcomes.

These two KLA projects best represent the type of work I want more of: workflow clarity, reporting automation, and better operational visibility.

Built a contractor compliance pipeline that improved visibility and cut reporting effort.

80% -> 87% course completion lift
Daily refresh moved from monthly reporting
12-15 hrs/mo manual work removed

Designed an automated reporting flow across Linux VM outputs, SharePoint, Python, Excel, and Power BI.

Linux VM SharePoint Python Excel Power BI
  • Built mismatch and visibility checks that pushed data quality close to 100%.
  • Surfaced incomplete, inconsistent, and missing contractor records more clearly.
  • Made status tracking easier for a global procurement workflow.

Mapped a complex approval flow and built the baseline for redesign.

9.6 days supplier submission cycle
38.3 days time-to-fill baseline
5 directions improvement paths proposed

Led a Cal Poly senior project on KLA's Staff Aug and SOW process in Beeline, from intake through final approval.

Intake TAPFIN Beeline DocuSign Approval
  • Identified sequential approvals, intake quality, and visibility gaps as key causes of delay.
  • Traced rework and information loss across Beeline and DocuSign.
  • Coordinated weekly stakeholder workshops to refine recommendations.

Additional experience: Odin Diagnostics CRM and dashboard design, PokeChef shift operations, Tesla production and quality inspection, and student leadership through Grow Crew and Home Greens SLO. I increasingly apply the same systems mindset with AI tools to remove repetitive work across reporting, finance, and cross-functional operating tasks.

03

Systems beyond the internship work

Projects that show how I think through systems, data, and execution.

Different domains, same pattern: understand the process, structure the system, and make the result easier to operate.

Automated Package Size Sorter

Designed and built a package sorting system that detected size, routed items, and supported operator monitoring.

System: Keyence vision, ladder logic, pneumatics, and HMI controls.

Result: Automated size-based sorting without manual intervention.

Signal: combines controls logic, sensing, and operator usability into one working system.

Senators Stock Transaction Database

Built a relational database that made congressional stock disclosures easier to explore and compare.

System: MySQL, ER modeling, SQL analysis, and Tableau dashboards.

Result: Surfaced ROI, portfolio shifts, sector trends, and transaction activity over time.

Signal: turns messy public data into a cleaner model for analysis, comparison, and decision support.

Maglio Inc. Process Improvement

Studied a CNC setup process to find where time was being lost and where process changes would matter most.

System: Time study, bottleneck analysis, and fixture standardization.

Result: Reduced setup time by 22%.

Signal: shows how I move from observation and data collection to a practical process change.

04

Background

Grounded in operations, with a strong bias toward better systems.

I am a Cal Poly San Luis Obispo Industrial Engineering student graduating in June 2026. I am most interested in operations, procurement, supply chain, and the systems that keep work moving.

I like starting with a messy process, a visibility gap, or a workflow that takes too much manual effort. Then I work backward from the friction and forward into something clearer, faster, and easier to run.

Codex Claude agents Snowflake SAP RPA Power BI Python SQL Excel Tableau SharePoint Power Automate Six Sigma Green Belt
School
Cal Poly SLO · B.S. Industrial Engineering · June 2026
GPA
3.4 · President's List · Dean's List
Coursework
Enterprise Analytics, Operations Research, Production Planning, Data Management, Statistics
Outside of work
Motorcycles, mountain biking, and life around San Luis Obispo

Contact

Open to roles and conversations in operations, supply chain, and systems improvement.

Email is the fastest route, but you can also leave a note if you want Patrick to follow up about a role, project, or workflow problem.

Want Patrick to follow up?

Leave your contact details and a short note. It lands in a secure intake flow so follow-up is easier to track and respond to.