A neat followup might be to take the job-search data and then put together a list of which technologies have the highest developer interest. This could be quite useful for companies or projects trying to decide on a tech-stack or tooling.
Even better would be to compare supply vs. demand and come up with a ranking of tech combinations that people want to work with but few companies are using. For example, Rust + Postgres gives one result that's actually hiring. That one company could conceivably get quite a boost to their hiring efforts if there are many developers that want to work with Rust + Postgres, and other companies that pick that tech company would also get a similar boost until it gets oversaturated.
Interesting way to search for jobs. I feel a bit weird though in that I'm drawn to jobs more based on the business domain and problems being solved than the particular technology used for the implementation. Getting asked 'what is your stack' always felt like a weird lead in vs. what problems you are solving day to day, but I feel mostly alone in this sentiment...
There is no reason to feel alone, perhaps rare, but not alone. There are others that share your feelings (including myself).
These people are often labelled as the "pragmatic". They also lean towards having a more general scope of knowledge and thus often lack a "speciality".
There are also those that simply wish to solve the problem in the "best" way possible, and will use whichever stack gets them closer to that ideal solution.
disclaimer: purely based on my experience/opinion/perspective.
I think it has merit for devs looking to get involved in a particular tech (whatever their reasons may be).
In the past I work almost exclusively within the .NET ecosystem (only some small projects in Java, Python, etc.). When I took up learning Scala, I decided that I want to immerse myself in full-time Scala development and started to look for Scala-related roles.
I can absolutely understand and I feel the same way. I can't understand this infatuation with stacks. They're just a tool for solving a problem. If another tool is better for solving a particular problem then you should use that. It's nothing to be obsessed with.
If you present yourself as just a bunch of TLAs you're effectively selling yourself short. Put bluntly, if you do that you're presenting yourself as a code monkey who turns other people's ideas and solutions into that nasty computer code the people who do the "real thinking" can't be bothered to deal with.
Besides, your favourite stack today might fall out of favour tomorrow. If you invested a disproportionate amount of time into learning all the intricacies of that particular stack you might have wasted a lot of time.
Being able to analyze and solve problems regardless of the toolset is a skill that likely will never fall out of favour.
But the job ads and interviews I've seen and been to are all heavily about the stack and very little about other qualities. E.g. changing language is considered making me junior from senior and halving my salary. Only exception would be a newer tech e.g. GO where perhaps getting experienced people is tough.
> as long as I don't have to work with something terribly archaic
Totally! I definitely wouldn't want to work in something like, say, Pascal, but my all time favorite job was at a startup using Java, of all languages.
Searching for F# seems to return all .NET-using companies, even if they're explicitly listing only C# or only VB.NET in their page.
Perhaps you could add a "search related tools" flag? I can imagine an experienced Java developer being OK with Kotlin and Scala jobs, but maybe a Scala fan wants to look specifically for Scala postings and avoid the majority of general JVM positions.
But in any case, sort by match % by default! I had to scroll quite a bit down to find the first actually-F# result, even though it was (correctly) matched as a 100% match and all the ones above were at 0%.
Good idea! Related searches makes a lot of sense. We'll look into that. And sorting by % should already be happening, but it's clearly not. We'll fix it.
Nice! This is a really interesting way to approach a job search.
I recall a few times in my career when I didn't like the technology choices being made at my current employer, which prompted me to look for new opportunities with the tools I did want to use.
There are a ton more things to consider about a new job, but the tools you will be asked to work with every day are certainly a factor.
I definitely recommend using HTTPS on this site. I would rather not have all of my calls logged on a company server somewhere (especially if someone works at a company that cares about this sort of thing)
Well done with room for improvement. Please add a remote/onsite switch. Other useful switches would be full time/part time and employee /freelancer. I'd go for remote, part time, freelancer so I won't use a service that makes me skim through hundreds of job listings before finding the one I want to see.
That count is actually inaccurate. They've added a ton of tools to be approved that are not visible (or searchable in that interface) but are included in the count. We'll fix that. It's rare that a company lists things they don't use; it's not very helpful for them.
When I filter location to Berlin, it shows three different Berlins in the US - but after selecting the first the results appear to be in Germany (what I was looking for).
Yeah, we noticed that too :( Still working on a fix. We're using Places (https://github.com/algolia/places) and haven't yet found a great way to improve relevance for our use case.
A few weeks ago at Hack the North (UWaterloo), a few friends and I built exactly this.
We literally aggregated all of our company data from StackShare, only difference was that we parsed their resumes for the preferred languages/technologies instead of having them manually enter it.
- Being able to sort my stack would be nice. I put up my company and noticed that random small libraries I added dominated the first few positions instead of the bigger elements.
- The scrollbars (or iframe?) and typeaheads can be pretty slow on mobile.
- The scrollbars (or iframe?) end up with a lot of unnecessary whitespace and may be difficult to navigate.
Even better would be to compare supply vs. demand and come up with a ranking of tech combinations that people want to work with but few companies are using. For example, Rust + Postgres gives one result that's actually hiring. That one company could conceivably get quite a boost to their hiring efforts if there are many developers that want to work with Rust + Postgres, and other companies that pick that tech company would also get a similar boost until it gets oversaturated.