[hardwaresofton]

Not the person who asked the question but thanks again for sharing this.

I'm in a similar situation but without the full time job -- I can understand the retainer, but with the contracting do you charge per hour? I'd imagine you charge per day/week but that also feels a bit hard to balance evenly with a full time job.

[im_busy]

I charge a flat retainer every 2 weeks that gives a client the ability to give me work if they need stuff done, and the ability to call me in the middle of the night if things go down.

I've never had an issue balancing it; after the initial work of bringing a client on board the infrastructure handles itself. I've put a lot of work into automation and tooling, so the engineering teams I work for are able to self service on 90% of the things they need, and only need things directly from me rarely.

This isn't software engineering, it's infrastructure, which means I'm not on the hook to work on new product features sprint to sprint. There are times when I only have to do an hour or so worth of work for a client.

[hardwaresofton]

Thanks for sharing -- this has been eye opening for me. I do a lot of infrastructure for myself and others. Great to know that rewards for competence and skill like this is out there for ICs.

You've inspired me -- I'll be looking to try and make some more contracts like this in the future.

> This isn't software engineering, it's infrastructure, which means I'm not on the hook to work on new product features sprint to sprint. There are times when I only have to do an hour or so worth of work for a client.

Great, and I think it's honestly a very high ROI improvement as well, enabling a team of 5 developers to commit, deploy and generate value faster is absolutely worth it.

The only things I've considered in that space that could be as lucrative as you're doing now has been reducing cloud costs (and taking % of cost saved over 6mo).