Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

as an open-source developer, i can confirm this is a real phenomena

best gigs i’ve got are because of relevant contributions and from companies depending on my software

if you have a strong open-source profile, many companies will skip the screener and invite you straight to interview (i believe this is called “red carpet treatment”)

public work makes you trustworthy and you will stand out among other candidates




Edit: I meant something more more like, "What would you say makes an OSS profile strong?", but I'll preserve the original question below so that the responses still make sense. :)

---

Where would you say a strong OSS profile begins? (Feel free to give a fuzzy low-stakes answer. Haven't experienced this but curious where the ballpark is.)


(Author here)

The path I took was to write libraries for a large ecosystem (Laravel) to solve gnarly problems I was having. The gnarlier the better. Pick the thing that nobody else wants to do and solve it. That's what I did, no guarantees that'll work for anyone else though!


i’d say with exposure!

most of the exposure you’ll be getting is from organic search

you might not realize, but people are literally searching for solutions all the time

companies also search for projects they want to build/use to see who’s already building it (this is where you can get hired)

so, a good idea would be to work on your README so when your prospects describe the problem to the search engine your project comes up as a solution

then make sure the technical side and the documentation are solid, so that people can depend on it

a plus for you would be to have projects across multiple domains, this increases your exposure

if you want to go a step beyond that, try to post your projects to relevant communities (note: this should come secondary after search)


Thanks--this gives me a good sense, I think.

My emphasis was probably a little off. You might be answering something like "if my goal is a strong profile, where should I start?" I was a little more curious about "where do you think ~strong begins?"

In any case, "people depend on it" and "projects across multiple domains" both seem like good-enough answers to the latter question.


Finding and reporting bugs in software you use is a good start.

Better yet is fixing those bugs and opening pull requests.

Or just mining the bugtracker to fix bugs other users encountered.

Its a solid place to start - getting known as a useful contributor to a handful of projects can work wonders.




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: