Joseph Coifman

Hey, I’m Joseph. I make things
that work.

Computer Engineering at McMaster University. I spend my time building software, experimenting with hardware, and figuring out how the two fit together.

Looking for Summer 2027 internships.

Explore my work View résumé
EmailGitHubLinkedIn

Software, a little hardware, and plenty of figuring things out.

Fantasy IQRaspberry PiPost of Joy

A few things I’ve made.

All work

Full-stack development, 2026

Fantasy IQ

A fantasy league has a lot of moving parts. I built Fantasy IQ to bring league management, player research, draft simulation, and AI-assisted trade analysis into one place.

I built the Next.js interface and FastAPI backend, with PostgreSQL for storage. The interesting part is making recommendations account for league rules and the roster—not just a player’s season total.

Next.js / FastAPI / PostgreSQL

The full story GitHub
Fantasy IQ dashboard with league management, research, comparisons, and trade tools
A second Fantasy IQ view comparing Josh Allen and Patrick Mahomes
Full screenshot

One workspace.

A Next.js interface connects league management, player research, and draft and trade decisions.

A Python backend.

FastAPI handles application requests, with PostgreSQL storing the platform’s data.

Context from NFL data.

External APIs feed the player, statistics, and matchup data used across the research views.

Reasoning you can inspect.

Custom rankings and recommendations account for league rules and roster needs. AI analysis surfaces evidence and risks.

The reasoning needs to be visible. Player analysis includes the evidence, risks, and missing context behind a recommendation.

Raspberry Pi Control Server, 2026

A small server. A physical connection.

I put system monitoring, file storage, and Arduino controls into a Flask dashboard running on a Raspberry Pi. A browser request travels through Node-RED and USB serial to an LED or servo.

I built the monitoring and file-management views and connected the device controls. It’s a working local-network prototype.

Python / Flask / Raspberry Pi / Arduino / Node-RED

The full story GitHub
Raspberry Pi server interface with LED and servo controls
Full screenshot

Sending a command isn’t the same as confirming it happened. The interface records requested state; adding hardware acknowledgement is a next step.

Following a command

From a click
to a physical output.

The prototype’s control path. Each connection has a different responsibility.

  1. Start in the browser.

    The dashboard puts system monitoring, file storage, and LED and servo controls in one interface. The device controls send a request over the local network.

  2. A small computer, running the server.

    Flask runs on the Raspberry Pi. It serves the dashboard and handles the application routes, including requests from the control interface.

  3. Translate the request.

    The control request passes to a Node-RED HTTP flow. That flow bridges the web application and the Arduino's serial connection.

  4. Cross into hardware.

    The Arduino receives the command over USB serial and handles the requested output. This is the handoff from a web request to the microcontroller.

  5. Make a physical change.

    The command controls the LED or servo. The interface stores requested state; a hardware acknowledgement loop is still a next step.

Collaborative web development, 2026

Post of Joy.

A website with people
on the other side.

I worked with the nonprofit’s stakeholders on a responsive website, from interface changes to persistent content and deployment.

We used Flask and Firestore, then deployed on Google Cloud Run. The work meant connecting what stakeholders needed with what the application could actually support.

Flask / JavaScript / Firestore / Cloud Run

The full story Visit the website
Post of Joy desktop website with its birthday-card initiative
Post of Joy mobile homepage
The live website, on desktop and mobile.

McMaster IEEE, 2026–2027

Learning it.
Then helping teach it.

I am the team lead for microcontrollers and microprocessors at McMaster IEEE Computer Society. That includes office hours, technical questions, certification support, and planning projects with the other executives.

Right now, I’m preparing Arduino workshops around an object counter and a touchless synthesizer. The guides are ready to explore; the sessions are still upcoming.

Inside the workshops
Industrial Object Counter guide coverObject counter ↗Touchless Musical Synthesizer handbook coverTouchless synth ↗

Beyond my own projects

Learning with other people.

Experience
  1. May — Sep 2026

    Talkerstein Consulting Group

    Summer Intern · Product Requirements & System Design

    Worked with founders on Vision Portal requirements, intake workflows, and system concepts. My foundational work and documentation were later used by the team to build its internal project management system.

  2. 2026 — 2027

    McMaster IEEE Computer Society

    Microcontroller & Microprocessor Team Lead

    Lead both teams, run office hours, and support member certification. Prepare two Arduino workshops and coordinate projects with other executives.

  3. Jan 2026 — present

    McMaster University

    Research Assistant

    Review wearable-sensor literature and work on sensor identification, run-data processing, and test guidelines. Research paper in progress.

Outside engineering

Usually Joey.
Often on a court
or out for a run.

I have a competitive tennis background, and I enjoy running. I’ve run 10KTO and have a 10K personal best under 45 minutes. Next up: a half marathon in 2027.

I’ve also taught swimming and worked as a lifeguard. Sport and teaching are a big part of my life—and part of why I’m interested in technology that connects to real-world activities.

A little more about me