TLDR; Well, it was a good situation and my skill set is not ideally suited for a freelancer, as I'm a predominantly backend engineer. If you want details, I'm

TLDR; Well, it was a good situation and my skill set is not ideally suited for a freelancer, as I'm a predominantly backend engineer. If you want details, I'm going into them now. 1) Good situation The entire team is pretty much remote now. Working at the office is the exception, not the norm. Trying to be the first remote worker on a team is a chore, not only do you have to come up to speed, but you have to institute a remote culture as a newcomer, which is not easy. A fight I don't want to have. 2) Skill set I've been focused on backend systems. I don't have any front-end experience, especially stuff that you can put in a portfolio and wow potential clients with. That tends to cut down on freelancing. If you don't mind me asking, what hourly rate do you generally charge your clients? And what true hourly rate, factoring in meeting clients and writing RFPs? Freelancing is looking increasingly attractive to me. 3) Personal connections Somebody who I used to report to referred me to the job, and I enjoyed and will enjoy working with him. It's always nice to know somebody on the inside who vouches for the team and can show you the ropes.