How did you organize development tasks (UI, frontend, backend)? What did the documentation consist of?

Task setting for development usually includes several key components tailored to the type of work — UI, frontend, or backend.

For UI and frontend:

• Technical assignment (TA) with a description of functionality, design requirements, interactivity.
• Layouts and prototypes (e.g., Figma, Sketch) with explanations of element behavior.
• Requirements for responsiveness and cross-browser compatibility.
• API description, if the frontend interacts with the backend.

For backend:

• Technical assignment with a description of business logic, performance, and security requirements.
• API specification (REST, GraphQL, etc.) with examples of requests and responses.
• Database structure and schema description.
• Requirements for integration with external systems.

Documentation is usually formatted as a set of documents or pages in a project management system (Confluence, Notion):

• Goals and objectives.
• Functionality description.
• Technical requirements.
• Design and prototypes.
• API specifications.
• Acceptance criteria.

Example of an API task part:

{
  "endpoint": "/api/users",
  "method": "GET",
  "description": "Get list of users",
  "parameters": {
    "page": "page number",
    "limit": "number of items per page"
  },
  "response": {
    "users": [
      {"id": 1, "name": "Ivan"}
    ],
    "total": 100
  }
}