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

None over current NOVA solution

Value to Customers & Users

None over current NOVA solution

Value to Lightcast

We need to bypass Nova in go-forward systems to enable significant engineering cost reduction in both engineering time and the reduction of ongoing system costs.

Target User Role/Client/Client Category

Who are we building this for?

All users looking at ANZ/SGP data

Delivery Mechanism

How will users receive the value?

Analyst, Snowflake and API’s

Success Criteria & Metrics

How will you know you’ve completed the epic? How will you know if you’ve successfully addressed this problem? What usage goals do you have for these new features? How will you measure them?

Success looks like data parity for features between the Nova feed and the Lightcast feed.

Aspects that are out of scope (of this phase)

What is explicitly not a part of this epic? List things that have been discussed but will not be included. Things you imagine in a phase 2, etc.

Any enrichments currently not supported by the Burning Glass cloud are not in scope.

Solution Description

Non-Functional Attributes & Usage Projections

Consider performance characteristics, privacy/security implications, localization requirements, mobile requirements, accessibility requirements

Data should be migrated to the standard used in US/UK/CA, i.e.

• Posting text

• National occupation taxonomy

  • ANZSCO (down to 6-digit) for Aus/NZ

  • SSOC (down to 5-digit) for SGP

• LOT taxonomy (moving to LOTv6 when ready)

• National industry taxonomy

  • ANZSIC for Aus/NZ

  • SSIC for SGP

• City name (assume this is possible in the same way as in US/UK/CA?)

  • SGP - none

  • NZ - happy to port this from Nova, good quality

  • Australia - current Nova city name is poor quality, would prefer a new one if we can find an existing taxonomy

• Administrative geography

  • None in SGP

  • Australia (all shape files here from ABS https://www.abs.gov.au/statistics/standards/australian-statistical-geography-standard-asgs-edition-3/jul2021-jun2026/access-and-downloads/digital-boundary-files )

    • Statistical Areas Level 4 - 2021

    • Statistical Areas Level 3 - 2021

    • Local Government Areas - 2022

  • New Zealand

    • Regional Councils https://datafinder.stats.govt.nz/layer/106666-regional-council-2022-generalised/

    • Territorial Authorities https://datafinder.stats.govt.nz/layer/106668-territorial-authority-2022-generalised/

• Salary

• Company name

• Company is staffing

• Education

• Experience

• Contract Type

• Employment Type

• Remote Type

• Lightcast Skills

• Lightcast Title

• Source

Dependencies

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

Legal and Ethical Considerations

Just answer yes or no.

High-Level Rollout Strategies

• Initial rollout to [internal employees|sales demos|1-2 specific beta customers|all customers]

  • If specific beta customers, will it be for a specific survey launch date or report availability date 

• How will this guide the rollout of individual stories in the epic?

• The rollout strategy should be discussed with CS, Marketing, and Sales.

• How long we would tolerate having a “partial rollout” -- rolled out to some customers but not all

Risks

Focus on risks unique to this feature, not overall delivery/execution risks. 

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.