Occupation Benchmark API

Occupation Benchmark API

 

Target PI

PI 1 - 2023

Created Date

Nov 2, 2022

Target Release

January 31, 2023

Jira Epic

Document Status

Draft

Epic Owner

@Nick Studt (Deactivated)

Stakeholder

@Nick Studt (Deactivated)

Engineering Team(s) Involved

Micro

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

Deliver Occupation Benchmark API by end of P1. This API will combine multiple other services already available to provide a snapshot of the Labor Market through the lens of an Occupation.

This will enable Legacy BG API clients to move their products/process onto the go-forward Lightcast platform to get their Occupational Benchmarking data.

 

Value to Customers & Users

The value to clients is it provides a single API and endpoint to get all of our most critical labor market data through the lens of an occupation in a single call to the API. This API will combine nearly 10 APIs into a single interface. Wrapping things like JPA, Core LMI, DDN, Salary Boosting Skills, Career Pathways, Occupation Growth and Skill Gaps.

 

Value to Lightcast

This will be the last piece from an API perspective to enable all Legacy BG API clients to move onto the go-forward platform. Once we move these clients, we can begin to shut down the legacy services.

Target User Role/Client/Client Category

Legacy BG clients to start. This will also be the primary API which any client would consume most of our occupation based models.

 

Delivery Mechanism

API only

 

Success Criteria & Metrics

Epic is complete when API and docs are launched. Success is measured by full transition of Legacy BG clients and minimal usage of the Legacy Service.

 

Aspects that are out of scope (of this phase)

No front end work. No data work.

  • Follow up would be expansion of global coverage - adding UK, CA, Global data elements/models

 

 

Solution Description

https://economicmodeling.atlassian.net/wiki/spaces/MICRO/pages/2131460458

https://economicmodeling.atlassian.net/wiki/spaces/MICRO/pages/2139258920

 

Non-Functional Attributes & Usage Projections

To start - we’d support primarily US but would like to expose CA/UK data where available

 

Dependencies

None - only team involved is Micro API Dev team

 

Legal and Ethical Considerations

Just answer yes or no.

Have you thought through these considerations (e.g. data privacy) and raised any potential concerns with the Legal team?

High-Level Rollout Strategies

Launching in February - primarily to existing Legacy BG clients then expanding communication to other areas of the sales/CS business to push this product more broadly.

Risks

None

 

Open Questions

None

 


Complete with Engineering Teams

 

Effort Size Estimate

2

Estimated Costs

Direct Financial Costs

Minimal costs - no additional data is required. Some service hosting fees but should be very minimal. This service is a wrapper API which serves up data available in other APIs.

 

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.

Team

Effort Estimate (T-shirt sizes)

Jira Link

Team

Effort Estimate (T-shirt sizes)

Jira Link

Micro

Large

https://economicmodeling.atlassian.net/browse/MIC-1574