Signal source
Job posting signals.
An engineering job posting describes the work a team expects to do. It names device families and toolchains because candidates are screened on them, and it appears when a team is growing.
That makes it evidence about two things: what a company's engineers work with, and that something is being staffed.
What the team works with, and that it is hiring.
In testing, a posting for an FPGA design engineer at a lidar manufacturer named the device class the team develops on and described the work as sensor processing and customer-facing features for the next generation of the product.
- Device families and tools the team uses
- What the programmable device does in the product
- That a hardware team is being staffed, with a date
A posting is about a team, not about a product.
Experience with a device family is a hiring requirement. It is not a statement that a named product contains that device. When the posting from the test was given to the extraction step, it filled the timing field and left the device field unknown. That is the intended behaviour.
- Hiring does not prove a purchasing programme.
- A posting lists alternatives; it rarely says which one is in production.
- Postings close. The date it was seen and the date it closed are both recorded.
The signal is the posting and the company. Names of people in roles are not collected.
Where postings help most.
- Timing, when a product fits and nothing says the design is open
- Learning which device families a company's engineers know
- Spotting a move from one family to another
How signals are detected · Datasheet signals · FCC filing signals · Teardown signals
Ask what hiring shows in your application class