Basic Principles and Rules of Our Team



  1. Self-sufficiency, responsibility, punctuality, and proactivity (within our technological stack).
  2. Every employee can and must introduce all issues and offers he/she is interested in at the general meeting along with other employees.
  3. Contact the colleagues or the team leader on all the issues that arise.
  4. Every employee of the team is obliged to individually follow the availability of the required volume of tasks to work at for the current and next days.
    If for some reason you do not have a task, contact the leader or project manager.
  5. If the current project or the tasks stack is about to finish, the employer must inform the leader or the project manager about it in advance. The sooner the better. The manager needs time to find a new project or a task.
  6. Every employee is individually responsible for the quality of the performed work no matter whether he/she works individually or in the team.
  7. The working day is 8 hours + 1 hour for dinner that is not included in the working day.
  8. The working day begins before 11:00. If you need to join later, make sure to inform the leader or the project manager in advance.
  9. If the difference in time zones with the customer is considerable, the working schedule must be shifted to have a possibility to communicate with the customer.
  10. Employees who have already completed the trial period and got a long-term order can work remotely. Herewith, the working day is the same as if you worked in the office.
  11. If you need, you can take a sick leave. Inform the manager or the project leader about it as quickly as possible.
  12. In order to get a traditional vacation, you need to write a request about the vacation not later than 2 weeks prior to it, and make a relevant mark in the vacations schedule.
  13. Cleanness, trimness and second pair of shoes are welcome.
  14. The desk must not contain garbage, only the objects you need for work.

We are looking forward to meeting you on our website

About the author

Stay Informed

It's important to keep up
with industry - subscribe!

Stay Informed

Looks good!
Please enter the correct name.
Please enter the correct email.
Looks good!

Related articles

Guidelines to Writing a Clear Spec [Software Specification Document]

In this article, we’ll clearly define what a spec is, why you need it, what you should include in the requirements, and finally, how to write an ...

Developer Guide to GDPR

It’s been over a year since the GDPR came into full effect, thus panic associated with the changes has already subsided; nevertheless, the GDPR ...

Web Accessibility: Standards, Guidelines, Testing & Evaluation Tools

In this piece, we’ll address the critical importance of accessibility, the laws and regulations currently in practice, and the testing and ...

No comments yet

Sign in

Forgot password?

Or use a social network account


By Signing In \ Signing Up, you agree to our privacy policy

Password recovery

You can also try to

Or use a social network account


By Signing In \ Signing Up, you agree to our privacy policy