---
esco_uri: http://data.europa.eu/esco/skill/0e0c9c11-b39e-43cf-ba95-2fe646f5de64
esco_label: "identify customer requirements"
relation: essential
onet_soc: 15-1252.00
source: model-knowledge
confidence: high
qa_count: 0
generator: gemma3:27b (prompt-designed and spot-checked by Claude)
generated: 2026-07-10
---

# identify customer requirements — Software Engineer

As a Software Engineer, 'identifying customer requirements' isn’t just about *asking* what users want; it's about translating vague needs into concrete, testable specifications. Daily tasks involve participating in sprint planning meetings, conducting user story workshops (often using tools like Jira or Azure DevOps), and directly interacting with Product Owners/Business Analysts – but also proactively seeking clarification when stories are ambiguous. You’ll be digging deeper than surface-level requests; for example, a request for 'faster loading times' needs to become ‘page X must load in under 3 seconds on a typical mobile connection’, which requires investigation and potentially user research (A/B testing, analytics review).

## Weitere Anreicherung

Stage-2 source for future practitioner grounding: arXiv cs.SE (software-engineering preprints).
