Features were released to all users as long as they increased critical product artifacts (e.g., user visits, user retention).
Good infrastructures. Many infrastructures improved efficiency, such as A/B testing, settings, a rich amount of 2nd-party components, and DevOps.
Good documentation. I didn't love documenting until I entered this company. You could easily find answers to problems by simply searching the documents. The Lark Document was a great product.
Talent and hard-working coworkers. Most of the coworkers were friendly, talented, and hard-working, even the graduates. You always got motivated working with them.
Heavy workload. The working hours were mostly from 10:30 A.M. to 10:30 P.M. I always left the office at 10:30 P.M. because there were so many tasks to finish every day. The company offered 3 meals, so you didn't have to leave the office.
Lack of manpower all the time. I often felt overwhelmed but didn't have coworkers to delegate some tasks to. In hiring new employees, HR didn't help much; we were on our own.
Hard to finish work at the office. Distractions from meetings, instant chats, and coworkers all the time meant I sometimes got started work after everyone left the office at night.
The interview started with a discussion of my past projects, followed by several questions on computer science fundamentals such as operating systems, databases, and basic data structures. After that, I was given a short live coding task, which invol
They were pretty quick on notifying if you have passed a round. The interview questions were like every other interview in the industry for the same position. As long as you know what you are doing, you'd be fine.
Intermediate difficulty, catching rainwater. The interviewer is helpful and engaging the whole time. Ask for a resume deep dive and one LeetCode-style question. For the Q&A session, I asked what the role will be like and what tech stack is required.
The interview started with a discussion of my past projects, followed by several questions on computer science fundamentals such as operating systems, databases, and basic data structures. After that, I was given a short live coding task, which invol
They were pretty quick on notifying if you have passed a round. The interview questions were like every other interview in the industry for the same position. As long as you know what you are doing, you'd be fine.
Intermediate difficulty, catching rainwater. The interviewer is helpful and engaging the whole time. Ask for a resume deep dive and one LeetCode-style question. For the Q&A session, I asked what the role will be like and what tech stack is required.