#depending on what your eventual goal of

1 messages · Page 1 of 1 (latest)

dense beacon
#

Sorry I didn't answer it very directly before.

  • Money
    I can't answer well as I don't want ideas stolen, but some of this is part of a bigger SAAS plan. That said, I'm not too worried about money; if it provides something people enjoy, but I can get a high income elsewhere, I'll be happy.
  • Value
    At the moment, when learning web dev, it's hard to ascertain exactly what technologies to put energy into--this will answer that and more. The value is part of a bigger platform; I run a discord for people who graduated bootcamp (a private slack was shut down), university and people with 1+ years experience. My plans are to run meetups when I can get back to canada. For specifically the job bot, it will allow easy filtering of jobs and people can see jobs go up quickly. Some of the statistical analysis I have planned I can't talk about, but as an MVP the value add won't be super high.

It will also allow better access to freelance gigs, because people can log in and post a job; like #🚀looking-for-work and #💼paid-opportunities. The whole site will eventually integrate with discord, not just the job bot.

  • Recruiter
    From the recruiters perspective, they will get access to a demographic of motivated people (hopefully); and people who are also legally able to work. As a result, hopefully they'd face less spam. That said, it's also grabbing from an API, so it isn't totally reliant on recruiters.

The video is very bare but each thread is a company, and then they will post jobs inside that

dense beacon
#

If you have suggestions to add more value, I'm all ears too! Ignore how some of the data is laid out. I need to change a lot haha

dense beacon
spiral gazelle
#

so that first flow of using the /jobs command would be the recruiter right? Would this second flow also be recruiter or would that be a candidates side? Trying to understand who that dashboard is for

dense beacon
#

people in the server use the /jobs command, and it populates with jobs relevant to their skillset. they will then be able to filter the jobs in discord. the admin panel you see is for me, but there will be a separate thing recruiters log into, that shows the data in a better way. they'd be able to post a job, and that would automatically get sent to discord

#

you only need the command to trigger the api, it wouldn't be needed when a recruiter posts a job

spiral gazelle
#

If I'm following then there's basically two layers of filtering then it sounds like. Initially by the /jobs command and then another by these filters?

dense beacon
#

typing /jobs will essentially send a signal to the api with variables like { "location": "calgary", "experience": "senior", "type": "developer" } and that then grabs jobs. the filters in discord will allow you to filter all results

#

since there might be a junior that uses the /jobs command and there might be a senior

#

so it will fill up more and more

#

it's not exactly two layers of filtering. discord filters, the other doesn't fetch the data in the first place unless it matches that request

spiral gazelle
#

Yeah but im saying that you already specify to grab is technically filtering from the user's perspective. But from that last sentence it sounds more like the technical nuance is the difference which i assume could be cheaper on your end or some trade off like that

dense beacon
#

yeah, from the users perspective they get jobs and then those go to the top. if they want to filter all jobs

#

they'd have to click the buttons

#

i thought about having it just generate jobs every 24 hours

#

but there could potentially be a bunch of locations and maybe we only have juniors there, etc. so im gonna see how it goes

#

for now it's sort of a fun thing to add to my discord, not sweating it too much

spiral gazelle
#

Ok so it doesnt refresh, so I would have to refresh the api command everytime to grab new jobs?

#

Of course, just asking questions

dense beacon
#

yeah

#

if you want the most recent jobs you would have to

#

(excluding recruiters)

spiral gazelle
#

As a user, I would assume they would want to see the most recent jobs as those are less likely to be filled so I'd have to run the command constantly every time i want to search.

dense beacon
#

yeah unless someone recently used it

#

which is likely since the majority are in vancouver

spiral gazelle
#

when you say someone, do you mean ANYONE does the / command?

#

not just user specific?

dense beacon
#

yeah anyone in the server

#

it's like if i ran it here, it would populate in the paid-opportunities channel

#

if a recruiter posted on my site, again it would go to that channel

#

i may also open it up for people freelancing to post stuff too. i am not hugely fond of the current method where people post stuff and then it's moderated

#

i think it should be moderated before posting

spiral gazelle
#

Yeah I think thats an important problem to solve

dense beacon
#

the api is kind of just a way to populate with some data when i don't have much

#

like i made forums for example, that show on the website like the old PHP forums

#

except you can write in discord

#

but not many people msg'd so no one even knew it worked well lol

#

with the api i will get enough data to make a site and whatnot

#

how did your thing at work go?

#

things just got more busy at a startup im part of so i have to slow down with the bot too haha

spiral gazelle
#

idk what thing at work we're talking about

#

im in idgaf mode since my contract isnt being renewed ive just been working on my portfolio and talking to other designers and networking or reading blogs

dense beacon
#

ohh

#

something you had to stay up until 2:30am for

#

and your friend told you to sleep