We are looking for a specialist to support and develop our Telegram bot, written in Python. This is not a full-time position, but a flexible collaboration: as needed, you will fix bugs, add new functionality, or optimize existing code.
Responsibilities:
- Fixing bugs in the bot (logic, API, messages, integrations)
- Additional functionality — by agreement (new commands, automation, integrations)
- Conducting code reviews (if necessary)
- Providing reports on completed work
- Possible participation in testing changes
Requirements:
- Experience with Python (minimum intermediate level)
- Understanding of Telegram Bot API
- Experience with databases
- Debugging skills
- Preferably experience with Python frameworks (e.g., Flask, aiogram, Telebot, etc.)
- Willingness to work as a contractor, not full-time
- Willingness to sign an NDA (non-disclosure agreement), if necessary
Work format:
- Hourly payment (freelance)
- Flexible schedule: work “as needed,” but with an agreed plan or arrangement
- Reports on hours
and completed tasks
I am sending a file with our bot (version without confidential information). We are currently looking for a reliable contractor for long-term technical support and improvements of this bot.
Please review the code and respond, if possible, to the following questions:
🔧 1. Technical expertise
1. Are you comfortable with the technology stack on which the bot is written?
2. Have you worked on similar projects before?
3. Can you briefly describe how you see the architecture of the bot after reviewing the file?
4. Do you see potential problems with the code structure or logic?
🔍 2. Error and risk analysis
5. Do you find any bugs or unstable places in the bot upon first review?
6. What technical risks may arise in the future?
7. Are there any aspects that should be rewritten or optimized?
8. Does the code adhere to the basic principles of clean architecture (clean code)?
9. Are there places that may cause frequent crashes or failures?
⏱️ 3. Time estimation
10. How much time will a basic audit and tidying up of the bot take?
11. How long will it take to fix the identified bugs?
12. How much time will be needed for ongoing support on average per month (approximately)?
13. How long will it take to connect/check webhooks, integrations, logging?
💰 4. Cost estimation
14. What is your hourly rate?
15. Can you roughly estimate the cost:
of the initial code audit?
of fixing bugs?
of regular support?
16. Do you work on fixed tasks or only by the hour?
17. How is payment handled — after completion, in advance, in parts?
🔐 5. Security and confidentiality
18. Are you willing to sign an NDA?
19. How do you ensure the security of access and data?
20. How do you organize work with tokens, passwords, keys?
21. Do you maintain a separate secure storage for secrets? (e.g., .env)
📈 6. Quality of work
22. Will you keep a changelog?
23. Do you provide brief technical reports after completing tasks?
24. Do you maintain documentation for the project?
25. Do you offer recommendations for product improvement?
🤝 7. Collaboration format
26. Are you interested in long-term collaboration with an irregular number of tasks?
27. Are you willing to respond to small tasks (1–2 hours of work)?
28. Are you comfortable working in conditions where sometimes there are no tasks, and sometimes several in a row?
29. Are you willing to support the bot on a “request” basis?
🛠️ 8. Work processes
30. In what format do you prefer to receive tasks? text video Trello / Jira Google-doc
31. What communication method is most convenient for you?
32. What response time frame do you guarantee (e.g., 24 hours)?
33. Do you work on weekends / can you connect urgently?
34. Do you have the ability to occasionally make calls for coordination?
📂 9. Deployment and environment
35. Do you need access to the server for testing?
36. Do you work with Docker / VPS / hosting?
37. Can you set up automatic backups and logging?
38. Can you suggest the optimal way to host the bot?
🔄 10. Availability and deadlines
39. When can you start?
40. Can you take on the project immediately after the New Year?