Start of main content

Call for paper

If you are reading this you are thinking about submitting a proposal for a talk. That’s great!

We are interested in the following topics

If you have an interesting idea on a topic that is not on the list we will be happy to consider your proposal anyway!

  • Software solutions under the hood
    • Web service description languages (SOAP/WSDL, OpenAPI, GraphQL)
    • Markup languages (XML, JSON/YAML)
    • Integration API (Swagger, Postman, cURL, HTTPie, Insomnia)
    • Queues, buses and message brokers (RabbitMQ, Kafka, Spark)
    • DSL and Low-code platforms
  • Requirements
    • Description and presentation (user story, use case, JTBD, CJM)
    • Non-functional requirements (performance, capacity management, compliance, information security)
    • UX/UI
    • Approaches and standards (ISO 29148, GOST 34, GOST 19)
  • Business processes
    • Notations (BPMN, UML, C4, IDEF, ARIS, EPC)
    • Tools (Enterprise Architect, PlantUML, Structurizr)
    • BPMS
  • Documentation
    • Confluence
    • AsciiDoc[tor]
    • Sphinx
    • Docusaurus
    • SSG
    • DocOps
  • Data
    • Data visualization and presentation
    • Data architecture design
    • Tools (R, Python, RegExp, ETL, Tableau, PowerBI, Grafana, DataLens, SQL, NoSQL)
  • Architecture development
    • Service design
    • Microservice architectures and other architectures
    • DDD
  • Collaboration tools
    • Github
    • Gitlab
    • Jira
    • Trello
  • Technological approaches to the organization of interaction
    • REST
    • CQRS
    • OData
    • Reactive
  • Other
    • Examples of real-life issues from different industries — fintech, retail, mobile, logistics, transport, telecom and others

Submission process

A workflow diagram from accepting an application to speaking at a conference.

Selection process

  • Relevance

    You are going to discuss things that participants of the conference find useful not only yesterday but also today and in the future. In addition, the topic of your session matches the theme of the conference, and the content you are going to present matches the stated description.

  • Depth

    Your talk reveals the subject deeply and comprehensively. There is no need to talk about yet another Hello World (unless you think it’s a new, not widely known, but very promising technology).

  • Originality

    There is technical novelty in your session; the content either hasn’t been published before or presents a well-known topic / problem in a different light.

  • Technical expertise

    You have experience and have completed projects in the field in question. The topic of your presentation is technically sound. You have a good understanding of what you are talking about and have been involved in the implementation of the project you are describing.

  • Practical applicability

    The content is important from a practical point of view and you not only cover the existing problems / solutions, but also share your experience.

  • Speaking experience

    If you have experience in speaking at conferences and meetups, this will be a great advantage. If this is your first presentation, be prepared to rehearse and practice.

Additional information

  • If you feel like you need help to prepare your session you can count on us: we can appoint a personal curator who will review your material and organize rehearsals.
  • Usually, we contact applicants within a week after the submission. If that hasn’t happened, feel free to contact us via email at Also, don’t forget to read the speaker’s memo.
  • If you are submitting on behalf of another person, please fill the form using the speaker’s contact information. You can leave your contacts in the last form field (the one which asks about a co-speaker or comments).