re: filters -- These are probably obvious, but just in case: a) location, b) remote/in person/combo, c) seniority level (junior, intermediate, senior), d) tech stack
Thanks, yeah. They may be "obvious" but always helpful to get basic feedback on even the little things. I'd hate for everyone to think something's obvious and then nobody ever brings it up.
We're definitely not trying to completely reinvent the wheel, as we think our value to each side lies in the subtle benefits of being a platform, and we're going to try to be helpful in the little ways.
I think a definite benefit is the fact that if someone applies through here, hiring managers can easily check out the candidate's posts and that gives a nice fuller picture of the person's interests, etc. Love that you're building out this feature!
Yeah. A lot of the motivation comes through experience. I've been looking to hire people and if you're unsure about someone, you're going to look into them on the Internet, and it is always a major plus if they are engaging in code in a way that shows they care. I'm not sure whether it's a perfect indicator, but it's a part of the process no matter what. We think your dev.to profile and activity is going to be a better representation of the important qualities than a lot of other online representations.
Companies also see a major benefit in the fact that everyone on the platform has self-selected to be early adopters in a community that seriously geeks out over software development and also holds values around inclusiveness and constructive dialogue. In talking to companies, this is always a major plus.
I've been seriously geeking out over this site since I discovered it. It's great to be part of a community of fellow code geeks, but even more importantly, a place where I felt confident to contribute. Not easy to create a space that is in one breath both rigorous and welcoming.
Couldn't agree more with Ben. This has been a ridiculously welcoming and approachable community. It will be interesting to see what happens in the future as some features may bring in the typical crowds I've walked away from. Prime example is the lifecycle of a question on stack overflow which typically results in arguments and 1 upmanship of late.
Equal parts higher-ed IT, web dev and support; with a dash of freelance consulting thrown in for good measure. (Oct/19: Seeking change of pace. Not afraid to take a step back in order to move ahead!)
With respect to "remote" postings, in particular; applicable citizenship/VISA requirements are good to know in advance.
Nothing quite so disappointing as to troll remote-friendly job sites only to find out that because I'm a Canadian citizen, I'm ineligible for many US opportunities. I suspect this boils down to the difference between contract and on-payroll/salaried hiring practices.
Thanks. We already had this general use case in mind, but if you could provide some insight into exactly where the job listings might fall off in this regard, that would be really helpful. We hadn't really thought beyond the general filtering of "sponsor's via". Any details into the issues you've run into with any different types of classifications is great.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
re: filters -- These are probably obvious, but just in case: a) location, b) remote/in person/combo, c) seniority level (junior, intermediate, senior), d) tech stack
Thanks, yeah. They may be "obvious" but always helpful to get basic feedback on even the little things. I'd hate for everyone to think something's obvious and then nobody ever brings it up.
We're definitely not trying to completely reinvent the wheel, as we think our value to each side lies in the subtle benefits of being a platform, and we're going to try to be helpful in the little ways.
I think a definite benefit is the fact that if someone applies through here, hiring managers can easily check out the candidate's posts and that gives a nice fuller picture of the person's interests, etc. Love that you're building out this feature!
Yeah. A lot of the motivation comes through experience. I've been looking to hire people and if you're unsure about someone, you're going to look into them on the Internet, and it is always a major plus if they are engaging in code in a way that shows they care. I'm not sure whether it's a perfect indicator, but it's a part of the process no matter what. We think your dev.to profile and activity is going to be a better representation of the important qualities than a lot of other online representations.
Companies also see a major benefit in the fact that everyone on the platform has self-selected to be early adopters in a community that seriously geeks out over software development and also holds values around inclusiveness and constructive dialogue. In talking to companies, this is always a major plus.
I've been seriously geeking out over this site since I discovered it. It's great to be part of a community of fellow code geeks, but even more importantly, a place where I felt confident to contribute. Not easy to create a space that is in one breath both rigorous and welcoming.
Thanks so much. That's exactly the value we try really hard to hit on.
Couldn't agree more with Ben. This has been a ridiculously welcoming and approachable community. It will be interesting to see what happens in the future as some features may bring in the typical crowds I've walked away from. Prime example is the lifecycle of a question on stack overflow which typically results in arguments and 1 upmanship of late.
With respect to "remote" postings, in particular; applicable citizenship/VISA requirements are good to know in advance.
Nothing quite so disappointing as to troll remote-friendly job sites only to find out that because I'm a Canadian citizen, I'm ineligible for many US opportunities. I suspect this boils down to the difference between contract and on-payroll/salaried hiring practices.
Thanks. We already had this general use case in mind, but if you could provide some insight into exactly where the job listings might fall off in this regard, that would be really helpful. We hadn't really thought beyond the general filtering of "sponsor's via". Any details into the issues you've run into with any different types of classifications is great.