Customer/User Job-to-be-Done or Problem

I am trying to take my company’s Job Titles and translate these to the Lightcast Occupation Taxonomy in order to provide a less granular look at the labor market using other Lightcast services like Analyst, JPA and (someday) Profiles.

Value to Customers & Users

This mapping allows a client to take the data they have (Titles in this case) and better understand the Labor Market through the lens of an Occupation vs. the oftentimes too granular Titles taxonomy. This would also enable more wide use of the mapping versus the US-focused Titles-> SOC + Skill mapping that is available today. Legacy BG Classifier API users already have this capability.

Value to Lightcast

We currently offer a similar mapping via the Titles API (Titles → SOC+Skill). This proposed mapping would enable us to sunset this alternate mapping in favor of more fully utilizing our Lightcast Occupation Taxonomy. This mapping also ensures clients stay within the Lightcast taxonomy ecosystem (vs sending them to a Government taxonomy). Further - Legacy BG Occupation Classifier API clients will transition to this utilize this mapping so we can also shut down that legacy service.

Tools such as Analyst and Talent Transform could also utilize this mapping.

Target User Role/Client/Client Category

Clients who use our Job title normalization API endpoint (54 clients in the last 90 days). This could also be used in our Analyst tool to quickly get from a Title to Occupation (client can type in a Title and we’d actually search Specialized Occupation).

Delivery Mechanism

Classification API - /mappings endpoint (Title->LOT)

Success Criteria & Metrics

Epic will be completed with Titles-> Spec Occ (LOT) is exposed to clients and we have a robust process in place to keep this mapping up to date with our Titles taxonomy updates.

Success would be transitioning clients using the /mapping endpoint(Titles API) AND BG Occupation Classifier API and further adoption in process.

Aspects that are out of scope (of this phase)

N/A

Solution Description

Early UX (wireframes or mockups)

N/A

Non-Functional Attributes & Usage Projections

Clients utilizing Legacy BG Occupation Classifier API will move to this service will be available.

Dependencies

Is there any work that must precede this? Feature work? Ops work? 

• Taxonomy team must complete this mapping

• Data Delivery will expose in the Classification API mappings endpoint

Legal and Ethical Considerations

Just answer yes or no.

High-Level Rollout Strategies

Risks

This mapping will not be perfect - there is a chance clients expectations will not align with how it will be built. (vague titles will have a mapping which most commonly aligns with that title in job postings data - not what the client might be expecting)

Open Questions

What are you still looking to resolve?

Complete with Engineering Teams

Estimated Costs

Direct Financial Costs

Are there direct costs that this feature entails? Dataset acquisition, server purchasing, software licenses, etc.?

Team Effort

Each team involved should give a general t-shirt size estimate of their work involved. As the epic proceeds, they can add a link to the Jira epic/issue associated with their portion of this work.