diff --git a/contents/negotiation-rules.md b/contents/negotiation-rules.md index d7772ec2..a832d1bf 100644 --- a/contents/negotiation-rules.md +++ b/contents/negotiation-rules.md @@ -42,7 +42,7 @@ Despite whatever is happening in the negotiation, give the company the impressio ## Don't be the decision maker -Even if you don't particularly care what your friends/family/husband/mother thinks, by mentioning them, you're no longer the only person the recruiter needs to win over. There's no point in them trying to bully and intimidate you; the "true decision-maker" is beyond their reach. This is a classic technique in customer support and remediation. It's never the person on the phone's fault, they're just some poor schmuck doing their job. It's not their decision to make. This helps to defuse tension and give them more control of the situation. +Even if you don't particularly care what your friends/family/spouse/parent thinks, by mentioning them, you're no longer the only person the recruiter needs to win over. There's no point in them trying to bully and intimidate you; the "true decision-maker" is beyond their reach. This is a classic technique in customer support and remediation. It's never the person on the phone's fault, they're just some poor schmuck doing their job. It's not their decision to make. This helps to defuse tension and give them more control of the situation. > I'll look over some of these details and discuss it with my [FAMILY/CLOSE_FRIENDS/SIGNIFICANT_OTHER]. I'll reach out to you if I have any questions. Thanks so much for sharing the good news with me, and I'll be in touch! diff --git a/contents/resume-case-study.md b/contents/resume-case-study.md index 836d2c19..e9ff07f9 100644 --- a/contents/resume-case-study.md +++ b/contents/resume-case-study.md @@ -8,7 +8,7 @@ import TeikjunResumeOldURL from '@site/static/img/teik-jun-resume-old.png'; impo To put the points mentioned in the [previous section](./resume.md) in practice. Here we will be reviewing [Teik Jun's](https://github.com/teikjun) resume, critiquing it and improving it. At the time of writing, Teik Jun is a Year 4 undergraduate at National University of Singapore and is looking for a Software Engineering (SWE) internship for the summer of 2022. -Here's the initial version of Teik Jun's resume I received from him. +Here's the initial version of Teik Jun's resume I received from them.
@@ -32,7 +32,7 @@ On first glance, it looks like a solid resume, and it is. However, I've known Te ### Points of improvement - **Irrelevant experience** - It's honestly super cool to be "Best Shot" of Sniper Course and to get other impressive accolades as an NSF, but it's hardly relevant to a SWE job. If I were running out of space I'd remove it. -- **Not sufficiently conveying the impressiveness of his experience** - Teik Jun's work on the MLH program was for a popular Facebook Open Source project, Docusaurus (the same project that powers this website) and he did very very good work as part of the program. I know because I reviewed his Pull Requests and he did a damn good job. Docusaurus is an important project to Facebook and widely used by popular Facebook projects like React Native, Jest, and Relay. +- **Not sufficiently conveying the impressiveness of their experience** - Teik Jun's work on the MLH program was for a popular Facebook Open Source project, Docusaurus (the same project that powers this website) and they did very very good work as part of the program. I know because I reviewed their Pull Requests and they did a damn good job. Docusaurus is an important project to Facebook and widely used by popular Facebook projects like React Native, Jest, and Relay. - **Not explaining what the project is about** - In most cases, recruiters are the ones reading a resume and they would not know what a project is about, especially when most of them aren't technical. Hence resumes also have to explain the complexity and impact of a project. I know what Docusaurus and TEAMMATES are, but that's because I worked on Docusaurus and I am aware of NUS' projects. Most recruiters would not, so we have to explain what they are. TEAMMATES was also a Google Summer of Code project, so mentioning that would be nice. - **Trivial details** - Under TEAMMATES, there was a point "Added a progress indicator component for expensive operations". This sounds quite small and can be removed if there's a lack of space. - **Obscure projects** - The "Mentorship Management Web Application" doesn't sufficiently relay the complexity. The details are also obvious and doesn't sound impressive. I'd remove this project because it doesn't add much value. @@ -40,7 +40,7 @@ On first glance, it looks like a solid resume, and it is. However, I've known Te ### Bonus -I know that Teik Jun will be interning with ByteDance in the fall, so it could be added as a signal of Teik Jun's abilities, telling recruiters that he's good enough to work at ByteDance. +I know that Teik Jun will be interning with ByteDance in the fall, so it could be added as a signal of Teik Jun's abilities, telling recruiters that they's good enough to work at ByteDance. ## Improved version diff --git a/contents/resume-checklist.md b/contents/resume-checklist.md index 798def5a..1b1e0380 100644 --- a/contents/resume-checklist.md +++ b/contents/resume-checklist.md @@ -68,9 +68,9 @@ Everyone wants the cream of the crop. In the absence of a standardized test, GPA If your GPA is rather low, but you have loads of technical experiences, you can try not listing your GPA in the resume. This kinda "forces" the recruiter to read through your projects/job experience, and perhaps grant you a first interview. If you manage to impress them, who cares about your GPA? But if your GPA is low and you do not have skills for the job... maybe you should work on one of them and revisit job applications later. -In a different scenario, some students have low GPA, but it might be due to some irrelevant classes which they did badly in. E.g. Student X is scoring A for all his programming classes, but did not do well for his language classes. If I am hiring a developer, Student X would still be a suitable candidate despite his low GPA. In such cases, it might even be recommended to attach a transcript along with the resume. +In a different scenario, some students have low GPA, but it might be due to some irrelevant classes which they did badly in. E.g. Student X is scoring A for all their programming classes, but did not do well for their language classes. If I am hiring a developer, Student X would still be a suitable candidate despite their low GPA. In such cases, it might even be recommended to attach a transcript along with the resume. -Also, when you list your GPA/results, try to benchmark it. Instead of simply listing 4.6, write 4.6/5.0 (First Class Honors or Summa Cum Laude). To the recruiter, 4.6 does not mean anything if he/she is not familiar with your grading system. +Also, when you list your GPA/results, try to benchmark it. Instead of simply listing 4.6, write 4.6/5.0 (First Class Honors or Summa Cum Laude). To the recruiter, 4.6 does not mean anything if they/they is not familiar with your grading system. diff --git a/contents/self-introduction.md b/contents/self-introduction.md index 4dc61921..6169a4d9 100644 --- a/contents/self-introduction.md +++ b/contents/self-introduction.md @@ -22,7 +22,7 @@ It is probably not a good idea to spend valuable time talking about things which ## The elevator pitch -An "elevator pitch" originates from a journalist trying to pitch an idea to an editor. The only time to catch the editor was in the elevator and she had only around 30 seconds to do so. The key elements of elevator pitches include: +An "elevator pitch" originates from a journalist trying to pitch an idea to an editor. The only time to catch the editor was in the elevator and they had only around 30 seconds to do so. The key elements of elevator pitches include: - **Short** - You have limited time! - **Direct** - As you only have limited time, you should get to the point @@ -104,6 +104,6 @@ Prepare a self introduction that follows the following outline (inspired by "Cra - "I love to create beautiful and performant products with delightful user experiences." - Same as above, qualities that a Front End engineer should possess. - "I previously worked at Grab where I led the Grab for Work project." - - Lyft was Grab's sister company! In fact they even had a partnership in the past. Most Lyft engineers would have heard of Grab before and mentioning this catches their attention. + - Lyft was Grab's sibling company! In fact they even had a partnership in the past. Most Lyft engineers would have heard of Grab before and mentioning this catches their attention. - "I built the project with another engineer over the period of 4 months on a React/Redux and Golang stack." - Acknowledge that you work with others. Building a non-trivial system with just 2 people in 3 months is quite good for a non-trivial system. Lyft also uses Golang for their high performance systems. diff --git a/contents/star-format.md b/contents/star-format.md index 77117f64..8918a82e 100644 --- a/contents/star-format.md +++ b/contents/star-format.md @@ -18,7 +18,7 @@ Here's an example of how the STAR format can be used to answer the question: **" ### Situation -> "I was the team lead of a school project about building a social network mobile web app. Our designer's midterms were approaching and didn't have time to produce the mockups. Our front-end person was rushing him for the mockups so that he could proceed with his work, and that was stressing the designer out. The atmosphere in the team was tense." +> "I was the team lead of a school project about building a social network mobile web app. Our designer's midterms were approaching and didn't have time to produce the mockups. Our front-end person was rushing them for the mockups so that they could proceed with their work, and that was stressing the designer out. The atmosphere in the team was tense." ### Task @@ -26,15 +26,15 @@ Here's an example of how the STAR format can be used to answer the question: **" ### Action -> "I spoke to the front-end developer to ask him why he was rushing the designer for the designs. He said that he wanted the designs early because it would be a waste of time rebuilding if the designer designed something different eventually. I explained to him that the midterm dates were out of the designer's control and we had to be more understanding about each other's schedules. +> "I spoke to the front-end developer to ask them why they was rushing the designer for the designs. They said that they wanted the designs early because it would be a waste of time rebuilding if the designer designed something different eventually. I explained to them that the midterm dates were out of the designer's control and we had to be more understanding about each other's schedules. > -> I spoke to the designer to get a rough idea of what he had in mind and asked him when he could commit to producing the high-fidelity designs. He replied that he could start on them as soon as his midterms were over. I explained to him why the front-end developer was pushing him for the mockups, and that the front-end developer had no ill intentions and simply wanted the project to succeed. +> I spoke to the designer to get a rough idea of what they had in mind and asked them when they could commit to producing the high-fidelity designs. They replied that they could start on them as soon as their midterms were over. I explained to them why the front-end developer was pushing them for the mockups, and that the front-end developer had no ill intentions and simply wanted the project to succeed. > -> As someone with some experience in UI/UX design, I came up with wireframe mocks, ran them by the designer for approval, then passed them to the front-end developer to start building. I encouraged the front-end developer to use placeholders and not be too concerned about the details for now. We could build the non-UI parts first (authentication, hook up with APIs) and tweak pixels and add polish later on. The front-end developer agreed and went ahead with the approach. I explained to the front-end developer that the designer will pass us the mockups after his midterm, by <DATE>." +> As someone with some experience in UI/UX design, I came up with wireframe mocks, ran them by the designer for approval, then passed them to the front-end developer to start building. I encouraged the front-end developer to use placeholders and not be too concerned about the details for now. We could build the non-UI parts first (authentication, hook up with APIs) and tweak pixels and add polish later on. The front-end developer agreed and went ahead with the approach. I explained to the front-end developer that the designer will pass us the mockups after their midterm, by <DATE>." ### Result -> "When our designer ended midterms, he came back with beautiful mockups that fit well into the wireframes. Our front-end developer implemented them with great care to detail. We ended up scoring top marks for the project and became a great team." +> "When our designer ended midterms, they came back with beautiful mockups that fit well into the wireframes. Our front-end developer implemented them with great care to detail. We ended up scoring top marks for the project and became a great team." ### Qualities @@ -44,4 +44,4 @@ Through the above, experienced interviewers can extract the following qualities - **Willingness** - to wear multiple hats: Picked up the role of the designer and came up with wireframes - **Project management** - Able to unblock the project by changing approaches midway to great effectiveness - **Conflict management** - Explain to parties involved in the conflict and make sure no hard feelings remain -- **Hold people accountable** - Get a confirmation date as to when the designer can produce the mockups and hold him accountable +- **Hold people accountable** - Get a confirmation date as to when the designer can produce the mockups and hold them accountable diff --git a/contents/understanding-compensation.md b/contents/understanding-compensation.md index ab06af6e..c6d9d11e 100644 --- a/contents/understanding-compensation.md +++ b/contents/understanding-compensation.md @@ -31,11 +31,11 @@ Bonuses are usually paid on a semi-annual basis and are typically dependent on a ### Examples -Bob is a Software Engineer fresh out of college. His base salary is $100,000, is a fresh grad (seniority multiplier: 10%), crushed expectations for the half (individual performance multiplier: 200%) and his company did pretty well (company performance multiplier: 120%). For that half, his bonus will be as follows: +Bob is a Software Engineer fresh out of college. Their base salary is $100,000, is a fresh grad (seniority multiplier: 10%), crushed expectations for the half (individual performance multiplier: 200%) and their company did pretty well (company performance multiplier: 120%). For that half, their bonus will be as follows: **Bonus:** 100,000 x 50% (half a year) x 10% (seniority) x 200% (individual performance) x 120% (company performance) = 12000 -Alice is an Engineering Manager with 10 years of professional experience. Her base salary is $220,000, is an experienced engineering manager (seniority multiplier: 20%), exceeded expectations for the half (individual performance multiplier: 150%) and her company did pretty awesome (company performance multiplier: 130%). For that half, her bonus will be as follows: +Alice is an Engineering Manager with 10 years of professional experience. Them base salary is $220,000, is an experienced engineering manager (seniority multiplier: 20%), exceeded expectations for the half (individual performance multiplier: 150%) and them company did pretty awesome (company performance multiplier: 130%). For that half, them bonus will be as follows: **Bonus:** 220,000 x 50% (half a year) x 20% (seniority) x 150% (individual performance) x 130% (company performance) = 42900 diff --git a/experimental/design/news-feed.md b/experimental/design/news-feed.md index 2c729f5f..11a8df9d 100644 --- a/experimental/design/news-feed.md +++ b/experimental/design/news-feed.md @@ -58,7 +58,7 @@ TODO > There are two basic objects: user and feed. For user object, we can store userID, name, registration date and so on so forth. And for feed object, there are feedId, feedType, content, metadata etc., which should support images and videos as well. > -> If we are using a relational database, we also need to model two relations: user-feed relation and friend relation. The former is pretty straightforward. We can create a user-feed table that stores userID and corresponding feedID. For a single user, it can contain multiple entries if he has published many feeds. +> If we are using a relational database, we also need to model two relations: user-feed relation and friend relation. The former is pretty straightforward. We can create a user-feed table that stores userID and corresponding feedID. For a single user, it can contain multiple entries if they has published many feeds. > > For friend relation, adjacency list is one of the most common approaches. If we see all the users as nodes in a giant graph, edges that connect nodes denote friend relation. We can use a friend table that contains two userIDs in each entry to model the edge (friend relation). By doing this, most operations are quite convenient like fetch all friends of a user, check if two people are friends. > @@ -97,7 +97,7 @@ TODO - First select features/signals that are relevant and then figure out how to combine them to calculate a final score. - How do you show the relevant posts that the user is interested in? - - Chronological - While a chronological approach works, it may not be the most engaging approach. For example, if a person posts 30 times within the last hour, his followers will have their news feed clogged up with his posts. Maybe set a cap on the number of time a person's posts can appear within the feed. + - Chronological - While a chronological approach works, it may not be the most engaging approach. For example, if a person posts 30 times within the last hour, their followers will have their news feed clogged up with their posts. Maybe set a cap on the number of time a person's posts can appear within the feed. - Popularity - How many likes and comments does the post have? Does the user usually like posts by that person? - How do you determine which are the more important posts? A user might be more interested in a few-hour old post from a good friend than a very recent post from an acquaintance. - A common strategy is to calculate a post score based on various features and rank posts by its score. diff --git a/website/blog/2019-11-03-are-front-end-development-enough-for-a-career.md b/website/blog/2019-11-03-are-front-end-development-enough-for-a-career.md index 4fffd487..4fa2130b 100644 --- a/website/blog/2019-11-03-are-front-end-development-enough-for-a-career.md +++ b/website/blog/2019-11-03-are-front-end-development-enough-for-a-career.md @@ -40,7 +40,7 @@ The web is incredibly cross-platform! ## Jack of all trades, master of one -However, I think that being a Front End development in many regards, is considered a specialized position. That's why it's important to be "T-shaped". I first got introduced to this term through my ex-manager at Grab, Tim Goh. He advised me to have a specialization (front end), yet still know a bit about everything. In other words, you are strong in your core fundamentals, but you also specialize in a particular area. +However, I think that being a Front End development in many regards, is considered a specialized position. That's why it's important to be "T-shaped". I first got introduced to this term through my ex-manager at Grab, Tim Goh. They advised me to have a specialization (front end), yet still know a bit about everything. In other words, you are strong in your core fundamentals, but you also specialize in a particular area. This is good advice and it's not new advice. In most university courses, students are expected to study the fundamental courses before choosing their area of specialization. In the context of a School of Computing in National University of Singapore, students start their in school by taking basic classes in Algorithms, Data Structures, Software Engineering, Operating Systems, Computer Networks, before choosing their specialization in deeper areas like Compilers, Computer Graphics, AI and Machine Learning, Media, Networking and more. diff --git a/website/blog/2021-04-12-importance-of-communicating-effectively-as-an-engineer.md b/website/blog/2021-04-12-importance-of-communicating-effectively-as-an-engineer.md index f75265e9..46c4097c 100644 --- a/website/blog/2021-04-12-importance-of-communicating-effectively-as-an-engineer.md +++ b/website/blog/2021-04-12-importance-of-communicating-effectively-as-an-engineer.md @@ -48,11 +48,11 @@ Takeaway — Make a noise! **A good product that many people use has more impact Communication has a huge impact on one's performance. If you aren't able to effectively update your manager on what you are doing, it is hard for them to help you stay on track to ensure you meet expectations for the half. At Facebook, Communication is explicitly stated as an evaluation axis of our performance review, but realistically, every axis involves communication. We saw how effective communication helps expand one's project impact in the Sentinel example above. Better engineering practices should be communicated to folks who work on the same code base so as to efficiently deliver products of excellent implementation quality. Strong communication also leads to successful conflict resolution, mentorship and recruiting. -Here's a scenario on how communication impacts calibrations - Alice's manager put her up for promotion to Staff Engineer after successfully delivering on an impactful project. However, due to lack of communication and visibility about her project, it's the first time other managers in the room heard about this project and many raised questions regarding it due to their unfamiliarity with it. This made the calibration process much harder than it should have been had Alice communicated about her project broadly earlier on. +Here's a scenario on how communication impacts calibrations - Alice's manager put them up for promotion to Staff Engineer after successfully delivering on an impactful project. However, due to lack of communication and visibility about them project, it's the first time other managers in the room heard about this project and many raised questions regarding it due to their unfamiliarity with it. This made the calibration process much harder than it should have been had Alice communicated about them project broadly earlier on. ### Influence -Influence is a core skill you need to develop as you grow your career, and communication is at the core of it. Senior folks are leaders and influential and are effective communicators. This is true regardless of IC (individual contributor) track or management track. Senior Engineers are expected to be able to influence the engineering culture in the broader team and possess strong communication skills to be able to explain technical information effectively. Recently I attended a meeting with a very senior Software Engineer and was blown away by how he managed to explain the concept of cookies in such simple terms to the non-technical folks in the meeting and how effective communication helps you to get things done. For those who are interested in embarking on the manager track in future, please also know that most of an engineering manager's job involves communication. +Influence is a core skill you need to develop as you grow your career, and communication is at the core of it. Senior folks are leaders and influential and are effective communicators. This is true regardless of IC (individual contributor) track or management track. Senior Engineers are expected to be able to influence the engineering culture in the broader team and possess strong communication skills to be able to explain technical information effectively. Recently I attended a meeting with a very senior Software Engineer and was blown away by how they managed to explain the concept of cookies in such simple terms to the non-technical folks in the meeting and how effective communication helps you to get things done. For those who are interested in embarking on the manager track in future, please also know that most of an engineering manager's job involves communication. ### Foster alignment and save effort down the road @@ -60,7 +60,7 @@ At large companies of similar scale as Facebook, it's not uncommon for two teams ### Facilitate project planning and ensure timelines are met -Imagine this extreme (but still plausible) scenario - Bob and his team have spent a few months working on a huge project which was slated to launch next week. However, the project is only half-completed due to unforeseen technical difficulties and lack of manpower. If Bob had communicated about the difficulties and progress earlier, his manager could have allocated more manpower earlier to help out, and the team would probably be in a better position to meet their deadlines. This scenario is unrealistic at Facebook in the sense that such issues would probably be caught earlier because of weekly syncs and progress update posts. However, it is still possible for smaller projects where there aren't any/many syncs. +Imagine this extreme (but still plausible) scenario - Bob and their team have spent a few months working on a huge project which was slated to launch next week. However, the project is only half-completed due to unforeseen technical difficulties and lack of personpower. If Bob had communicated about the difficulties and progress earlier, their manager could have allocated more personpower earlier to help out, and the team would probably be in a better position to meet their deadlines. This scenario is unrealistic at Facebook in the sense that such issues would probably be caught earlier because of weekly syncs and progress update posts. However, it is still possible for smaller projects where there aren't any/many syncs. ## Ways to communicate effectively diff --git a/website/blog/2021-08-19-facebook-career-questions-and-answers.md b/website/blog/2021-08-19-facebook-career-questions-and-answers.md index ff9dd23e..5bfb8f1a 100644 --- a/website/blog/2021-08-19-facebook-career-questions-and-answers.md +++ b/website/blog/2021-08-19-facebook-career-questions-and-answers.md @@ -163,7 +163,7 @@ As of writing, internships in FB SG are run annually so if you fail this year yo For all roles, there should be an initial contact (e.g. phone call) with recruiters. For interns, it would be 2 rounds of online coding interviews where the focus is on DSA. For fresh graduates, it would be 2 rounds of online coding interviews and 1 behavioral round. -### Based on your past experience, if a candidate does not get full marks for the online coding test, what are the chances of him or her getting a face to face interview? Just curious about the level of competition haha (This is because I'm not that worried about whiteboard interviews but afraid that I may not even get a chance to go through it) +### Based on your past experience, if a candidate does not get full marks for the online coding test, what are the chances of them or them getting a face to face interview? Just curious about the level of competition haha (This is because I'm not that worried about whiteboard interviews but afraid that I may not even get a chance to go through it) I don't even think there's an online coding test for Facebook. Can't answer this. diff --git a/website/blog/2021-08-28-front-end-career-questions.md b/website/blog/2021-08-28-front-end-career-questions.md index 8a691aea..8848ec14 100644 --- a/website/blog/2021-08-28-front-end-career-questions.md +++ b/website/blog/2021-08-28-front-end-career-questions.md @@ -31,6 +31,6 @@ I really like all aspects of Front End development, maybe except optimizing perf Learn your fundamentals well. There are many UI and CSS libraries out there, but a good Front End developer still needs to know how to build a website without them. Peek beneath the abstraction layers and understand the problems these libraries are trying to solve, do not use them blindly. Keep building stuff - try to build a simple version of the libraries you frequently use, build interesting user interfaces and products, etc. -### What do you think about developing breadth-wise vs depth-wise? For example, do you think it's important for a software engineer to know more about other fields besides the end he/she is currently working at? In particular, what do you think about an Front End engineer that knows BE (i.e. a full-stack developer), or an Front End engineer that knows mobile development (with the advent of React Native or Flutter)? +### What do you think about developing breadth-wise vs depth-wise? For example, do you think it's important for a software engineer to know more about other fields besides the end they/they is currently working at? In particular, what do you think about an Front End engineer that knows BE (i.e. a full-stack developer), or an Front End engineer that knows mobile development (with the advent of React Native or Flutter)? I somewhat answered this in another [blog post](/blog/are-front-end-development-skills-enough-for-a-career). Lemme know if your question isn't answered after reading it. diff --git a/website/blog/2021-10-30-my-experience-working-as-a-meta-engineer.md b/website/blog/2021-10-30-my-experience-working-as-a-meta-engineer.md index d6d5be78..83d325df 100644 --- a/website/blog/2021-10-30-my-experience-working-as-a-meta-engineer.md +++ b/website/blog/2021-10-30-my-experience-working-as-a-meta-engineer.md @@ -82,7 +82,7 @@ Every Meta employee has 21 days of leave/paid time off every year and this year ## Transfers and mobility -It is extremely easy to move around in Meta because Meta understands that mobility is important to the happiness and welfare of employees. People move around quite often and people are eligible to consider team changes from their second year at the company onwards. Meta is a large company comprising of many organizations and each organization has their own unique culture. It can be refreshing to move to another part of the company, working on different domains, different products, experiencing a slightly different engineering culture, yet still be productive because you are using the same engineering tools as before. When engineers move around the company, positive things can happen - they bring the good practices from their previous organizations to the new organizations, networks are strengthened and new connections are formed. Because Meta has offices around the globe, it is also possible to transfer to different countries as long as there are no work authorization issues. Personally I relocated back to Meta Singapore office after working for 2 years in Meta Menlo Park and my manager has worked in **4 different offices** (Menlo Park, London, New York, Singapore) throughout her 9 years at Meta! +It is extremely easy to move around in Meta because Meta understands that mobility is important to the happiness and welfare of employees. People move around quite often and people are eligible to consider team changes from their second year at the company onwards. Meta is a large company comprising of many organizations and each organization has their own unique culture. It can be refreshing to move to another part of the company, working on different domains, different products, experiencing a slightly different engineering culture, yet still be productive because you are using the same engineering tools as before. When engineers move around the company, positive things can happen - they bring the good practices from their previous organizations to the new organizations, networks are strengthened and new connections are formed. Because Meta has offices around the globe, it is also possible to transfer to different countries as long as there are no work authorization issues. Personally I relocated back to Meta Singapore office after working for 2 years in Meta Menlo Park and my manager has worked in **4 different offices** (Menlo Park, London, New York, Singapore) throughout them 9 years at Meta! For engineers, there are also temporary transfers which we call Hackamonths. Hackamonths are month-long projects proposed by teams where they welcome someone outside their team to work on. At the end of the hackamonth, the participating engineer could return back to their original team or stay on the new team. This provides engineers with the opportunity to try out work and the culture of their new teams before committing to a permanent move. diff --git a/website/blog/2021-12-23-front-end-vs-back-end-system-design-interviews.md b/website/blog/2021-12-23-front-end-vs-back-end-system-design-interviews.md index 7d9fc764..6ca46340 100644 --- a/website/blog/2021-12-23-front-end-vs-back-end-system-design-interviews.md +++ b/website/blog/2021-12-23-front-end-vs-back-end-system-design-interviews.md @@ -1,7 +1,7 @@ --- title: Front End vs. Back End System Design Interviews slug: front-end-vs-back-end-system-design-interviews -author: Zhenghao He +author: Zhenghao They author_title: Senior Software Engineer at Instacart author_url: https://twitter.com/he_zhenghao author_image_url: https://pbs.twimg.com/profile_images/1489749168767660032/M_us3Mu2_400x400.jpg