Microservices architecture. The team's responsibility is pretty clear.
Many new things as an SDE to play with: React, Next.js, GraphQL, Cypress, etc.
For me, there won't be a lot of work to do as an intern; the job is pretty chill.
Generous equipment and perks. Keyboard, mouse, etc., could be kept after the internship.
Old frameworks, with a pretty bad developer experience (check kraken.js).
Old versions of Jira/Confluence make searching docs extremely painful.
Microservice architecture brings a lot of complexity to the system. Often, it takes time to ping many people to get some simple job done.
Lots of crappy in-house tools that are buggy all the time.
The process started more than a month ago. I've had four phone calls, between the HR staff, hiring manager, and internal recruiters.
It was a long process. There were two technical interviews, followed by two more interviews for team matching. Lastly, I received an offer after all this. The interviews were easy, and none of them followed LeetCode style.
A recruiter reached out to me on LinkedIn and presented a front-end engineering opportunity with high-level details on what they were looking to fill. My first interview was a video call with someone, supposedly an engineer, approaching a problem on
The process started more than a month ago. I've had four phone calls, between the HR staff, hiring manager, and internal recruiters.
It was a long process. There were two technical interviews, followed by two more interviews for team matching. Lastly, I received an offer after all this. The interviews were easy, and none of them followed LeetCode style.
A recruiter reached out to me on LinkedIn and presented a front-end engineering opportunity with high-level details on what they were looking to fill. My first interview was a video call with someone, supposedly an engineer, approaching a problem on