SOFTWARE ENGINEER WHO CARES ABOUT THE WHOLE PRODUCT

I build useful software and care how it works for people.

I’m a software engineer who likes the awkward problems that sit between application code, data, infrastructure and the people using them. I’ve been doing this since 2014, and I’m happiest when I can understand the whole problem instead of stopping where one discipline ends.

I care about whether a system is dependable, whether the interface makes sense and whether the work has actually made someone’s day easier. I’m comfortable deep in technical detail, but I never want the technology itself to become the point.

My current role is wrapping up soon, and I’m looking for my next opportunity. If you think I could be useful to your team or project, tell me what you’re working on.

Start a conversation LinkedIn GitHub

HOW I GOT HERE

I’ve followed the work
that needed doing.

I did not set out to collect disciplines. I kept taking responsibility for the next part of the problem.

I started freelancing in 2014, mostly writing PHP and Python backends. Agency and lead-development work taught me how to ship for real clients, work inside existing systems and take responsibility beyond the original brief.

My skills span backend development, cloud infrastructure and automation. I’m comfortable designing APIs, working with data, troubleshooting complex systems and making existing software more reliable and easier to maintain.

The work has since taken me through data security, AWS data engineering and network automation around Cisco ISE and ServiceNow. Along the way I have kept building interfaces, dashboards and tools because I like seeing how the whole thing fits together, including the service behind it.

WHAT I WANT NEXT

I’m not trying to force that experience into one perfect job title. I’m looking for good people, a worthwhile problem and enough ownership to do the job properly. I value teams that can discuss trade-offs honestly and care what happens after the software ships.

A PROJECT OF MY OWN

I wanted a better HeadRush editor,
so I started building it.

The hardware is powerful, but some everyday jobs are awkward on its screen and the supplied web editor did not cover everything I needed. I started by mapping the undocumented API, then turned that work into the desktop application I wanted to use.

It has let me do the whole job: work out which problems are worth solving, design the interactions, build the application, test it with a real device and document it for other musicians. It is the clearest example of the way I like to work.

DEVICE APIUnderstand the thing properly

Mapped an undocumented API and checked assumptions against a real HeadRush device.

PRODUCTChoose problems worth solving

Focused the product on ToneMod, StageHand, Change History and the jobs the original editor makes difficult.

APPLICATIONBuild it end to end

Combined React, TypeScript and Tauri with device integration, recovery paths, state modelling and desktop packaging.

REAL USETest where it matters

Added automated coverage and responsive checks, then verified the important workflows with the hardware itself.

Explore the product View GitHub profile Support my work on Ko-fi

WHAT I CAN HELP WITH

The kind of work
I’m useful for.

I’m usually at my best when something important is complicated, manual or unreliable. I can get into the code, follow the data, talk through the workflow and help turn it into a system people can trust.

Build or improve software

I can take a rough requirement through service design, API, interface, tests and release. I’m equally comfortable making sense of an existing codebase and improving it without needless disruption.

Python, Django and Flask
TypeScript, REST APIs and testing

Make data useful

I build pipelines, reporting and data services with an eye on quality and the decision at the other end. Moving data is only worthwhile when people can understand and trust the result.

Glue, Kinesis, Athena and Redshift
QuickSight, Looker, Power BI and Bokeh

Remove operational friction

I look for repetitive work, fragile hand-offs and systems that fail quietly. The automation should be observable, maintainable and honest about what happens when something goes wrong.

AWS infrastructure and DevOps
Cisco ISE and ServiceNow

Design a clearer experience

I work through flows, hierarchy, feedback and edge cases so capable tools do not feel needlessly difficult. RushLink is where I have taken that responsibility from the first sketch to working software.

React, responsive interfaces and UX/UI
Data visualisation and reusable components

GET IN TOUCH

If this sounds useful
to your team, let’s talk.

If you need someone who can get into the code, understand the system around it and still keep the person using it in view, I’d be glad to hear what you’re working on.

LinkedInlinkedin.com/in/matcygal GitHubgithub.com/matcygal