Earlier quoted context omitted.
How? This is what I never understood. Every domain expert I’ve ever knowing is because they’ve already I can spend all the time I have reading and toying around in a subject, but until I have real concrete experience to guide me, it’s usually pretty difficult to become an “expert” in anything. I know how to become an advanced hobbyist, but thats never in my life translated to someone being willing to pay me over say,…
If you're a dev, one approach to specialization is to align with the tooling associated with common "profit center" processes. Become a Salesforce/Hubspot/Odoo/Shopify developer. If you're not interested in developing, you can specialize in learning one specific ecosystem really well and then teach companies -- typically SMBs -- how to set themselves up and organize their operations around it.
Ask HN: How did you land your first projects as a solo engineer/consultant?
121–130 of 165 posts
Re: Ask HN: How did you land your first projects as a solo engineer/consultant?
#1223 quick (and true) stories that helped me when I was in a similar situation (started my own thing in 2024). Currently have 6 clients and 9 employees (which wasn’t the plan!) 1. Embrace the bizarre. You need your first client, not a repeatable go to market motion. Once you have a client, you can begin to work on getting clients and figuring out what type of work you want to do longer-term. My first client was a friend…
Re: Ask HN: How did you land your first projects as a solo engineer/consultant?
#123Re: Ask HN: How did you land your first projects as a solo engineer/consultant?
#124General consultancy is an extremely crowded space. As a startup CEO, I get at least 3 emails per week from software agencies and consultants. On top of that, they're usually located in India/Ukraine and the rates they offer are very low, so I assume it's very difficult to compete. My advice would be to differentiate yourself: - Become an expert in 1 thing, and one thing only: either start an open source project, or b…
Or one vertical, or space. IE: you act as a CTO for companies that are in manufacturing but are a liiitle to small to hire someone.
Re: Ask HN: How did you land your first projects as a solo engineer/consultant?
#125You will become tool agnostic. you will see to the end. you will find tools to do it.
So a good way to go independent is to go into a consultancy based business - you will get a feel for AR, AP, contracts and so forth in a way that you won't really often see at a service provider, ISP, software company or SaaS tech company.
Re: Ask HN: How did you land your first projects as a solo engineer/consultant?
#126General consultancy is an extremely crowded space. As a startup CEO, I get at least 3 emails per week from software agencies and consultants. On top of that, they're usually located in India/Ukraine and the rates they offer are very low, so I assume it's very difficult to compete. My advice would be to differentiate yourself: - Become an expert in 1 thing, and one thing only: either start an open source project, or b…
> Become an expert in 1 thing Any suggestions to what that could be? I'm a backend developer looking to specialize in something with a clear demand. Top-of-the-head ideas are things like: Kubernetes, Postgres, Caddy, Self-hosting, Go or Google Cloud Obviously, one has to try to gauge the demand before spending too much time on it
Re: Ask HN: How did you land your first projects as a solo engineer/consultant?
#127Earlier quoted context omitted.
How? This is what I never understood. Every domain expert I’ve ever knowing is because they’ve already I can spend all the time I have reading and toying around in a subject, but until I have real concrete experience to guide me, it’s usually pretty difficult to become an “expert” in anything. I know how to become an advanced hobbyist, but thats never in my life translated to someone being willing to pay me over say,…
If you're a dev, one approach to specialization is to align with the tooling associated with common "profit center" processes. Become a Salesforce/Hubspot/Odoo/Shopify developer. If you're not interested in developing, you can specialize in learning one specific ecosystem really well and then teach companies -- typically SMBs -- how to set themselves up and organize their operations around it.
Re: Ask HN: How did you land your first projects as a solo engineer/consultant?
#128I was hanging out on a slack community of developers where I would commonly respond to questions and chat on the channel for Python. Someone there had a friend with AWS costs flying through the roof and he needed some help from somebody who could understand python. My action on that channel caused him to reach out to me. Once I solved their issue, they asked me if I could add features to the site. I turned them down…
Re: Ask HN: How did you land your first projects as a solo engineer/consultant?
#129General consultancy is an extremely crowded space. As a startup CEO, I get at least 3 emails per week from software agencies and consultants. On top of that, they're usually located in India/Ukraine and the rates they offer are very low, so I assume it's very difficult to compete. My advice would be to differentiate yourself: - Become an expert in 1 thing, and one thing only: either start an open source project, or b…
> Become an expert in 1 thing Any suggestions to what that could be? I'm a backend developer looking to specialize in something with a clear demand. Top-of-the-head ideas are things like: Kubernetes, Postgres, Caddy, Self-hosting, Go or Google Cloud Obviously, one has to try to gauge the demand before spending too much time on it
I'm a web developer / designer-lite (amongst other things in previous lives), and have embedded myself as the web-tech guy for an embedded / hardware team. I help provide better customer facing interfaces (through websites, apps, etc) to both end users and manufacturer that the company uses.
I've made small, simple tools that can be packaged up along in a device's flash (it's ~2KB), that allows a user to interrogate the device via serial, capture all the commands + responses, & trivially email them to an engineer. It's designed for troubleshooting devices remote, without needing to ship JLink's or debuggers or what not to clients. It's a very small thing, but it's cool to hear people using it to help troubleshoot with users, in a way that's much simpler than trying to jump on the phone with them & guess what they're seeing on their screen.
I also specifically help make manufacturing test systems which sit closer to a web-app like experience (in terms of usability and visuals), because I've observed that providing end-of-line manufacturing staff with poorly cludged together test systems leads to a bunch of errors which don't need to exist (they're often just quickly thrown together CLIs, which are unpleasant to use and buggy all round - especially for less tech savvy manufacturing staff).
I also happen to really like embedded engineers, they're fun to hang around with - and I get genuine satisfaction out of being able to help them out in areas they haven't specialised in.