We have postings for pretty much all product teams. I'm a manager on our Data Integrations team. We take loosely structured data from APIs, flat-files, or whatever our customers can give to us... and bring it into a useable format. We're working on this problem for our 7000+ customers, so we have lots of fun problems to work.
We take data from customers, in whatever shape they give it to us... and get it into our products. It's a fun UX, Scale, and ML problem. We're hiring at all levels.
PayScale helps individuals figure out how much they should be paid, and helps companies set pay for their employees. 100's of millions of individuals have come to use for help over the last decade.
Our team is focused on getting data from the customer into our products, with little-to-no friction. We also work on sharing data between our products.
PayScale believes that fact-based and transparent relationships between employers and employees leads to better results for both. We believe this for our products, and we believe this for ourselves.
Why do we believe this? We researched the topic, extensively.
> We discovered that transparent conversations about money can actually mitigate low pay. So, if an employer pays lower than the market average for a position, but communicates clearly about the reasons for the smaller paycheck, 82% of employees we surveyed still felt satisfied with their work.
It can do something as simple as a site: search on Google, but you can string configs together to join up 20-30 sites together, create tabs to split out by sentiment, split out by number or dollar ranges, etc. etc. I have barely scratched the surface with the Blades there now, hoping to see some creative ones surface.
Well, yes, if you don't mind typing or pasting the same combo of 20-30 different search operators in Google.com, it can be done there.
But there are some other subtle differences: you get thumbnail images with search results (if available) with Blades, and you don't get a captcha to prove you're human if your search volume or rate is out of bounds on a Blade. (These are features of CSEs, not something I've hacked.)
I'd love to talk more details with you sometime! We(PayScale) don't scrape linkedin, but we have been collecting, analyzing and predicting pay for over a decade.
PayScale believes that transparent, fact-based relationships yield better results for employees and employers.
All jobs are here: https://www.payscale.com/about/jobs
We have postings for pretty much all product teams. I'm a manager on our Data Integrations team. We take loosely structured data from APIs, flat-files, or whatever our customers can give to us... and bring it into a useable format. We're working on this problem for our 7000+ customers, so we have lots of fun problems to work.
Here is a link to that job: https://www.smartrecruiters.com/PayScale/743999678090468-Sof...
-- Adam