Context and intros

• Student platform to connect cse students with job openings https://jobsboard.csesoc.unsw.edu.au/

• Recently released v2 last year and should be a perfect time to use it now due to internships opening soon.

• What was the collab like last year?

  • Main issue was on verifying companies/jobs?

  • Careers did use much as busy with other responsibilities

Sponsors vs Companies

• Should jobsboard be only used for sponsored companies or should any company be able to post job openings.

  • possible differentiate sponsors vs other companies if we want to open it up for other companies to post?

  • Final decision: NO not right now → Part of sponsorship package to promote jobs.

• If we open to sponsors, we dont need to verify jobs post. For non sponsored company (if we decided to open it up to them), should manually verify.

• stick to promoting for sponsors

  • too busy to handle manual verification for non sponpored companies

  • emphasis sponsored posts

  • careers only promote sponsor events

• Idea: If we do open up for non sponsors:

  • have an entrace fee to use jobsboard without being a sponsor

  • empahsis sponsored job posts first before non sponsors

• more leaning to use sponsors as its fair because they are paying a sponsorship package to promote their events to cse students → unfair to sponsored companies if non sponsored companies can use it

Verification

• Workload for careers

  • pretty tricky to manage verification process and check emails to manage process.

• Workload for jobsboard

  • we arent too knowledgable to handle with careers stuff

• Job postings and company accounts needs to be verified by an admin.

• How should the verification system be handled?

  • Right now, each company has to be manually verified before posting a job. We thought of adding a verification code model where we automate approving companies if they entered a correct code.

    • Pros

      • remove human aspect

      • speed up verification process and time

    • Cons

      • code could be leaked and abused?

      • jop postings not inspected manually so some openings could be sus - job has to comply with the fair work law so someone has to go through the post to make sure it’s paid

      • need to be develop (should be quick tho)

• Workload for careers: idea is to get execs involved in this (i.e. secretary or other execs as they have a lighter workload?), delegate to execs to manage jobsboard?

• all job posts should be manually approved, only for sponsored companies can post

• verification code idea:

  • we both agree

  • mass email codes to sponsors, no need to verify the company

    • at that point, job openings can be briefly skimmed by subcom

    • maybe randomly generated codes for each email

      • each code one time use and asisgned for a specific

  • sponsor reply game bad, so a month for the code to be valid before it expiers?

• entrance fee for non sponsored company to be discussed later, for now keep it SPONSORED!!

Pipeline for posting jobs and verification

• What would be the pipeline to post jobs on Jobsboard?

  • before every term, remind sponsors to sign up for jobsboard

  • when they create a post, verify the job post

Responsiblities

• What responsibilities does careers want to handle?

  • promotion

  • verifying companies + job postings?

• What responsibilities does jobsboard want to handle?

  • dev work on adding new features + improvmenets

  • verification code system

• careers can promote to sponsors via email

  • send them verification codes via gmass through google sheets/excel

  • wait for jobsboard to build

    • promote on facebook and linkedin in the meantime

    • early t1 (max deadline week 5)

• careers directors and subcom can handle verifying job posts

  • could delegate to execs

• some vp from dev promote jobsboard on csesoc page (not unsw, gatekeep )