It's specifically aimed at helping people find their very first dev job (mainly for people who are trying to transition into tech). Right now there are three parts that help with different aspects of the process:
- jobs: jobs for junior positions(through AngelList, HN etc.)
- posts: knowledge in the form of articles. (from learning to code to interview prep)
- stories: interviews of people who have successfully made the career switch to development
If you are a developer who is looking for his first(or maybe 2nd?) developer job, I would love to have your feedback!
Also, it would be nice to see a little bit of information underneath the posting before you view the full ad: maybe show the "skills" section from AngelList?
Again, thanks! I already applied to FormSwift through your site.
Both your points make sense. Reg distance slider - do you think option to input state can be an alternative? Would that work for you?
I feel like you would have to ask yourself how most people use these features: perhaps someone is searching for the city they live in and are willing to commute "30 miles." They certainly wouldn't want to search the entire state of Texas. Is that the major use-case for users of your site? Forgive me if I'm using an incorrect logic here as I have never done user interface testing but this seems like the sort of thing to think about when designing features.
Honestly though I love the simplicity in design of your site, but the way your job-tile elements are created they're just begging to be clicked on to expand them for more detail.
EDIT: Also as a suggestion, it would be cool to filter by full-time/part-time/contract if possible
Edit: Appears to be working correctly now.
It's really annoying when the title says junior and then description asks for few years experience. We are working hard to prevent such cases.
'If you are a developer who is looking for your first(or maybe 2nd?) developer job, I would love to have your feedback!'
No need for gendered pronouns in a general description.
* I add ONSITE because I used to get asked every time whether remote was supported.
Previously: https://news.ycombinator.com/item?id=13302035
(Edited to reflect what I wrote previously, I hadn't checked)
(It shows 59 jobs in PA, most of which seem to be NYC jobs.)
Maybe I'm cynical, but I've been hesitant to post there with reservations about poor-quality leads and spending time dealing with them.
For now you can keep salary in the first line in {attrs} section for, or somewhere below the first line.
What kind of the format you would like to see for salaries?
location | [xxx to yyy]
location | [US$xxx to yyy]
Best to disable the map when REMOTE is checked.
1. Check 'remote', and I get a single job (Automation dev, Dublin, Ireland)
2. Uncheck 'remote', zoom right out 75 jobs off the coasts of Ghana & Gabon, all listed as remote.
https://en.wikipedia.org/wiki/Null_Island
I've decided to leave them there. Since I can't figure where to put them on the map, the address in most of them is "remote".
I will see what I can do about it.
https://whoishiring.io
or just HN items
https://whoishiring.io/search/36.0440/-90.8984/4?source=hn
If you post here, please use the below format to help me with parsing. If you won’t, no worries, I will do my best to get all the things right.
or I’m using this regex to test the firstline. You can test it in Python or here https://regex101.com/r/relwQD/3 (for the match look right).