About
I build software for the part of a project nobody enjoys: the handoffs, the missing document, the date that moves and takes six other dates with it.
Draft. The opening line and the first two sections are placeholder prose, written to hold the shape of the page; Ethan replaces them. The contact details and the note on how this site is built are real.
In his own words
Signal Studio is my product and my studio. It is where I work out how a small team keeps a promise — who owns what, what happens when a file never arrives, and how a plan changes without anyone losing the thread.
I work at both ends. I draw the surface, argue about the type ramp and the easing curve, then write the system that has to hold up when a provider goes down mid-upload. The two are the same job to me: an interface is a claim about how a system behaves, and it should be a true one.
Before Signal Studio I ran procurement and reporting systems, which is where the interest in this problem started — watching good teams lose days to a spreadsheet that three people were editing at once.
What I am looking for
I am interested in design engineering and product roles where the surface and the system are owned by the same person, or by a team small enough to argue in one room.
Contact
- GitHub
- ethanmcn2013-droid
- Signal Studio
- signalstudio.ie
This site
Static HTML, CSS and JavaScript with no framework and no runtime dependencies, built by a Node script and deployed as files. Everything it asserts about itself is on the colophon, computed at build time.