Work stability, no layoffs.
They count your working hours. ROFL.
Huge-size company with every possible internet restriction, interfering with your job (slow proxies, broken SSLs, inhibition of entire protocols like tcp/22, forbidden access to socials where software engineers debate techies, etc.).
Non-trust culture: Everyone suspects everyone else.
No space for technical growth: If you want to take a training, that is NOT included in your work time. That's ridiculous in a fast-paced, changing world.
If you work as a Software Engineer, you have to take some incredibly messed-up internal algorithm proficiency certifications in C or Java, not recognized anywhere else, of course.
Internal portals are like labyrinths, impossible to understand. Some work only on Windows. Some may prompt JS popups in Korean and kill your browser entirely.
Bureaucracy for anything that's easy: If you need a headphone, you must ask for 10 approvals, with a chain of command going up to almost the company CEO.
You can take your first PTO day after at least 6 months, which I think is even illegal.
Update the corporate culture to 2018.
It was good. Ask operating system questions, including topics like pages and deadlock, and Object-Oriented Programming (OOP) based questions. There were then 3-4 coding questions, mainly on linked lists and graphs. You can search on GitHub; all quest
Resume screening, coding interviews (four hours), and a final interview. Overall, the questions are not that easy if you are unprepared. However, if you work on a few coding tests beforehand, it will be easier than you think.
I went through my resume in the technical round and was asked questions from the courses I listed on it. Questions covered Computer Architecture, Computer System Design, and Data Structures & Algorithms. Later, there was an HR round where my though
It was good. Ask operating system questions, including topics like pages and deadlock, and Object-Oriented Programming (OOP) based questions. There were then 3-4 coding questions, mainly on linked lists and graphs. You can search on GitHub; all quest
Resume screening, coding interviews (four hours), and a final interview. Overall, the questions are not that easy if you are unprepared. However, if you work on a few coding tests beforehand, it will be easier than you think.
I went through my resume in the technical round and was asked questions from the courses I listed on it. Questions covered Computer Architecture, Computer System Design, and Data Structures & Algorithms. Later, there was an HR round where my though