You say it searches the latest jobs advertised on Twitter, but you also advertise job postings for $149. Why wouldn't someone just post their job on Twitter if your service is going to pick it up anyway?
"That is pretty visible, a lot more qualified people than me are going to apply."
Granted I'm a bit of an noob due to a career change so that probabbly applies to me anyway, but I wonder if other folks respond the same way to seeing heavily promoted jobs?
I know of some places I interviewed at who endlessly advertise... because a lot of people have turned down their intermittently (strangely random) low ball offers or worked for them and word on how their management structure has gotten out.
Again, purely anecdotal, but the quality has usually been pretty high - probably because the candidates were always "known" to the company, either by knowing them from a user group, or being friends/associated with someone at the company.
Seems like a good way to miss out on potential talent.
> Search Engine on the top of twitter to find jobs in real time.
Should generally be written as:
> Search Engine on top of twitter to find jobs in real time.
A website like this is great to make finding those positions even faster.
I tell my story of how a single tweet landed me a $10K fully remote front-end freelance gig here: [REDACTED]
P.S. - If you're interested in learning how to find remote freelance positions yourself on Twitter then I have a free PDF for you that shows you how to find them, structure your profile, etc. Get it here: [Medium.com Link: https://hackernoon.com/how-to-find-your-next-remote-freelanc... ]
Hope it helps and thank you for releasing tweetjobs, OP.
EDIT: Removed first link to my website and linking up to Medium.com post instead of a PDF file. Sorry if this came across as clickbait...
This feels like spam.
Twitter could probably make a tidy sum providing such a service themselves. In a way, it's a bit weird that they haven't. Or, it's a sound strategy to stay focused on the main service, who knows.
As always with projects which use data from Twitter to build something valuable, I wonder if you could share some insights into how your Twitter-to-Website ETL pipeline looks like?
Same here, appears to be another case of HN hug of death.
Now, website is working fine.