Feature: Job Posts

[chtzvt]

Personas

As a Business, I want to post a job opening so that I can hire a new employee.

As a Developer, I want to see a list of job openings so that I can apply for a job.

Platform Outcomes

Engagement:

• Facilitate easier discovery of job opportunities for Developers
• Facilitating easier sourcing of candidates by Businesses. Currently, Business customers must sift through the database of developer profiles in order to locate candidates they feel are a good match.

Growth:

• Increase the number of user registrations by displaying job openings to unauthenticated users
• Increase the number of successful job placements by enabling Businesses and Developers to engage through a new channel.

Visual Design

UI mockups are being tracked in Figma here.

I would also recommend reviewing our past work in this area for visual inspiration, as well.

Acceptance Criteria

Platform Features

• A new entry in the navigation bar is created for the job posting feature
  • Depending on the role of the user (Developer or Business) the page displayed allows them to view open roles or manage the roles they’ve posted. Note that a User may be a Developer, Business, or both.
• Developer interest in job posts should be counted towards the platform-wide response rate.
• Job posts are automatically archived after 90 days.
• Job posts are included in the sitemap and submitted to Google for indexation via their Job search API.
• Job posts emit a Segment analytics event upon creation, upon developer [application, acceptance, rejection].
• Job posts are syndicated into the Tampa Devs Slack (via Segment).

Business Features

• A Business can create a job posting
• Businesses are limited in the number of posts they are allowed to create based on their plan. Per the current plan, the default number is 5 active posts at a time.
• A Business can view a list of Develpers interested in their job posting
• A Business can start a conversation with an interested developer
• A Business receives an email notification when a developer indicates their interest in a job posting
• A business must provide a salary range as part of their job posting.

Developer Features

• A Developer can view a list of job postings
• A Developer can indicate their interest in a job posting
  • When a Developer indicates their interest in a listing, all that's needed is to create a message to the Business which posted that listing. Effectively, this feature enables Developers to start conversations with Businesses.
  • This also provides a facility for Developers to add some descriptive information to their message.
• A Developer can receive a weekly digest of new job postings
• A Developer can sort or filter the list of open job reqs based on various criteria, such as keywords, salary range, role type (part time, full time, contract) and location (remote, in office, etc)

Unauthenticated Features

• An unauthenticated user can view a censored list of job openings
  • E.g., rather than “Senior Frontend Developer at Foo Business”, they would see “Senior Frontend Developer”
• An unauthenticated user is directed to register if they try to apply for a job opening
  • If an unauthenticated user registers as part of this flow, they are redirected to the post after registration to continue their action.
• Information about the business and job req is redacted unless a user is logged in

[chtzvt]

We also need to integrate with https://developers.google.com/search/blog/2018/06/introducing-indexing-api-for-job.