[Nihilartikel]

If you appreciate wearing a lot of hats and roving around to create real value, it might be worthwhile to look into going independant!

I'm ex faang and have managed to carve out a comfortable independant consultancy where I can kind of join needful organizations as a roving 'fix-it-up' engineer at large, answering to the directors who (hopefully) only care about things working better.

It's gratifying to swoop in and fix real problems for teams, and also get a view on cross team efficiency opportunities that most siloed org-structures don't have good visibility or agency to tackle.

[Backslasher]

I tried doing that, but couldn't land a starting gig with reasonable pay. To my impression, the market is flooded with cheap-to-hire people and I couldn't make my quality stand out enough to get interesting clients. If you have any tips I'd be happy to read them either here or at cv AT backslasher.net

EDIT saw your reply. That's a great experience! I tried that but the timing / friends / luck didn't pan out there. I'm happy you got it working though :)

[sgillen]

How did you manage to do this? This is a goal of mine. I’m curious how the pay and stress compares to faang, and what your niche is.

[SOLAR_FIELDS]

I started down this path before deciding it wasn’t for me. The path I found was to get hired on as a sub consultant to a software consulting firm which gave me the time and legal freedom to pursue other work on the side

[sul4bh]

Not op but, do you have any suggestion on how to go independent? How do I get my first business? What kind of companies can I reach out to?

[Nihilartikel]

Replying here, but also to the other response: I don't really have a formula (and if I did, I best be trying to sell it!) but for my case, it came down to letting friends and colleagues know that I'm open for work, and settling in to work on an interruptable bootstrapping project. The bootstrapped work has never come to fruition though it has been useful and may still become viable IP. But by word of mouth I came into working for a MedTech organization that needed a sizeable data normalization and analysis pipeline built. This could have been full time W2 work, but by that point (and after more than one burn-out) I had made up my mind that I was more of an 'outside cat' engineer that comes and goes as they please, and I asserted that I would work on a 1099 basis. This may or may not have been wise, but it did set the groundwork for being independent. It also introduces a subtle but impactful change in one's relationship to the organization that they are working for.

Case in point, about a year into the MedTech work, I was contacted by someone I knew at a large local cyber-charter school who was looking to build out a SWE team (as leverage with the other contractors they were working with). If I were a full time employee, the answer would have been 'Sorry, I'm busy'. But, as a 1099 worker with no set hours, I was happy to help them do interviewing to build out a core team. This lead to a long term advisory relationship with them, firefighting when things exploded, and also building a ton of automation and data governance back office utilities.

There have been some other tasks too, but if I had to boil it down to a few pithy points it would be to: play HARD to your strengths and be flexible.. But also don't be afraid to turn down work if you don't think you can hit it out of the park. Let everyone know that you're open for business too. A lot of organizations would be happy to have a problem solved without having the overhead of onboarding an employee.

This is predicated on you cultivating the level of experience and autonomy needed to get things done without oversight, or, in-fact, providing oversight of others trying to do 'the thing'.

My current challenge is in trying to move away from hourly billing and on to project-scoped contracts. Eventually I would like to build productized services and IP that make money while I'm asleep.. but who doesn't?