• Decent salary, stock option, ESPP available • Peer-level colleagues are very good, friendly, and open to new ideas • Good snack program • The first two years are really very exciting • Great company for college graduates
• Working days are very long. For a senior engineer position, you can expect meetings with the USA till 7 pm (sometimes till 8). The day starts at 9 am. There are too many meetings.
• Career growth is very limited. If you have the ambition to grow on the technical ladder, then this company is not for you. Some people have already complained about favoritism (read other Glassdoor reviews).
• The majority of the managers are good at talking and have less technical knowledge. As this company grows rapidly, this becomes a major issue. Management values people who are good storytellers.
• With the growth of the company, they are becoming more process-oriented. This is too much sometimes.
• The Dublin App Dev team depends heavily on the USA. The Dublin team doesn't have enough freedom for a technical decision (this is one of the reasons to have so many late-night meetings).
• After two years working as an application developer, your learning scope is very limited. Once you have worked in (almost) all Xpresso frameworks, there is not much to learn, and the job becomes less challenging.
• Technical interview processes are very easy. This is one of the reasons lots of candidates (who are not so good technically) got offers.
The interview was easy. I thought it would be a tough one, but it wasn't. I wasn't bombarded with DSA and the usual suspects, just straight assessments and discussion around modern topics like Git and general DOM.
The interview was clear and well-organized. First, a simple background check was conducted, followed by a chat with the manager focused on scenarios. It was interesting but challenging to explain everything fully. A final stage was planned, but I co
1. Recruiter call to discuss the role and salary expectations. 2. Hiring manager call - about your experience in general and which language/tool you have used in your previous role. 3. HackerRank test in Python and Bash. The position was for DbaaS, s
The interview was easy. I thought it would be a tough one, but it wasn't. I wasn't bombarded with DSA and the usual suspects, just straight assessments and discussion around modern topics like Git and general DOM.
The interview was clear and well-organized. First, a simple background check was conducted, followed by a chat with the manager focused on scenarios. It was interesting but challenging to explain everything fully. A final stage was planned, but I co
1. Recruiter call to discuss the role and salary expectations. 2. Hiring manager call - about your experience in general and which language/tool you have used in your previous role. 3. HackerRank test in Python and Bash. The position was for DbaaS, s