The listed distribution
Browse production-code roles, configuration and integration roles, and prototype or script roles. The original posting is the place to confirm the tools, ownership, and expected delivery.
What the labels mean
Production code means the posting describes software that will run as part of a delivered or operated system. Configuration and integration covers connecting systems, mapping data, or adapting an existing product. Prototypes and scripts covers exploratory or limited-purpose code. “No coding” is our reading that the role does not involve coding. “Not stated” means the text did not support a reliable classification.
These groups describe the main coding shape we read. A production role can still include prototypes or integration. An integration role can still require careful software engineering. Read the details for APIs, tests, deployment, monitoring, debugging, data work, and customer or internal users.
How to compare a role with your experience
Ask what happens to the code after the first demonstration. Who owns deployment? Who responds when an integration fails? What tests and logs are expected? Who decides when the customer can use the result? These questions separate a production responsibility from a short prototype without assuming that one is better.
The dataset also records technology mentions. A posting naming Python, SQL, or a cloud service shows that the term appears in its text. It does not prove that the tool is required in every part of the role or that it will be tested. See FDE skills and learning for a practical way to turn a named technology into evidence of work.