You will get a code review for Golang back end
Top Rated
Project details
You will get a feedback/reviewed code with comments/suggestions for improvement. Please send along the link to the github repo for the review.
Programming Languages
GoCoding Expertise
Performance OptimizationWhat's included
| Service Tiers |
Starter
$200
|
Standard
$500
|
Advanced
$750
|
|---|---|---|---|
| Delivery Time | 1 day | 3 days | 7 days |
Number of Revisions | 1 | 2 | 4 |
Design Customization | - | - | - |
Content Upload | - | - | - |
Responsive Design | - | - | - |
Source Code |
193 reviews
(187)
(5)
(0)
(1)
(0)
This project doesn't have any reviews.
JK
Joram K.
May 8, 2025
English to Russian - Machine Translation Post-Editing (Start immediately!)
Had a great collaboration with Andrey, recommended for Russian and Ukrainian projects.
AM
Adaline Lefe M.
Apr 3, 2025
Russian Content Writer
BF
Brandon F.
Feb 27, 2025
Backend Developer
Andrey is communicative, motivated, and does excellent work.
BM
Brendan M.
Feb 25, 2025
Hotel Availability and Booking API Development
I would not recommend Andrey despite the acceptable work he delivered. There are two reasons for this
1) Andrey invoiced 30 minutes for sending a slack message asking if there was any work for him that week. To be fair, when called on this, he did say that he reduced the next manual bill by 30 minutes to compensate.
However, this, combined with his unwillingness to use the hourly tracker from the start, plus the fact that he billed significantly (1.5 - 2X) more hours than our other API developer on similar projects, we lost the trust in him to bill honestly. Maybe he is just slower than the other API developer. But the combined unwillingness to use the tracker and the invoicing 30 minutes for a slack message asking for work is quite over the line in our view; considering we did not agree on any kind of retainer or fixed number of hours (see below)
The relevant text from the job post: (Number of hours
"The number of hours per week will depend on how many integrations we need that week, but over a month we expect something like 20-40 normally but if new deals are closed it could go up."
2) Despite us clearly mentioning that the hours would vary in the job description and in the interview, Andrey somehow came to believe that he was "owed" 10 hours a week of work.
Once we called him on the issue that he billed 30 minutes for a slack followup asking for work, he refused to even give us a timeline when he would work on our projects. Instead, he would simply answer, I don't have time this week, maybe I will have time next week.
Since we complained about the overbilling and gave him another chance, he refused to do any additional work other than 2 hours.
In his communication with the team, he had the audacity to make 2 further false claims:
1) " that the capacity isn't set, and this literally became 1 or 2 hrs per week (if at all) project,"
This is not true, we assigned several API connections and he replied that he did not have time
2 " for future I guess it would help a lot if you guys have a bit more visiblity in terms of the expected workload,"
This is also a false claim since as mentioned above, the expectations of hours was set from the beginning in both the interview and in the job description.
Obviously, I cannot recommend a freelancer that misrepresents clearly documented discussions and information, despite the fact that the work delivered was of acceptable quality.
1) Andrey invoiced 30 minutes for sending a slack message asking if there was any work for him that week. To be fair, when called on this, he did say that he reduced the next manual bill by 30 minutes to compensate.
However, this, combined with his unwillingness to use the hourly tracker from the start, plus the fact that he billed significantly (1.5 - 2X) more hours than our other API developer on similar projects, we lost the trust in him to bill honestly. Maybe he is just slower than the other API developer. But the combined unwillingness to use the tracker and the invoicing 30 minutes for a slack message asking for work is quite over the line in our view; considering we did not agree on any kind of retainer or fixed number of hours (see below)
The relevant text from the job post: (Number of hours
"The number of hours per week will depend on how many integrations we need that week, but over a month we expect something like 20-40 normally but if new deals are closed it could go up."
2) Despite us clearly mentioning that the hours would vary in the job description and in the interview, Andrey somehow came to believe that he was "owed" 10 hours a week of work.
Once we called him on the issue that he billed 30 minutes for a slack followup asking for work, he refused to even give us a timeline when he would work on our projects. Instead, he would simply answer, I don't have time this week, maybe I will have time next week.
Since we complained about the overbilling and gave him another chance, he refused to do any additional work other than 2 hours.
In his communication with the team, he had the audacity to make 2 further false claims:
1) " that the capacity isn't set, and this literally became 1 or 2 hrs per week (if at all) project,"
This is not true, we assigned several API connections and he replied that he did not have time
2 " for future I guess it would help a lot if you guys have a bit more visiblity in terms of the expected workload,"
This is also a false claim since as mentioned above, the expectations of hours was set from the beginning in both the interview and in the job description.
Obviously, I cannot recommend a freelancer that misrepresents clearly documented discussions and information, despite the fact that the work delivered was of acceptable quality.
EB
Ejane B.
Feb 10, 2025
GoLang Developer
About Andrey
Golang Backend & Microservices Developer | AWS & GCP | REST API Expert
100%
Job Success
Kostanay, Kazakhstan - 4:29 pm local time
I specialize in Go microservices, leveraging tools like Docker, Kubernetes, and cloud services (AWS/GCP) to ensure your backend is scalable and reliable.
I help startups and businesses design robust backend systems from scratch, or improve existing platforms to handle growth. My goal is to ensure your application’s backend is secure, fast, and scales effortlessly as your user base grows.
⚡ Key Skills & Technologies
✅ Golang & Microservices: Building RESTful and gRPC APIs using Go, with expert use of concurrency patterns for high-performance, scalable services.
✅ Cloud Platforms (AWS, GCP, Azure): Deploying and scaling applications on Amazon Web Services, Google Cloud, and Azure. (E.g., using AWS Lambda, Google Cloud Pub/Sub, or Azure services as needed.)
✅ Databases & Messaging: Experience with SQL and NoSQL databases like PostgreSQL, MySQL/MariaDB, MongoDB, plus caching and messaging systems such as Redis, Apache Kafka, and RabbitMQ for robust data pipelines.
✅ API Security: Implementing OAuth2, JWT authentication, and secure token management (including Firebase Auth and AWS Cognito) to protect APIs.
✅ Real-Time Communication: Developing real-time features using WebSockets (Gorilla toolkit) and event-driven architectures for live updates (e.g. in chat or notification systems).
✅ Testing & Monitoring: Writing thorough unit/integration tests and using monitoring/logging stacks (e.g. ELK Stack with Elasticsearch, Logstash, Kibana) to ensure code quality and reliability.
🔷 RECENT PROJECTS
------------------
🟦 MEDICAL ERP
Physician Partners business is based on early disease detection, prevention, and treatment. SXOPE is the IT backbone of the clinic's operations. Here are some key facts about the system 45 clinics+, 400+ PCPs, 60 000+ patients. I was a part of backend dev team consisting of 20+developers, besides new features development also did L3 support/bug fix tasks. The system is written in Go and is based on GCP stack.
🟦 ATMOS CLI
Enhanced circuit breakers mechanism and repos cloning for more resilient performance under heavy load, integrated GitHub, Gitlab and Bitbucket tokens injection to bypass rate limits, introduced support for SSH vendoring, fixed the bug with globs (both shallow and greedy) inclusing and exclusion patterns as well as SCP SSH urls alignment for go-getter. Also implemented a sub command 'docs generate' for readme files that have terraform variables listed (json, hcl, helmfile).
Tech Stack: Go, GitHub APIs, Jenkins for CI/CD, Docker-based deployments
🟦 HOTEL SCRAPING ENGINE
Migrated Python scrapers to Golang microservices, increasing data throughput by 50% and improving maintainability.
Tech Stack: Go, concurrency, Redis, AWS CDK for IaC
🟦 GYM & FITNESS APP
implemented Stripe, Cliq, and Payarc for seamless payments, resulting in a smoother billing process for the client’s users. Built membership, billing, and account endpoints using Golang, GORM, and PostgreSQL.
leveraged Docker and CI/CD (Jenkins) to ensure fast and reliable deployments.
🟦 BOXES APP
Developed a notifications microservice in Go with Redis Pub/Sub; added WebSocket endpoints for real-time updates.
Implemented Jenkins pipelines for automated builds and tests
🟦 AI Agent
Created OAuth2 flows (Facebook, Instagram, TikTok) and cron-based publishing with Golang APIs.
Managed AWS Fargate tasks to scale containerized workloads
🟦 TelePQC – Post-Quantum Secure Telecom Prototype
Designed and implemented a post-quantum secure communication prototype combining lattice-based key encapsulation (Kyber/NTRU) and code-based digital signatures (McEliece), grounded in Discrete Analysis and Theory of Random Coding. Applied Stochastic Methods of Informatics and Operations Research techniques to model and optimize encryption/decryption latency across simulated telecommunication networks, and partnered with academic cryptographers to benchmark against NIST PQC candidates. Keywords: post-quantum cryptography, lattice-based KEM, code-based signatures, discrete mathematics, stochastic optimization, telecom network security.
🚀
Steps for completing your project
After purchasing the project, send requirements so Andrey can start the project.
Delivery time starts when Andrey receives requirements from you.
Andrey works on your project following the steps below.
Revisions may occur after the delivery date.
Provide link to the repo
The code review takes place in this repo