---
esco_uri: http://data.europa.eu/esco/skill/d9e5349e-8791-49c2-8ba4-839fdd1606c2
esco_label: "define technical 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
---

# define technical requirements — Software Engineer

As a Software Engineer, 'defining technical requirements' isn’t just about listing *what* the software should do – it's translating vague user needs (“it needs to be fast!”) into concrete, testable specifications. Daily this means participating in requirement gathering sessions (often with Product Managers and stakeholders), then breaking those down into detailed stories or tasks. You'll specify things like API endpoints, data formats (JSON schema, Protobuf definitions), performance metrics (response times under load), security constraints (authentication methods, data encryption), scalability needs (expected concurrent users), and error handling strategies. Tools used heavily include Jira/Azure DevOps for story creation, Confluence/Wiki for documentation, and potentially modeling tools like UML or sequence diagrams to visualize complex interactions.

## Weitere Anreicherung

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