FSU / ELECTRICAL ENGINEERING / HARDWARE SYSTEMS
Electrical engineering student building and testing embedded, optical, robotic, and electro-mechanical systems—with an emphasis on the evidence that proves they work.
01 / SELECTED ENGINEERING WORK
Each case study separates the engineering problem, individual contribution, system decisions, and what was actually validated.
Evaluate an optical diagnostic system that makes otherwise invisible density gradients in a flow observable and spatially selective.
Integrate reliable competition robot hardware for rapid specimen handling under strict match-time and field constraints.
Sequence a two-direction intersection in hardware while making conflicting green outputs structurally impossible.
Create a compact, documented interface for directional distance measurement using an ultrasonic sensor, servo, and microcontroller.
02 / ENGINEERING SYSTEM MAP
Select an area to trace the supporting skills and project evidence across sensing, logic, hardware, and validation.
03 / EXPERIENCE
Roles are kept distinct: technical work is documented as technical work, and communication experience is presented on its own merits.
Research
Florida Center for Advanced Aero-Propulsion · FSU
Supports self-aligning focusing schlieren development through optical alignment, analytical MATLAB plots, system evaluation, and experimental visualization work.
Robotics
FTC Team 16255 · Minerva Warriors
Contributed to competition robot hardware and electro-mechanical integration while helping diagnose mechanical, electrical, and autonomous-system interactions under event constraints.
Technical internship
U.S. Consulate General Guadalajara
Completed a full-time technical internship supporting troubleshooting, end users, and technology infrastructure in an operational environment.
Communication internship
U.S. Consulate General Guadalajara
Produced technical media, visual communication, event documentation, and coordinated deliverables. This role is presented as communication experience, not engineering work.
04 / TECHNICAL CAPABILITIES
Capability claims link to concrete project evidence rather than self-scored proficiency bars.
05 / ABOUT THIS BUILD
The site applies the same discipline it describes: define the audience, separate claims from evidence, make the system inspectable, and verify the release.
Give a recruiter the strongest evidence in roughly 30 seconds, while preserving a second path for engineers who want architecture, tradeoffs, tests, and failure boundaries.
A centralized TypeScript content model drives project cards, capability links, system-map evidence, résumé entries, and reusable case-study pages from one source of truth.
Responsive layouts, keyboard-operable controls, reduced-motion behavior, progressive disclosure, and deliberately larger typography keep the interface usable instead of merely decorative.
The release is checked with linting, TypeScript validation, a production build, route tests, and interaction review before the live version is updated.
ImplementationNext.js · TypeScript · Tailwind CSS · Framer Motion · Structured project data · Accessible HTML
06 / ABOUT
Ben is an Electrical Engineering student at Florida State University whose work sits at the intersection of electronics, experimental testing, robotics, instrumentation, and aerospace systems.
He is especially interested in environments where hardware must be built, tested, debugged, and validated—and where a useful answer comes from connecting physical behavior to measured evidence.
Aerospace hardware · Test engineering · Embedded systems · Sensors · Controls · Experimental research