diff --git a/contents/algorithms/dynamic-programming.md b/contents/algorithms/dynamic-programming.md index c43e5caf..355d06ad 100644 --- a/contents/algorithms/dynamic-programming.md +++ b/contents/algorithms/dynamic-programming.md @@ -1,6 +1,6 @@ --- id: dynamic-programming -title: Dynamic Programming +title: Dynamic programming --- ## Study links diff --git a/contents/algorithms/linked-list.md b/contents/algorithms/linked-list.md index 1fc9c203..9fe156d0 100644 --- a/contents/algorithms/linked-list.md +++ b/contents/algorithms/linked-list.md @@ -1,6 +1,6 @@ --- id: linked-list -title: Linked List +title: Linked list --- ## Notes diff --git a/contents/algorithms/oop.md b/contents/algorithms/oop.md index b342b2ce..96c7ee2b 100644 --- a/contents/algorithms/oop.md +++ b/contents/algorithms/oop.md @@ -1,6 +1,6 @@ --- id: oop -title: Object-Oriented Programming +title: Object-oriented programming --- ## Sample questions diff --git a/contents/algorithms/sorting-searching.md b/contents/algorithms/sorting-searching.md index 01181156..383650e8 100644 --- a/contents/algorithms/sorting-searching.md +++ b/contents/algorithms/sorting-searching.md @@ -1,6 +1,6 @@ --- id: sorting-searching -title: Sorting and Searching +title: Sorting and searching --- ## Tips diff --git a/contents/behavioral-questions.md b/contents/behavioral-questions.md index fdaa5552..209512a0 100644 --- a/contents/behavioral-questions.md +++ b/contents/behavioral-questions.md @@ -1,7 +1,7 @@ --- id: behavioral-questions -title: Behavioral Interview Common Questions -sidebar_label: Common Questions +title: Behavioral interview common questions +sidebar_label: Common questions --- Here's a list of common behavioral questions to prepare for. If you prepare well for the general questions and apply the STAR format along with demonstrating qualities, you will be fine. diff --git a/contents/behavioral-round-overview.md b/contents/behavioral-round-overview.md index 21ef18da..8eb69890 100644 --- a/contents/behavioral-round-overview.md +++ b/contents/behavioral-round-overview.md @@ -1,6 +1,6 @@ --- id: behavioral-round-overview -title: Behavorial Round Overview +title: Behavorial round overview sidebar_label: Overview --- diff --git a/contents/best-practice-questions.md b/contents/best-practice-questions.md index 4e415260..bf1afec7 100644 --- a/contents/best-practice-questions.md +++ b/contents/best-practice-questions.md @@ -1,6 +1,6 @@ --- id: best-practice-questions -title: Best Practice Questions +title: Best practice questions --- Practicing is the best way to prepare for coding interviews. Years ago, I curated a list of the most important 75 questions on [LeetCode](https://leetcode.com). Many other LeetCode questions are a mash of the techniques from these individual questions. I used this list in my last job hunt to only do the important questions. @@ -33,7 +33,7 @@ In week 1, we will start off easy and do a mix of easy and medium questions on a - [Maximum Product Subarray](https://leetcode.com/problems/maximum-product-subarray/) - [Search in Rotated Sorted Array](https://leetcode.com/problems/search-in-rotated-sorted-array/) -## Week 2 - Data Structures +## Week 2 - Data structures The focus of week 2 is on linked lists, strings and matrix-based questions. The goal is to learn the common routines dealing with linked lists, traversing matrices and sequence analysis (arrays/strings) techniques such as sliding window. @@ -49,7 +49,7 @@ The focus of week 2 is on linked lists, strings and matrix-based questions. The - [Palindromic Substrings](https://leetcode.com/problems/palindromic-substrings/) - [Pacific Atlantic Water Flow](https://leetcode.com/problems/pacific-atlantic-water-flow/) -## Week 3 - Non-Linear Data Structures +## Week 3 - Non-linear data structures The focus of week 3 is on non-linear data structures like trees, graphs and heaps. You should be familiar with the various tree traversal (in-order, pre-order, post-order) algorithms and graph traversal algorithms such as breadth-first search and depth-first search. In my experience, using more advanced graph algorithms (Dijkstra's and Floyd-Warshall) is quite rare and usually not necessary. @@ -70,7 +70,7 @@ The focus of week 3 is on non-linear data structures like trees, graphs and heap - [Binary Tree Level Order Traversal](https://leetcode.com/problems/binary-tree-level-order-traversal/) - [Encode and Decode Strings (LeetCode Premium)](https://leetcode.com/problems/encode-and-decode-strings/) -## Week 4 - More Data Structures +## Week 4 - More data structures Week 4 builds up on knowledge from previous weeks but questions are of increased difficulty. Expect to see such level of questions during interviews. You get more practice on more advanced data structures such as (but not exclusively limited to) heaps and tries. @@ -93,7 +93,7 @@ Week 4 builds up on knowledge from previous weeks but questions are of increased - [Graph Valid Tree (LeetCode Premium)](https://leetcode.com/problems/graph-valid-tree/) - [Number of Connected Components in an Undirected Graph (LeetCode Premium)](https://leetcode.com/problems/number-of-connected-components-in-an-undirected-graph/) -## Week 5 - Dynamic Programming +## Week 5 - Dynamic programming Week 5 focuses on Dynamic Programming (DP) questions. Personally as an interviewer, I'm not a fan of DP questions as they are not really applicable to practical scenarios and frankly if I were made to do the tough DP questions during my interviews I'd not have gotten the job. However, companies like Google still ask DP questions and if joining Google is your dream, DP is unavoidable. diff --git a/contents/choosing-between-companies.md b/contents/choosing-between-companies.md index b85882a9..0e4c12b2 100644 --- a/contents/choosing-between-companies.md +++ b/contents/choosing-between-companies.md @@ -3,7 +3,7 @@ id: choosing-between-companies title: Choosing between companies --- -After pass the interviews and if have received multiple offers, congratulations on the feat! Now you're faced with yet another problem (albeit a good one!) of choosing between companies. Here we will provide some insights into the factors you should be considering when deciding on the company to join. Everyone is different and certain factors matter more/less to others, so only you can decide what is best for you. +If you have passed the interviews and received multiple offers, congratulations on the feat! Now you are faced with yet another problem (albeit a good one!) of choosing between companies. Here we will provide some insights into the factors you should be considering when deciding on the company to join. Every individual is different and certain factors matter more/less to others, so only you can decide what is best for you. Do your due diligence by researching on the companies before deciding! @@ -21,7 +21,7 @@ What does the company work on and is the company working on a domain you are int That said, each tech company is uniquely known for something and it's in their DNA. So if you are interested in specific areas and you are sure you can be able to work on them, the choice should be clearer: -- Meta - Social networks (FB, IG), Chat (WhatsApp, Messenger), VR stuff (Oculus) +- Meta - Social networks (Facebook, Instagram), Chat (WhatsApp, Messenger), VR stuff (Oculus) - Google - Search, Browsers, Maps, Cloud infrastructure (Google Cloud Platform), Google Suite - Amazon - Cloud infrastructure (Amazon Web Services), e-commerce - Microsoft - Operating Systems, Microsoft Office Suite @@ -29,32 +29,32 @@ That said, each tech company is uniquely known for something and it's in their D Personally I feel more motivated and productive if I'm working on products which I use as an external user as well, as I have a better understanding of the product from a user perspective which can potentially lead to better engineering and product decisions. -### Prospective Teams +### Prospective teams -While a company can be working on various products, some products are only worked on in certain offices.For example, Google Singapore primarily works on Payments and if you're only interested in working on search, Google Singapore wouldn't be that great of a fit (although it is definitely a possibility to transition to another part of the company in future). +While a company can be working on various products, some products are only worked on in certain offices. For example, Google Singapore primarily works on Payments and if you're only interested in working on search, Google Singapore wouldn't be that great of a fit, although it is definitely a possibility to relocate to another country in future while still remaining as a Google employee. More on that on the [Transfers and mobility](#transfers-and-mobility) section below. Do find out what products and teams your intended location works on so that you have a better idea of how your potential working life looks like if you were to join that company. -## Company Prospects +## Company prospects If you are awarded stocks, the company's prospects will affect your compensation! Is the company poised to be successful in the coming years or are there factors hindering the company's progress? -## Career Growth +## Career growth -How fast does the company promote its employees and does the company provide opportunities for its employees to grow? In smaller companies, you will get to wear multiple hats and build many products from 0 to 1. It's great for people who like to grow their product building skills and launch products quickly. However, technical growth might be limited due to the company's focus on product work and less on building infrastructure, which is usually only needed at scale. There's little need for a Principal Engineer in a small startup of 10 people where everyone is scrambling to build products. Career growth might be limited by the size and scope of the company and its suite of products. +How fast does the company promote its employees and does the company provide opportunities for its employees to grow? In smaller companies, you will get to wear multiple hats and build many products from 0 to 1. It's great for people who like to grow their product building skills and launch products quickly. However, technical growth might be limited due to the company's focus on product work and less on building infrastructure, which is usually only needed at scale. There's little need for a Principal Engineer in a small startup of 10 people where everyone is scrambling to build products. Career growth might be limited by the size and scope of the company and its product offerings. -Some companies promote their employees faster than the others. There's a saying that go to Google to rest and vest, go to Meta if you want to accelerate your career. I've found this to be quite accurate from what I experienced and looking at my peers at Google. At Meta, engineers are required to get from E3 to E4 within 2 years and E4 to E5 within 3 years. On the other hand, Google has a slower promotion cycle - the average engineer at Google takes more than 2 years to get from L3 to L4, more than 3 years to get from L4 to L5 and more than 4 years to get from L5 to L6. At Google the terminal level is L4 so there's no pressure to promote. None of my peers are L6 at Google but a few are already E6 at Meta and it is quite achievable. I think Google is a great place to learn to be excellent engineers. They require everything to be well-engineered, with design docs and full test coverage. +Some companies promote their employees faster than the others. There's a saying that go to Google to rest and vest, go to Meta if you want to accelerate your career. I've found this to be quite accurate from what I experienced and from looking at my peers at Google. At Meta, engineers are required to get from E3 to E4 within 2 years and E4 to E5 within 3 years. On the other hand, Google has a slower promotion cycle - the average engineer at Google takes more than 2 years to get from L3 to L4, more than 3 years to get from L4 to L5 and more than 4 years to get from L5 to L6. At Google, the terminal level is L4 so there's no pressure to promote. None of my peers are L6 at Google but a few are already E6 at Meta and it is quite achievable. In my opinion, Google is a great place to learn to be excellent engineers. They require everything to be well-engineered, with design docs and high test coverage. Meta is a great place for career-driven folks who don't mind working harder to accelerate their career path. -## Work-Life Balance +## Work-life balance -How long are employees required to work each week? How fast does the company move? How stressful is it to work at the company? Some Chinese companies famously [require employees to work 6 days a week](https://www.reuters.com/world/china/chinese-tech-workers-disclose-working-hours-criticism-996-2021-10-14/). +While the common practice is for employees to work 40 hours a week and 8 hours a day, some places are infamous for being more stressful and asks more time from their employees. Some Chinese companies famously [require employees to work 6 days a week](https://www.reuters.com/world/china/chinese-tech-workers-disclose-working-hours-criticism-996-2021-10-14/). Most tech employees do not get paid when they work overtime, so sometimes a more accurate way of calculating your salary is dollars per hour instead of the raw annual total compensations -Google is famous for being a company for moving slower and more senior folks to go rest-and-vest (your stocks) while [Microsoft scores a C+ for Work Life Balance](https://www.comparably.com/companies/microsoft/work-life-balance) in an employee survey. +Google is famous for being a company for moving slower and a place where people go to rest and vest (their stocks) while [Amazon scored a C- for work-life balance](https://www.comparably.com/companies/amazon/work-life-balance) in an employee survey. -## Company Culture +## Transfers and mobility -TODO +Does the company have offices around the globe where employees can possibly relocate to? This is obviously out of the question for smaller companies where there is only one headquarters, but some companies allow employees to be remote and some are even entirely remote! Meta, Google, Apple, and Stripe are examples of companies which have global presence and regional headquarters. At Meta and Google, mobility is extremely high given there are large engineering offices all across US, in London, Tel Aviv, and more recently, in Singapore. One of my managers at Meta has worked at **four** offices! Personally, I relocated from Meta/Facebook Menlo Park to Meta/Facebook Singapore right before COVID hit and a few of my Meta/Googler friends have done similar moves, some even moving from Singapore to the US. -## Transfers and Mobility +## Company culture TODO diff --git a/contents/coding-round-overview.md b/contents/coding-round-overview.md index 3815b013..cf0b0f4c 100644 --- a/contents/coding-round-overview.md +++ b/contents/coding-round-overview.md @@ -1,6 +1,6 @@ --- id: coding-round-overview -title: Coding Round Overview +title: Coding round overview sidebar_label: Overview --- diff --git a/contents/coding-signals.md b/contents/coding-signals.md index 67ecbc17..aafbc46a 100644 --- a/contents/coding-signals.md +++ b/contents/coding-signals.md @@ -1,6 +1,6 @@ --- id: coding-signals -title: Coding Signals +title: Coding signals --- The point of interviews is for interviewers to extract signals from certain candidate behaviors. In coding interviews, the signals can be broadly classified into the following categories: Problem Solving, Technical Competency, Testing, and Communication. diff --git a/contents/cover-letter.md b/contents/cover-letter.md index 29ddfd2a..fa1ab927 100644 --- a/contents/cover-letter.md +++ b/contents/cover-letter.md @@ -1,6 +1,6 @@ --- id: cover-letter -title: Cover Letter +title: Cover letter --- - A short introduction describing who you are and what you're looking for diff --git a/contents/during-coding-interview.md b/contents/during-coding-interview.md index 5207ecbf..e3f18054 100644 --- a/contents/during-coding-interview.md +++ b/contents/during-coding-interview.md @@ -1,6 +1,6 @@ --- id: during-coding-interview -title: During the Coding Interview +title: During the coding interview --- Congratulations, you are ready to put your skills into practice! In a real coding interview, you will be given a technical question (or questions) by the interviewer, write code in a real-time collaborative editor (phone screen/virtual onsite) or on a whiteboard (onsite) to solve the problem within 30–45 minutes. This is where the real fun begins! diff --git a/contents/engineering-levels.md b/contents/engineering-levels.md index 024436ad..764ba246 100644 --- a/contents/engineering-levels.md +++ b/contents/engineering-levels.md @@ -1,6 +1,6 @@ --- id: engineering-levels -title: Engineering Levels +title: Engineering levels --- :::caution @@ -11,7 +11,7 @@ This section is still WIP. Feel free to contribute ideas at [our GitHub issue](h Understanding the various career levels for engineers is crucial because it helps to determine the compensation you should be receiving and also helps you to understand what is expected of you at that level. In most companies where the career levels have been defined, it would resemble something along the lines of: Junior → Software Engineer → Senior → Staff → Senior Staff → Principal → Fellow -## Career Levels +## Career levels ### Junior Software Engineer diff --git a/contents/how-to-apply.md b/contents/how-to-apply.md index a54a263e..f7bdafee 100644 --- a/contents/how-to-apply.md +++ b/contents/how-to-apply.md @@ -1,6 +1,6 @@ --- id: how-to-apply -title: How to Apply +title: How to apply --- ## Apply Directly diff --git a/contents/interview-formats.md b/contents/interview-formats.md index d4a896f7..9c8febd0 100644 --- a/contents/interview-formats.md +++ b/contents/interview-formats.md @@ -1,6 +1,6 @@ --- id: interview-formats -title: Interview Formats +title: Interview formats --- Interviews are a multi-stage process and each stage can consist of vastly different formats. diff --git a/contents/mock-interviews.md b/contents/mock-interviews.md index 0278fa4f..75ce3e56 100644 --- a/contents/mock-interviews.md +++ b/contents/mock-interviews.md @@ -1,6 +1,6 @@ --- id: mock-interviews -title: Mock Interviews +title: Mock interviews --- Interviewing is a skill that you can get better at. The steps mentioned above can be rehearsed over and over again until you have fully internalized them and following those steps become second nature to you. A good way to practice is to find a friend to partner with and the both of you can take turns to interview each other. diff --git a/contents/negotiation.md b/contents/negotiation.md index a7d53faf..f1da98f6 100644 --- a/contents/negotiation.md +++ b/contents/negotiation.md @@ -3,7 +3,7 @@ id: negotiation title: Negotiation --- -## Always Negotiate +## Always negotiate If you've received an offer (or even better, offers), congratulations! You may heave a huge sigh of relief and think that the toughest parts are over. Well yes, but not entirely! For most people, the reason they're finding a new job is to increase their salary, and salary negotiation is the last stretch in achieving that goal. @@ -29,7 +29,7 @@ Get paid more. Receive salary negotiation advice from [**Moonchaser**](https://w If you are not keen on paying for negotiation services and are a fan of courses, here's something for you - the [Grokking Comp Negotiation in Tech](https://www.educative.io/courses/grokking-comp-negotiation?aff=x23W) course, a text-based course where you can get information on each aspect of negotiation. **Disclaimer: I haven't tried this course before.** -## Ten Rules of Negotiation +## Ten rules of negotiation Key points extracted from "Ten Rules for Negotiating a Job Offer" [Part 1](http://haseebq.com/my-ten-rules-for-negotiating-a-job-offer/) and [Part 2](https://haseebq.com/how-not-to-bomb-your-offer-negotiation/) by Haseeb Qureshi. diff --git a/contents/picking-a-language.md b/contents/picking-a-language.md index 8aaa8bc6..8da1f65b 100644 --- a/contents/picking-a-language.md +++ b/contents/picking-a-language.md @@ -1,6 +1,6 @@ --- id: picking-a-language -title: Picking a Language +title: Picking a language --- Before anything else, you need to pick a programming language to do your interviews in. Most companies will let you code in any language you want, the only exception I know being Google, where they only allow candidates to pick from Java, C++, JavaScript or Python for their algorithmic coding interviews. diff --git a/contents/psychological-tricks.md b/contents/psychological-tricks.md index 610851b8..f5e01249 100644 --- a/contents/psychological-tricks.md +++ b/contents/psychological-tricks.md @@ -1,6 +1,6 @@ --- id: psychological-tricks -title: Psychological Tricks +title: Psychological tricks --- Here are some psychological tricks that will help you ace a job interview. diff --git a/contents/questions-to-ask.md b/contents/questions-to-ask.md index 7a75b049..2acba4b6 100644 --- a/contents/questions-to-ask.md +++ b/contents/questions-to-ask.md @@ -1,6 +1,6 @@ --- id: questions-to-ask -title: Questions To Ask +title: Questions To ask --- Here are some good questions to ask at the end of the interview, extracted from various sources. The ones in **bold** are the ones that tend to make the interviewer go "That's a good question" and pause and think for a bit. diff --git a/contents/resume-case-study.md b/contents/resume-case-study.md index 405c430d..aaebab7a 100644 --- a/contents/resume-case-study.md +++ b/contents/resume-case-study.md @@ -1,7 +1,7 @@ --- id: resume-case-study -title: Resume Case Study -sidebar_label: Case Study +title: Resume case study +sidebar_label: Case study --- import TeikjunResumeOldURL from '@site/static/img/teik-jun-resume-old.png'; import TeikjunResumeNewURL from '@site/static/img/teik-jun-resume-new.png'; diff --git a/contents/resume-sample.md b/contents/resume-sample.md index 5e45c006..0d7de201 100644 --- a/contents/resume-sample.md +++ b/contents/resume-sample.md @@ -1,6 +1,6 @@ --- id: resume-sample -title: Resume Sample +title: Resume sample sidebar_label: Sample --- diff --git a/contents/resume.md b/contents/resume.md index cca2dc9c..57c121ab 100644 --- a/contents/resume.md +++ b/contents/resume.md @@ -1,6 +1,6 @@ --- id: resume -title: Resume Checklist +title: Resume checklist sidebar_label: Checklist --- diff --git a/contents/star-format.md b/contents/star-format.md index 4c6dfa11..77117f64 100644 --- a/contents/star-format.md +++ b/contents/star-format.md @@ -1,6 +1,6 @@ --- id: star-format -title: STAR Format +title: STAR format --- ## What is STAR? diff --git a/contents/study-and-practice.md b/contents/study-and-practice.md index e4336f35..a67be7b7 100644 --- a/contents/study-and-practice.md +++ b/contents/study-and-practice.md @@ -1,9 +1,9 @@ --- id: study-and-practice -title: Study and Practice +title: Study and practice --- -## Recap CS fundamentals +## Recap computer science fundamentals If you have been out of college for a while, it is highly advisable to review CS fundamentals — Algorithms and Data Structures. Personally, I prefer to review as I practice, so I scan through my college notes and review the various algorithms as I work on algorithm problems from LeetCode and Cracking the Coding Interview. diff --git a/contents/system-design.md b/contents/system-design.md index a5869ec1..62e47b6f 100644 --- a/contents/system-design.md +++ b/contents/system-design.md @@ -1,6 +1,6 @@ --- id: system-design -title: System Design Interviews +title: System design interviews --- The objective of system design interviews is to evaluate a candidate's skill at designing real-world software systems involving multiple components. System design questions are typically given to more senior candidates (with a few years of experience). Interns aren't typically given system design questions as it is hard to expect interns to have sufficient and relevant industry experience to answer this type of questions well. @@ -24,7 +24,7 @@ System design content is still work-in-progress, but the following are some reso ::: -## Quality Courses +## Quality courses - ["Grokking the System Design Interview" by Educative](https://www.educative.io/courses/grokking-the-system-design-interview?aff=x23W) - This is probably the most famous system design interview course on the internet and what makes it different from most other courses out there is that it is purely text-based, which is great for people who refer reading over watching videos (such as myself!). It contains a repository of the popular system design problems along with a glossary of system design basics. I've personally completed this course and have recommended many others to use this. Highly recommended! - ["System Design Interview Course" by Exponent](https://www.tryexponent.com/courses/system-design-interview) - This course by Exponent covers system designs basics and has a huge database of popular system design questions with video explanations. Use this [referral link to get 10% off](https://www.tryexponent.com/refer/abdlb). In my opinion, Exponent is one of the most credible interview preparation resources out there as their resources are high quality and goes beyond Software Engineering roles. diff --git a/contents/understanding-compensation.md b/contents/understanding-compensation.md index 8b72b456..9b6049c8 100644 --- a/contents/understanding-compensation.md +++ b/contents/understanding-compensation.md @@ -1,6 +1,6 @@ --- id: understanding-compensation -title: Understanding Compensation +title: Understanding compensation --- Compensation is one of the largest factors when it comes to deciding between job offers. This section gives you a breakdown of the common components of compensation in the tech industry. diff --git a/website/sidebars.js b/website/sidebars.js index 060d221d..bee54736 100755 --- a/website/sidebars.js +++ b/website/sidebars.js @@ -4,7 +4,7 @@ module.exports = { Preface: ['introduction', 'landscape'], }, { - 'Resume Preparation': [ + 'Resume preparation': [ 'resume', 'resume-case-study', 'resume-sample', @@ -12,11 +12,11 @@ module.exports = { ], }, { - 'General Interview Tips': ['self-introduction', 'questions-to-ask'], + 'General interview tips': ['self-introduction', 'questions-to-ask'], }, 'interview-formats', { - 'Coding Interviews': [ + 'Coding interviews': [ 'coding-round-overview', 'picking-a-language', 'study-and-practice', @@ -55,7 +55,7 @@ module.exports = { }, 'system-design', { - 'Behavioral Interviews': [ + 'Behavioral interviews': [ 'behavioral-round-overview', 'star-format', 'behavioral-questions', @@ -63,10 +63,10 @@ module.exports = { ], }, { - 'Offer Negotiation': ['understanding-compensation', 'negotiation'], + 'Offer negotiation': ['understanding-compensation', 'negotiation'], }, { - 'Job Preparation': [ + 'Job preparation': [ 'choosing-between-companies', 'engineering-levels', // 'team-selection', diff --git a/website/src/css/custom.css b/website/src/css/custom.css index 5d1de198..6c2450ba 100755 --- a/website/src/css/custom.css +++ b/website/src/css/custom.css @@ -62,20 +62,42 @@ div[class^='announcementBar_'] { margin-bottom: 0 !important; } -.header-github-link:hover { +.navbar-icon:before { + background-repeat: no-repeat; + content: ''; + display: flex; + height: 24px; + width: 24px; + transition: all 300ms ease-in-out; +} + +.navbar-icon:hover { opacity: 0.6; } -.header-github-link::before { - content: ''; - width: 24px; - height: 24px; - display: flex; - background: url("data:image/svg+xml,%3Csvg viewBox='0 0 24 24' xmlns='http://www.w3.org/2000/svg'%3E%3Cpath d='M12 .297c-6.63 0-12 5.373-12 12 0 5.303 3.438 9.8 8.205 11.385.6.113.82-.258.82-.577 0-.285-.01-1.04-.015-2.04-3.338.724-4.042-1.61-4.042-1.61C4.422 18.07 3.633 17.7 3.633 17.7c-1.087-.744.084-.729.084-.729 1.205.084 1.838 1.236 1.838 1.236 1.07 1.835 2.809 1.305 3.495.998.108-.776.417-1.305.76-1.605-2.665-.3-5.466-1.332-5.466-5.93 0-1.31.465-2.38 1.235-3.22-.135-.303-.54-1.523.105-3.176 0 0 1.005-.322 3.3 1.23.96-.267 1.98-.399 3-.405 1.02.006 2.04.138 3 .405 2.28-1.552 3.285-1.23 3.285-1.23.645 1.653.24 2.873.12 3.176.765.84 1.23 1.91 1.23 3.22 0 4.61-2.805 5.625-5.475 5.92.42.36.81 1.096.81 2.22 0 1.606-.015 2.896-.015 3.286 0 .315.21.69.825.57C20.565 22.092 24 17.592 24 12.297c0-6.627-5.373-12-12-12'/%3E%3C/svg%3E") - no-repeat; +.navbar-icon-github:before { + background-image: url('/img/icons8-github.svg'); +} + +html[data-theme='dark'] .navbar-icon-github:before { + background-image: url('/img/icons8-github-light.svg'); + height: 28px; + width: 28px; +} + +.navbar-icon-twitter:before { + background-image: url('/img/icons8-twitter.svg'); +} + +html[data-theme='dark'] .navbar-icon-twitter:before { + background-image: url('/img/icons8-twitter-light.svg'); +} +.navbar-icon-facebook:before { + background-image: url('/img/icons8-facebook.svg'); } -html[data-theme='dark'] .header-github-link::before { - background: url("data:image/svg+xml,%3Csvg viewBox='0 0 24 24' xmlns='http://www.w3.org/2000/svg'%3E%3Cpath fill='white' d='M12 .297c-6.63 0-12 5.373-12 12 0 5.303 3.438 9.8 8.205 11.385.6.113.82-.258.82-.577 0-.285-.01-1.04-.015-2.04-3.338.724-4.042-1.61-4.042-1.61C4.422 18.07 3.633 17.7 3.633 17.7c-1.087-.744.084-.729.084-.729 1.205.084 1.838 1.236 1.838 1.236 1.07 1.835 2.809 1.305 3.495.998.108-.776.417-1.305.76-1.605-2.665-.3-5.466-1.332-5.466-5.93 0-1.31.465-2.38 1.235-3.22-.135-.303-.54-1.523.105-3.176 0 0 1.005-.322 3.3 1.23.96-.267 1.98-.399 3-.405 1.02.006 2.04.138 3 .405 2.28-1.552 3.285-1.23 3.285-1.23.645 1.653.24 2.873.12 3.176.765.84 1.23 1.91 1.23 3.22 0 4.61-2.805 5.625-5.475 5.92.42.36.81 1.096.81 2.22 0 1.606-.015 2.896-.015 3.286 0 .315.21.69.825.57C20.565 22.092 24 17.592 24 12.297c0-6.627-5.373-12-12-12'/%3E%3C/svg%3E") - no-repeat; +html[data-theme='dark'] .navbar-icon-facebook:before { + background-image: url('/img/icons8-facebook-light.svg'); + height: 28px; + width: 28px; } diff --git a/website/src/pages/index.js b/website/src/pages/index.js index 39292067..1d3cebb2 100755 --- a/website/src/pages/index.js +++ b/website/src/pages/index.js @@ -13,7 +13,7 @@ const BLIND_75_URL = const FEATURES = [ { - title: <>💯 Go From Zero to Hero, + title: <>💯 Go From zero to hero, description: ( <> Go from zero to tech interview hero with this handbook. No prior @@ -23,7 +23,7 @@ const FEATURES = [ link: '/introduction', }, { - title: <>📝 Curated Practice Questions, + title: <>📝 Curated practice questions, description: ( <> No one has time to practice a few hundred questions. We created the{' '} @@ -36,7 +36,7 @@ const FEATURES = [ link: '/best-practice-questions', }, { - title: <>📋 Interview Cheatsheet, + title: <>📋 Interview cheatsheet, description: ( <> Straight-to-the-point Do's and Don'ts during an interview. The battle is @@ -46,7 +46,7 @@ const FEATURES = [ link: '/cheatsheet', }, { - title: <>💁‍♀️ Practical Algorithm Tips, + title: <>💁‍♀️ Practical algorithm tips, description: ( <> Practical tips for every algorithm topic - common techniques and corner @@ -56,7 +56,7 @@ const FEATURES = [ link: '/algorithms/introduction', }, { - title: <>💬 Behavioral Questions, + title: <>💬 Behavioral questions, description: ( <> Check out what behavioral questions companies commonly ask and you can @@ -66,7 +66,7 @@ const FEATURES = [ link: '/behavioral-questions', }, { - title: <>🧪 Tested and Proven, + title: <>🧪 Tested and proven, description: ( <> Countless engineers have gotten their dream jobs with the help of Tech @@ -557,7 +557,7 @@ function SuccessStoriesSection() { 'text--center', styles.sectionTitle, )}> - Success Stories + Success stories {successStories.map((user) => (