The Remote Freelancer: A list of remote work alternatives to Upwork
github.com
github.com
Domino and TopTal look like they may be more suitable for more experienced developers.
What is everyone else's experience for finding work at the higher end of the market ($600 - $900 / day)? From my experience I know the demand is out there but currently all of my work comes via traditional recruitment agencies which seems a shame for the companies doing the hiring, since agencies charge fairly big fees.
I have in the past tried eLance, Upwork, People Per Hour, and they all seem to end up overrun with low-end work and low-end clients and whilst there may be some gems in there it ends up not being worth your time to sift through / send propsals because 95% of clients will choke if you mention your hourly rate.
https://www.wisecashhq.com/blog/how-to-have-clients-find-you....
EDIT: I've been freelancing since 2005, and 100% remote since 2010. Happy to answer questions!
I also liked the infos of Brennan Dunn, but these seem mostly related to keeping customers and appearing "professional".
I've found that giving talks and weekly writing blog posts (https://www.robustperception.io/blog/) are great for acquiring customers. Beware though it's often at least 6-9 months before any of it directly bears fruit.
For consultants working with a single client, the right moment to do that kind of marketing is right now, while you're busy with your gig.
My big question, which I'm still struggling with, is how much to specialize.
I'm one of those guys who wants to do everything. After a few years of Java development in financial companies, I now work on real-time web UIs. I'm now eyeing distributed, soft real-time systems with Elixir, and a bit of applied machine learning.
If you look at my blog, you'll see stuff on Clojure, React, and a few other things. So far, the React stuff has helped me land a client.
My question: Is this counter-productive? Should one specialize? How does one adapt when the specialization wanes and a re-branding is required?
Jump between Java, .NET and C++, backend and frontend (both native and web) depending on the project.
Also since I majored in systems programming, I tend to dabble in other languages.
On my personal experience and those on my circle of friends, some specialization is required to keep being marketable.
Switching among technology stacks inside the company is relativity easy, as it is only a matter of being available when the right project is looking for new devs.
Outside on the job market, agencies and HR departments tend to focus on the last couple of projects, so if they aren't the key technologies that are looking for, it is very hard to convince them that we also have knowledge in the specific area.
In any case, just the size of standard libraries for modern languages, make it almost impossible to know everything.
Let alone the third party tooling and most relevant libraries outside the standard.
You can remain pretty much (internally) a generalist and a tinkerer (as you are, and I am, too! but make sure not to spread yourself too thin), yet make sure to market /some/ special skills appropriately (and in very specialized/niche fashion).
You'll decide which areas to market based on how you feel the market can generate recurring revenue.
For instance, I'm a tinkerer, yet I have a couple of well-defined niches :
- in the past, "Rails maintenance work" (easy to find, and useful while my second child was still a baby)
- Ruby ETL (http://www.kiba-etl.org/) (more specialized, but very visible in my little sphere)
- "SaaS bootstrapper with experience implementing products (and their billing)"
- anything FinTech related (as in WiseCash & other projects)
- scaling your data processing (no matter the technology, Elixir, Node, Ruby, ...)
The underlying skills are all very "aligned" around products & data, yet each small niche appeals to a subset of potential clients.
Hope this helps!
One of the site's founders emailed me later to tell me that he knew that those questions didn't actually really test programming skills, and that they were trying to improve, but the damage was already done.
It also had pretty much zero overlap with actual software development (e.g. it completely ignored actual business needs, which is a big part of what devs should care about).
It's actually quite fun to do. I succeeded only one of the three within the time limit, and sent the results of the second one an hour or two later. I still got denied, but was told I could reapply in a couple of months.
The thing is, I'm earning a nice 70 euros per hour with local work. They don't advertise the rates, but I've heard and read it's 20-30% lower than that.
They'll give me another shot at it, but honestly it's not worth the effort. I discovered from the engineer that the average asking rate for the other 70+ developers in Canada is $45/hour. I'm not going to work for that - as a "top 3%" developer it's so much easier to make $65+/hour full-time, remotely. Why would I settle for sporadic work and lots of risk for less money? Do yourself a favor and steer clear of those guys if you know what's good for you.
[0] https://medium.com/@AdShadlabs/why-you-should-never-use-upwo...
1. I bid on the project and in my opening message I write that I'd love to learn more about the project/client and am available for phone/Skype call. I'm finding more and more jobs that already request a quick Skype "interview" so that's fine by me. I've never been flagged (to my knowledge) by Upwork for providing my email or Skype name in Upwork messages.
2. 9 times out of 10 I end up redefining the project scope based on my conversation w/ the client. As an action item coming out of the call, I always tell the client I'll send them a 1-pager task summary with anticipated fees and timeline via email (which takes our communication off Upwork).
3. In that 1-pager, I have a standard payment section which includes non-Upwork services like paypal, venmo, etc. At this point it's about feeling the client out. I'm not actively trying to screw Upwork, but their new pricing is just ridiculous, so I'm also not too concerned about ethics here either. I've yet to have a client get offended at the thought of completing our transaction off Upwork's platform, but I also don't push the issue if I feel hesitation.
4. Also as part of my standard payment policy is 50% payment upfront with 50% upon completion. To this day I've only been left out to dry by a client once and it was only about $650. For projects with very large fees, I'll sometimes split the final 50% up into 25% at a certain mile marker and then 25% upon completion.
I should mention that I only work with growth/marketing/content jobs, typically strategy > execution. I also put a lot of stock into my ability to suss out job owners, though I'm fully aware that instincts can bite you in your ass.
I also try to get the client to put some "skin in the game" by way of connecting me to whatever software they use that is relevant to the project (GA, intercom, etc.). This goes a little way in creating mutual trust. (That said, the one client who screwed me over STILL has me as admin on a bunch of their services.)
Based on what you've posted, you are deliberately seeking out work on their service, and deliberately trying to close the deal off their service, to avoid giving them any cut, in knowing violation of their TOS.
It's one thing to say you don't mind screwing them over, because you don't like them. But it's disingenuous at best to pretend you're not actively screwing them over.
The more you work with a platform like Upwork, the better you get at quickly labeling and filtering clients/gigs, and the better you get at finding similar jobs to successful ones you've completed. That's when project-based fees are great because you can trim hours by creating a system and/or template that reduces your project hours over time.
If you simply don't charge per hour you're filtering many clients out already.
The bigger the period is you charge on, (day, week, month etc.) the less people find you interesting, because they just want you for 5hours/2day/1week etc.
On the other hand you have to ask yourself, do you want to work with those people? If yes, charge per hour, if no, don't charge per hour :)
That way you avoid the problems of charging per project (even if that project is a feature), but avoid the commoditisation of people thinking they can just "grab you" for 3 hours of work.
If you are being paid per week and on day 3 the requirements change, well, it's not on you.
The point is as you get better, you can MORE THAN double your rate at solving problems. A junior programmer might spend a week writing a way to sort a list. A senior programmer might call Arrays.sort and be done in 30 seconds.
I am not kidding. By design that site eliminates 97% of applicants -- be it front-end or mobile development or Python or Java or Go language.
Can people who are learning still do remote freelancing?
In fact, I'd say my issues with sites like these is that most of them are exclusively for people who aren't that good.
I don't know about top 3%, but I'd say I'm in the top 25% for what I do and I have a hard as hell time finding top 25% clients.
I did the most remote freelancing at the earliest point in my career, while still learning, and given the cost sensitivity of most companies that hire freelancers, I'd say it works real well for that.
Just send the emails. You'd be surprised how crappy your competition is.
Best to add:
1. How many people are on this site?
2. Does it specialize in something?
It would be even better to have some proxy of quality (eg. 3. average hourly rate or something), but that is a lot more work.
There have been a bunch more resources mentioned here - I'm working on including them all!
If someone wants to help me go through and actually qualify each of the items - that would be amazing.
Probably needs an actual site now, a standard MD file is a little hard to read when it gets complex.
One interesting thing is that most sites target freelancers as single people. What if I have a team of coders/designers (ie. a small software house) looking for clients? That's my current problem. Maybe will start a new thread about this.
But I agree it would be nice if this was made more explicit, and even touted as a feature. In many cases I might feel more comfortable hiring a team consisting of two developers a graphic designer and a UI/UX expert as opposed to one person claiming to be an expert in all those fields.
You can read why I created it here:
https://medium.com/@laurenholliday_/10-reasons-i-created-my-...
I was a full-time consultant for a while but decided to go back being a full time employee due to a new baby in the house.
I've read some spanish-language forums and read about very different experiences - some good, some pretty bad.