Prototypes, tests, and iteration — documented like R&D.
I build real hardware: CAD → wiring → embedded firmware → testing. This site is structured as scrollable “pages” so each project reads like a short case study.
What I want
Target: R&D / Product DevAn R&D role where I can build prototypes, validate them with data, and improve them fast. I care about reliability, clean integration, and measurable results.
How to read this
Newer → Earlier- Newer projects show current capability: integration, testing, polish.
- Earlier projects show growth: modeling, basics, learning trajectory.
- Each project uses an R&D-style format: Problem / Approach / Results / Tools.
MIDI Controller + Audio Level Bars
Embedded • UI • PrototypingA tactile controller built for real workflow: knobs/faders + visual audio feedback (level bars). Designed to feel like a finished product, not a breadboard demo.
Photo / demo (add later)
Recommended: one clean top-down shot.
At a glance
- Problem: physical controls + clear visual feedback for audio mixing.
- Approach: modular firmware + simple UI states.
- Results: (add) latency, update rate, stability notes.
Engineering decisions
- IO strategy for smooth fader/encoder reads (debounce + filtering).
- UI behavior designed around fast “at-a-glance” understanding.
- Mechanical layout optimized for hand feel and spacing.
What to add later
- 1 wiring photo + 1 enclosure photo
- Short spec list (power, update rate, number of controls)
- 1-minute demo video
Thermocouple Temperature Controller (PID Test Rig)
Controls • Test • SafetyTemperature control setup for repeatable heating tests. Built to measure performance, tune response, and document repeatability like a real lab rig.
Photo / plot (add later)
This is hiring-manager gold.
R&D framing
- Problem: stable, safe temperature control with measurable performance.
- Approach: thermocouple sensing → PID → SSR/driver → heater.
- Results: (add) overshoot, settling time, steady-state error.
What I learned
- How noise & sampling affect control stability.
- How to tune for “fast but not sloppy.”
- How to document results so they’re credible.
Next milestone
- Add logged data export (CSV) + plotting.
- Define safety limits and fault behavior.
- Write a 1-page test report (spec → results).
Smart IV Bag / IV Pole System
Mechatronics • Medical-style device thinkingA mechatronics concept focused on practical usability: sensing + controls + a clear UI. Structured as a product-like system: requirements, constraints, and validation plan.
CAD / prototype photo (add later)
System overview
- Problem: improve monitoring + usability.
- Approach: load sensing + actuator concept + UI.
- Results: (add) accuracy, repeatability, user workflow.
Design constraints
- Stability and safe motion (limit switches / stops).
- Battery life + charging considerations.
- Calibration and drift over time.
Validation plan
- Bench test load readings across multiple weights.
- Repeatability tests (same weight, multiple trials).
- Motion cycle test (wear / reliability).
Autonomous Drone Build
Systems • Integration • IterationDrone platform work focused on real-world reliability: component integration, tuning, packaging, and a test-driven approach to improving flight behavior.
Flight / build photo (add later)
What matters for R&D
- Problem: stable flight + repeatable performance changes.
- Approach: tune parameters, log changes, validate with flights.
- Results: (add) “before/after” behavior and settings summary.
Highlights
- Repeatable tuning process (changes tracked + validated).
- Wiring and mechanical packaging improvements.
- Focus on “works every time,” not “works once.”
Add later
- Short checklist: build, setup, tuning steps.
- Table: change → expected effect → observed effect.
Automotive Trim Piece (Design + 3D Print)
CAD • Fitment • IterationPractical CAD-to-physical part workflow: measure, model, print, test fit, revise. This project shows early “real-world constraints” thinking.
Before/after (add later)
Process
- Problem: replacement / improvement part that fits and holds up.
- Approach: measure → CAD → prototype prints → revise.
- Results: (add) fitment notes + print settings/material.
Growth point
- This is where I learned iteration discipline (small changes, retest).
- Fitment taught tolerance and real-world variability.
Upgrade later
- Add a dimensioned drawing snapshot.
- Add a “rev history” note (Rev A, B, C improvements).
3D Modeled Water Pump
CAD • Mechanisms • Learning fundamentalsA modeling-heavy project that shows fundamentals: part breakdown, assemblies, and mechanical reasoning. Great for demonstrating growth from CAD skill → integrated mechatronics later.
Render (add later)
What it demonstrates
- Understanding of components and assembly relationships.
- Better modeling practices over time (naming, constraints, structure).
- Add: what you’d do differently today (DFM, tolerances, sealing).
Lessons learned
- How to structure assemblies cleanly.
- How to think about motion constraints and interfaces.
Make it stronger later
- Add a simple section view or interface detail.
- Add a short “requirements” paragraph retroactively.
Early CAD Models (Growth)
Show progressionA curated set of earlier models to show growth over time. Keep this section selective: 4–8 items max, each with one sentence.
Gallery placeholder
Best format: 2×3 grid with short captions.
How to present growth (do this)
- Label each: Year / Context (class, personal, client).
- One line: what you learned (constraints, tolerances, assembly).
- End with: “What I do differently now.”
Example entries (replace later)
- Bracket model — learned constraints & clean sketches.
- Assembly practice — learned mates and motion planning.
- Fitment part — learned tolerances and iteration.
Why this helps hiring
- Shows trajectory, not just isolated wins.
- Signals coachability and learning speed.
Let’s talk
Fastest response: emailIf you’re hiring for R&D / product development roles (mechanical, mechatronics, test), I’d love to connect.
Next improvements (later)
- Add resume PDF + set the Resume button link.
- Add 1 hero photo per project + 1 results plot when possible.
- Make each project include a measurable result (even simple ones).