Zachary Cohen

Electromechanical Systems Engineer

Electromechanical Systems Engineer
Designing integrated hardware systems from architecture to deployment

I design and build electromechanical systems that combine mechanical structures, embedded electronics, and firmware into reliable working hardware.

My work focuses on system architecture, clear interface boundaries, and hardware that can be built, tested, and iterated quickly. I spend most of my time turning ideas into physical prototypes, building test platforms, and documenting the decisions that make complex systems maintainable.

I also apply the same systems mindset through volunteer leadership in FIRST Robotics Competition, including event operations, judging, and mentoring engineering teams.

How I Build Systems

My work centers on defining system architecture, developing mechanical and electronic subsystems, integrating embedded firmware, and building the infrastructure needed to test and validate complex systems.

Featured Systems

• Sentry V3 — Embedded control platform for a pan-tilt actuation system, integrating sensors, motor drivers, and safety-oriented control logic.
  Core domains: PCB, embedded firmware, controls, integration, test
• Autonomous Surfer Fleet — Distributed control system for small autonomous vessels, combining navigation, telemetry, and power management. Core domains: controls, embedded systems, communications, power, systems integration
• SPARK Programming Board — Hardware expansion board that exposes debugging, power control, and protocol interfaces during embedded bring-up. Core domains: embedded tools, hardware interfaces, firmware, validation
• Fusion System Blocks — Visual systems documentation framework for mapping architecture, subsystem boundaries, and interface definitions across multidisciplinary projects. Core domains: systems architecture, documentation, integration planning, workflow design

Other Work

• FIRST Robotics
• Teaching Portfolio
• Documentation Library

How I work

• Start with system architecture before touching implementation.
• Define clear electrical, mechanical, and software interfaces.
• Design subsystems to evolve independently.
• Treat testing as part of design, not something done afterward.
• Document decisions so systems remain maintainable years later.
• Consider manufacturing and serviceability from the beginning.
• Apply the same systems thinking in FIRST Robotics Competition event operations, mentoring, and technical leadership environments.

Engineering Focus

• Embedded systems
• PCB design
• Electromechanical integration
• Controls and actuation
• Rapid prototyping
• Hardware test infrastructure
• Systems architecture

Contact

• GitHub: github.com/zcohen-nerd
• LinkedIn: linkedin.com/in/zachary-cohen-nerd
• Email: zachary@zcohen-nerd.com