One issue in particular that I ran into was the difficulty in context switching between my day job and my side job. I imagined being able to do an hour here or there before or after work. But in reality I found it really hard to get any meaningful work done in an hour, which meant I needed to allocate larger chunks of time than I originally planned. That meant I often ended up sacrificing entire evenings, or chunks of my weekend on my side job. The difficulty in context switching also caused me to procrastinate a lot, which also made me feel terrible about myself.
I had the exact same experience last year and it fucked me up good with anxiety (which I've never experienced before) and I couldn't eat properly for weeks causing me to lose a stone in weight.
I had the exact same preconceived notions you did with the 1 hour block a day mon-friday. Seemed like it would be a breeze at first and easy money. The problem with this is it just turned into feeling guilty when I wasn't working on it, even outside of the allotted hour. I think I felt like this because there was no clear seperation of environment as I was be doing the work at home and the result was I felt like I was just working all the time.
I did learn a valuable lesson though and that is that my free time is a lot more valuable than I realise.
I will never again consider doing side gigs for anyone other than myself.
I was under the impression that I would be able to do it because back when I was in high school and college I can easily get good grades with barely any effort. I even had time to enjoy other leisure activities. Turns out, I was just oblivious what real responsibilities are.
Learn Salesforce development. I've accepted a new contract role that is full time hours and my older employer straight up told me, "We cannot match your new hourly rate, but here is still a raise. Feel free to work on things for us whenever you want, whenever you have time, remotely."
I'm nothing special, an average developer. But businesses cannot find enough Salesforce developers, so some take what they can get, even if it's part-time.
Focus on getting certified to really stand out.
It took me 4 years working full time to get to the point I’m at now. But I also worked Uber, Postmates, and fast food jobs to support my family at night till I got side gig developer work. In my 3rd year things really started to take off. I now have 8 certifications.
Cert tests are only $200-400 a piece to take.
I've also worked part time contract gigs while working full time on software. It gets to be a lot pretty quickly.
I've come to think the impact on my quality of life isn't worth it. I'm so sleep deprived and the monetary rewards have never felt that great - especially now since I'm paid less than I have been in almost ten years. I think I'd feel a little differently if my son wasn't such a schedule mangler or I was earning what I'm used to, but... I'm fairly firmly in the camp now that my time is worth more than anything I can manage to get paid after a certain point.
Something worth considering is intermittently taking on smaller but lucrative contracts. Be selective. Don't commit to a long term slog in which you'll sacrifice your personal life and appreciation for your career.
It helped a lot that the company I work for started a technical content agency as a new division of the company and was okay with me doing extra paid work for them outside of normal work hours.
If you're a developer who is also a decent writer, maybe something like this would work for you?
I actually found technical writing to be a nice change of pace from my day job. If I'd tried to do extra paid software work on the side I think I'd have felt burned out rather quickly.
If you want to know more about getting into technical writing, my email address is in my profile.
Most of what I've done has been for clients that want to document how to accomplish something specific with a company's library or API. Usually this ends up being 1200-1500 words including detailed instructions and code samples.
A few weren't product specific, but instead about how to accomplish a specific task with React or Angular. Companies pay for articles like these because they hope to attract customers by providing useful information to developers. I think that's a fair trade, as long as the article is actually good and teaches something new to the people who read it. Personally, if I've read a good article or blog post I don't mind if the company mentions their own products at the end. It's not like they're forcing me to but anything. :)
I've done one whitepaper as well, though I'm not sure that qualifies as 'technical writing'. More like writing a high level topic that is about a technical subject, but aimed at managers and executives who are thinking of adopting that product or technology.
That’s interesting. I had always thought of TW as manuals and documentation. It never occurred to me that it could be “marketing”. At my job we’ve payed people to write articles for Trade journals That relate to our products. But I never thought of it as TW. Now that you mention it, it think it obviously does.
How do you find these gigs? What’s the going rate for 1200 words?
* Write external API documentation/guides.
* Clean up internal API docs written by devs to make them actually readable (without messing up the logic/examples/etc).
* Help with whitepapers (usually with the dev/ops/etc teams).
it was beneficial for them because i was able to offboard and knowledge transfer much more effectively over a few months of part-time work as opposed to the standard 2 weeks notice.
it was beneficial for me because right out of the gate i had a consulting contract with a yc startup at a rate that was slightly higher than my yearly salary which i could use as social proof when reaching out to new clients and negotiating rates.
i ended up consulting for about a year as my only source of income where i took on a couple other clients through my network (ex-coworkers starting companies and needing help faster than they could hire, ex-coworkers referring me to others who were stating companies) and a few lucky connections through upwork (he contacted me on linkedin so upwork never got a cut of the invoices i sent). i've also tried toptal and moonlight but no contracts have come out of those platforms.
a year ago i took on a new full time job and i've been consulting on the side since. i agree with ananonymoususer in that i can have as much extra work as i can handle however i was lucky to have already created relationships with clients before getting a full time job. i'd imagine approaching a new client while maintaining a full time job is a harder sell than simply letting an existing client know that your availability will be reduced moving forward.
I moved on to a company that was paying me a lot and i couldnt say no. Instead of 2 week notice i offered my former employer this option.
I fully disclosed to my prospective employer this relationship. I even carved out a clause that lets me leave the office once per month to be working elsewhere.
I also converted a job recruiting attempt into a contractual arrangement.
I dont have more time for anything anymore.
A few tips.
Former employers are a balancing act. If you were working full time for them, and doing good work, that is effectively their expectation. It will be hard to change it. Learn to manage it. Make sure the contract specifically states what you will do and what you wont.
Make sure you clearly state who you will be reporting too. Contracts can go sideways quickly if your expertise is no longer trusted by way of new hire with something to prove. This is mostly true for new contracting engagements. Former employers know your depth of expertise, new guys do not.
Don't take additional problems at your new FT employer until you know you can manage all the work across all co's.
Particularly, be choosy with your clients. Do not take startups for cheap unless there is significant upside. Your time is valuable and it should be paid well. Taking a job below market rate for your experience is a quick way to utterly destroy your motivation in doing a good job. Unless you are bored, the project is interesting, or unemployed.... Do not do it.
I am not a developer. I cant even write SQL. I work in a rather mundane field. However i am an expert in scaling that field with a good tech stack, and I can speak semi intelligently about tech infrastructure. I can even read a SQL query and immediately understand what it is doing.
Is it all a local network of people that you've worked with or have you gone out and found clients?
To counter this, my experiment at the moment is in freelancing at moonlight, but where the client is non-technical and so getting a non-tech to non-tech referral means the client couldn't whiteboard me* if they wanted to, no more than I can white board my dentist. They will base their decision on the trust of the referral, and the fact they can try me out first / easily fire me anyway.
My question to you, is what sort of companies let you skip the hoop jumps? Would Google / Netflix etc allow this, or are they too standardized? I can see a startup allowing this or even needing it as an early employee is much more than just an algo remembering machine. What about a medium size co?
* I just noticed how similar "whiteboarding" and "waterboarding" sound. :-/
Hard question as I did not apply to many, but the largest offer I had was a company with some 150k+ people and I could just go in and start. I knew the CTO from a project in another company (he was the CTO there and we were contractors); the project failed but we kept in touch. I find (my prejudice) that kind of scale very much not interesting to work for; I like companies < 500 people.
For Google/Netflix(/Facebook/...) I definitely cannot answer as I never wanted to work for those companies and my network is local so I am nothing to them. In working for a very-large-company I think I would only consider microsoft research as I really love what they are doing  (and would work there almost for free), but like said, my network is far more local.
Embedded development is also pretty much in demand, more so if you have FPGA skills as well.
As with most things different skills give you different places where you might hunt for piece work.
Don't do contracting on the side if you work for any of the big tech companies. They will find out and they will fire you for it, whether that is legal or not.
Extremely so. Demand is vastly outpacing supply for engineers in this growing sector.
At this point, I'm looking to switch from hourly to project-based pricing -- I'm finally efficient enough to charge by value; there are only so many billable hours in a day.
Life got a lot easier after I figured this out :-)
I'm lucky in that I've been a career generalist and my personal network includes business owners. A lot of small to mid-sized business owners really want a second opinion on whatever the heck it is their full-time IT person is telling them. If you are already serving as that second opinion, its not inappropriate to so "hey, I'm happy to help out here, but I could be a lot more available on this sort of stuff in a formal consulting relationship." If they are interested, you can pursue it, if not, you've established some boundaries.
I’d be cautious about the idea of having it be a “secondary source of income” or anything - that’s not feasible with a full-time role - but for my part I use the money to pay for hardware upgrades or similar. It’s important not to over-work though; I’d be skeptical of doing any more than maybe the 120 or so hours I do in a year.
It's a lot of work, sometimes OK and sometimes very stressful.