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.
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.
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.
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.
Feature request: Allow me to filter by technologies that a company doesn't use.
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%.
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.
This helps sort it out.
148 technologies in their stack, practically guaranteed to match every search. This tool will need some moderation to be of any use to developers.
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.
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.
Glad to see our idea had some validity!
Link for those curious: https://github.com/kshvmdn/find-me-a-job.
- 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.
