Those could mean anything. Some people think 5k likes is large. Others think 100k is small.
Oh well, at least they didn't say "complex".
Since its proprietary, it runs in a private cloud environment and is processing only data of one "user per instance"; there is not public interface, only a VPN you have to dial in etc., so no frontend/frontpage facing the public.
Though, there are some design flaws from this perspective, because of convenience: E.g. it lets you persist the account number in the DB, if wanted.
LOC is currently around 200k, so for sure: Its not Microsoft-scale :-D
I could do this TCP server in another time at all and it would be perfect. I have done stuff that complicated and more many times.
You need to rethink how you are using the tool because you absolutely could get excellent results like I do.
The biggest things I suggest are... Treat it as collaboration or pair programming. Make sure to work through a design before programming and have it written to a file for your review before execution.
You can do this.
The last: I asked for a quick TCP server in C++ that handled just a single client (disconnecting the existing client when a new client connected), with a send() that I could call from another thread. It was holding mutexes over read(), and trying to set the SO_REUSEPORT port socket option on a socket that had already been bound. Subtley broken garbage.
It would literally be better to copy and paste a solution off Stack Overflow, because at least there's a chance it'd have been reviewed by someone who knows what they're doing.