27 karma · joined April 25, 2022
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.
I've been doing it for the past few years, and it hasn't had a negative effect on my mental well being or family relationships. I work extra here and there, sure, but so does everyone, and it has more to do with "we need to do this at this specific time" than any actual extra work needing to be done.
* the full time and contracting gigs are in separate time zones, which helps time management.
* I only actually work ~45-50 hours a week total, but all work is complete.
* I only take on work that aligns. I use several extremely standard tools and ALL gigs are all the same, which lowers my cognitive overhead a lot.
It's going fine; I measure that based on my performance reviews all being excellent, my clients all paying the bills on time, and all work is done in a timely fashion. I do individual contributor infrastructure engineering at the senior+ level.
Managing the calendar is the toughest part, making sure things don't overlap is difficult. My full time calendar is relatively light, the contracting gig on the other hand is starting to get on my nerves with the amount of meetings they're pushing me to attend.