If you are hiring somebody to own a system, I would like to hear about it

You do not need a long message. What helps most is what the system does, what is going wrong with it or what needs building, and what the team looks like today.

If you are unsure whether I fit, the quickest read is how I work, because that is the part that transfers when the stack does not match. If the stack is the question, the senior Node.js page answers the usual requirements with the system where I met each one.

I am not looking for contract or agency work, and I do not publish rates, because the conversation should start with the problem rather than with a number.

A system somebody has to own. That is the work I am good at and it is the work I enjoy: the part of the product that has to be correct, that runs when nobody is watching, and that somebody gets called about when it is not.

Permanent rather than contract. The work I am proudest of took years, which is not a coincidence. A system only teaches you its real behaviour over a long period, and most of what I know came from operating something long enough to be surprised by it repeatedly.

Remote, with a team that writes things down. I have worked mostly alone, so I have strong habits around written plans and handovers, and those habits are wasted somewhere that decides everything in meetings I would be asleep for.

The stack matters less than most job descriptions imply. If it is Node and TypeScript I will be useful in week one. If it is something I have not used, I will be slower for a few weeks and no slower after that, and the reasoning behind that claim is on how I work.