www
/
www-new
11
3
Fork 5
Code Issues 58 Pull Requests 44 Projects Releases Wiki Activity

internship-guide #673

Closed
ry3zhu wants to merge 10 commits from internship-guide into main
pull from: internship-guide
merge into: www:main
Conversation 0 Commits 10 Files Changed 12 +219 -338
13 changed files with 219 additions and 338 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files
Showing only changes of commit 0445f3aabc - Show all commits

16
components/Navbar.tsx
View File

@ -98,7 +98,21 @@ const menu: Menu = [
},
{
name: "Internships",
route: "/resources/internships",
submenu: [
{
name: "Resume",
route: "/resources/internships/resume",
},
{
name: "Interview",
route: "/resources/internships/interview",
},
{
name: "Resources",
route: "/resources/internships/resources",
},
],
route: "/resources/internships/resume",
},
],
},

131
content/resources/internships/interview.mdx Normal file
View File

@ -0,0 +1,131 @@
## <span>Preparing for and Acing the Interview</span>
The interview process may seem daunting, but it allows for both you and the employer to determine if either of you are a perfect fit for each other. You can see it more of a bidirectional test as opposed to all the pressure being placed on you, the interviewee.
The purpose of the interview for an employer is to see if you’re the perfect fit, as mentioned, as well as truly get to know you and ask more detailed questions about anything, as you only have limited space to talk about yourself on a resume or a cover letter. This is also a time for you to truly demonstrate your mastery or proficiency in a skill.
As mentioned, the interview isn’t only for the employer, it’s also time for you to get to know more about the employer/company and determine if this job is truly something that suits you.
Most, if not all jobs, contain a portion known as the “Behavioural” interview. This is where you would talk about yourself, your interests, hobbies, the reason why you want this job, etc. This portion relies heavily on soft skills and you may need to practise with others to refine your skills.
For software development jobs, you may experience an additional portion known as the “Technical” interview. This is where your hard skills come in, and they’ll ask more specific questions about programming and computer science. You will also need to practise for this, which can be done alone as opposed to the behavioural portion which we recommend that you do with others.
Check out some of our advice below!
### General Advice
- Make sure you understand the question before you answer
- It’s perfectly fine to ask the interviewer for further clarification or ask them to repeat themselves
- It’s also fine, and highly recommended, that you slow down and take time to understand the question in full detail, rather than jumping ahead and answering
- Find the right balance for length in your responses
- Your answers shouldn’t be too long nor should they be too short
- Be precise and to the point
- **DO NOT RAMBLE**
- Be confident in what you say, and stand by what you say
- It looks very bad if you keep backtracking and try to constantly reverse what you say
- If you begin to doubt your answers, **slow down** and think things over
- Be friendly, professional, enthusiastic and show that you’re passionate
- You want this job and the employer knows this
- Remember! The interviewer wants you to succeed, so make it easier for them by being friendly and professional
- Research about the company beforehand
- Ask questions throughout and at the end of the interview (unless specified)
- **ALWAYS BRING A QUESTION TO AN INTERVIEW**
- If you begin to run out of time, you can exclude asking questions
- Otherwise, it shows your interest in the position if you ask questions
- Some safe general questions you can ask include:
- What’s the work/team environment?
- What type of projects will I be working on/have other interns worked on?
- What do you like about (Company Name)?
- What technologies/tools are used here?
- Is this job remote, hybrid, or in-person?
- When will I hear back about this job?
- Don’t ask this question on WaterlooWorks unless it’s direct offer round, as you can refer to the co-op calendar with all the offer dates
- What is the expected salary/compensation?
- **ONLY ASK ON WATERLOOWORKS IF IT’S NOT SPECIFIED**
- CCA not only protects you, but they also recommend you ask
- Describe why you need to know, such as if it’s in-person and you need to consider living accommodations
- Try to word it in such as way that you may be concerned about living conditions as opposed to greed
- Lastly, **go into the interview with the right mindset!**
- More often than not, people walk into an interview being extremely nervous, which is valid but causes them to trip up and leads to the interview being less than ideal
- Breathe! Stay relaxed and grounded
- Whatever the outcome, this is another opportunity for you to practise your skills
### Behavioural
- There are tons of questions that you may face as part of the behavioural portion
- This is where you demonstrate your passion, interest, and ability to adapt, learn, and grow
- You should be able to describe every portion of your resume in detail
- More often than not, an interviewer may ask for a bit more clarification about a certain point on your resume
- We’ll cover a few of the common or trickiest questions, but there are a variety you can search up on the internet
### **“Tell me about/Introduce yourself”**
- This is the most common first question you will encounter at any interview
- Pitch/Sell yourself! Show all that’s great about you!
- Start by saying your name, your year, school, and program
- Talk about interests and hobbies, and tie them back to your interest and passion to the field
- Tell a very short story about yourself that allows the employer to see what drives you
- Especially if you may lack some skills, being able to demonstrate your desire to learn and grow may be much more impactful
- Example: Hi! I’m FirstName and I’m a 3rd year Computer Science student at the University of Waterloo! Ever since I was a little kid, I’ve always been curious about the world and how it works, from how a simple click on my smartphone can result in me seeing someone on the other side of the world, which is what led me to start programming and end up here at the University of Waterloo studying computer science. I’ve always had this passion to learn more and contribute to something bigger, which is why I’m here looking to join Company Inc. as a software developer!
### **Behaviour-based question**
- This often comes in the form of “Describe a time when…” or “Tell me about a time when…” or “Give me an example of…”
- The reason why this type of question is used is to see how you tackle a past situation, which may potentially arise in the future, these often include:
- Working under pressure
- Working in a team, especially with conflicts or disagreements
- Completing a task within a given deadline
- Approaching a difficult situation
- To answer these questions, you should use the STAR Method, which can be used to model your answer with the following:
- Situation
- Provide the interviewer with context and background information about the situation you faced
- Use the five Ws (Who, What, When, Where, Why, How)
- Task
- Describe what you needed to do, the goals you had, challenges you expected to face and any expectations of the task
- Action
- Describe what you did and how you did it in relation to tackling the task you mentioned
- Highlight tools and skills you used
- This should be the most extensive part of your answer
- Result
- Discuss the outcome of your actions, in relation to the task
- Describe any accomplishments from your actions, and what you learnt as a result of your actions
### **Negative questions**
- These are questions that usually come in the form of:
- “Tell me about a weakness you have.”
- “What is one time you made a mistake?”
- “Describe when you weren’t able to complete a task within a given deadline.”
- This question is not supposed to put you down, it’s more to test your ability to pull yourself out of a messy situation and be able to adapt, learn, and grow from adversity
- State the negative first, such as your weakness, then talk about how you’re using this weakness to learn and grow into something positive
- Avoid using certain answers that may be seen as more positive than negative or are too broad
- Some answers that are frowned upon are being a perfectionist, being a workaholic, or public speaking
### Technical
- This is where all the hard skills you mentioned on your resume are truly tested, in addition to your critical thinking and problem solving skills
- Depending on the job you apply to, you may be asked questions ranging from something that is extremely concrete to something that is extremely conceptual
- An example of a more concrete question would be “Demonstrate how you would call this API, which returns an array of objects, as a list in React?” or “Determine the number of prime numbers from 2 to N”
- An example of a more conceptual question would be “Describe what a RESTful API is” or “What is the time complexity of deletion in an AVL tree”
#### **Concrete Questions**
- You will most likely encounter this type of technical question in your interview
- Read the question carefully, understand the full question and ask clarification questions about it before proceeding
- People often skip important details in the question, which may change large parameters of the question
- Slow down, get a full understanding, and ask the interviewer anything about the question, as they will fully understand the question and can answer any related questions that may cause you to get stuck
- If you’re given a choice of language, choose one that you’re most comfortable using
- Discuss your approach to the problem prior to beginning
- Wait until the interviewer says you can begin, as they may not have everything set up for you to do the question
- While you’re doing the question, **THINK OUT LOUD**
- The interviewer is more concerned about the process as opposed to the answer
- Even if you make mistakes in your code, if you voice your thoughts, the interviewer may spot errors that are silly mistakes (which may be penalised less than if they didn’t know)
- This also allows the interviewer to help you if you get stuck
- Run some test cases and edges cases, and discuss those edge cases
- There are plenty of websites where you can practise and test yourself prior to the interview, such as LeetCode
#### **Conceptual Questions**
- A lot of these questions are trivia based, where you need extensive knowledge on a given technology, tool, framework, data structure, etc.
- Google is a good resource to go to for these types of questions, as there are a variety of questions that could be asked for your specific job
- Try your best to answer them to the best of your ability, and even if you’re unsure, it’s fine to make an educated guess

48
content/resources/internships/interview/behavioural.mdx
View File

@ -1,48 +0,0 @@
- There are tons of questions that you may face as part of the behavioural portion
- This is where you demonstrate your passion, interest, and ability to adapt, learn, and grow
- You should be able to describe every portion of your resume in detail
- More often than not, an interviewer may ask for a bit more clarification about a certain point on your resume
- We’ll cover a few of the common or trickiest questions, but there are a variety you can search up on the internet
### **“Tell me about/Introduce yourself”**
- This is the most common first question you will encounter at any interview
- Pitch/Sell yourself! Show all that’s great about you!
- Start by saying your name, your year, school, and program
- Talk about interests and hobbies, and tie them back to your interest and passion to the field
- Tell a very short story about yourself that allows the employer to see what drives you
- Especially if you may lack some skills, being able to demonstrate your desire to learn and grow may be much more impactful
- Example: Hi! I’m FirstName and I’m a 3rd year Computer Science student at the University of Waterloo! Ever since I was a little kid, I’ve always been curious about the world and how it works, from how a simple click on my smartphone can result in me seeing someone on the other side of the world, which is what led me to start programming and end up here at the University of Waterloo studying computer science. I’ve always had this passion to learn more and contribute to something bigger, which is why I’m here looking to join Company Inc. as a software developer!
### **Behaviour-based question**
- This often comes in the form of “Describe a time when…” or “Tell me about a time when…” or “Give me an example of…”
- The reason why this type of question is used is to see how you tackle a past situation, which may potentially arise in the future, these often include:
- Working under pressure
- Working in a team, especially with conflicts or disagreements
- Completing a task within a given deadline
- Approaching a difficult situation
- To answer these questions, you should use the STAR Method, which can be used to model your answer with the following:
- Situation
- Provide the interviewer with context and background information about the situation you faced
- Use the five Ws (Who, What, When, Where, Why, How)
- Task
- Describe what you needed to do, the goals you had, challenges you expected to face and any expectations of the task
- Action
- Describe what you did and how you did it in relation to tackling the task you mentioned
- Highlight tools and skills you used
- This should be the most extensive part of your answer
- Result
- Discuss the outcome of your actions, in relation to the task
- Describe any accomplishments from your actions, and what you learnt as a result of your actions
### **Negative questions**
- These are questions that usually come in the form of:
- “Tell me about a weakness you have.”
- “What is one time you made a mistake?”
- “Describe when you weren’t able to complete a task within a given deadline.”
- This question is not supposed to put you down, it’s more to test your ability to pull yourself out of a messy situation and be able to adapt, learn, and grow from adversity
- State the negative first, such as your weakness, then talk about how you’re using this weakness to learn and grow into something positive
- Avoid using certain answers that may be seen as more positive than negative or are too broad
- Some answers that are frowned upon are being a perfectionist, being a workaholic, or public speaking

35
content/resources/internships/interview/general.mdx
View File

@ -1,35 +0,0 @@
- Make sure you understand the question before you answer
- It’s perfectly fine to ask the interviewer for further clarification or ask them to repeat themselves
- It’s also fine, and highly recommended, that you slow down and take time to understand the question in full detail, rather than jumping ahead and answering
- Find the right balance for length in your responses
- Your answers shouldn’t be too long nor should they be too short
- Be precise and to the point
- **DO NOT RAMBLE**
- Be confident in what you say, and stand by what you say
- It looks very bad if you keep backtracking and try to constantly reverse what you say
- If you begin to doubt your answers, **slow down** and think things over
- Be friendly, professional, enthusiastic and show that you’re passionate
- You want this job and the employer knows this
- Remember! The interviewer wants you to succeed, so make it easier for them by being friendly and professional
- Research about the company beforehand
- Ask questions throughout and at the end of the interview (unless specified)
- **ALWAYS BRING A QUESTION TO AN INTERVIEW**
- If you begin to run out of time, you can exclude asking questions
- Otherwise, it shows your interest in the position if you ask questions
- Some safe general questions you can ask include:
- What’s the work/team environment?
- What type of projects will I be working on/have other interns worked on?
- What do you like about (Company Name)?
- What technologies/tools are used here?
- Is this job remote, hybrid, or in-person?
- When will I hear back about this job?
- Don’t ask this question on WaterlooWorks unless it’s direct offer round, as you can refer to the co-op calendar with all the offer dates
- What is the expected salary/compensation?
- **ONLY ASK ON WATERLOOWORKS IF IT’S NOT SPECIFIED**
- CCA not only protects you, but they also recommend you ask
- Describe why you need to know, such as if it’s in-person and you need to consider living accommodations
- Try to word it in such as way that you may be concerned about living conditions as opposed to greed
- Lastly, **go into the interview with the right mindset!**
- More often than not, people walk into an interview being extremely nervous, which is valid but causes them to trip up and leads to the interview being less than ideal
- Breathe! Stay relaxed and grounded
- Whatever the outcome, this is another opportunity for you to practise your skills

13
content/resources/internships/interview/preface.mdx
View File

@ -1,13 +0,0 @@
## <span>Preparing for and Acing the Interview</span>
The interview process may seem daunting, but it allows for both you and the employer to determine if either of you are a perfect fit for each other. You can see it more of a bidirectional test as opposed to all the pressure being placed on you, the interviewee.
The purpose of the interview for an employer is to see if you’re the perfect fit, as mentioned, as well as truly get to know you and ask more detailed questions about anything, as you only have limited space to talk about yourself on a resume or a cover letter. This is also a time for you to truly demonstrate your mastery or proficiency in a skill.
As mentioned, the interview isn’t only for the employer, it’s also time for you to get to know more about the employer/company and determine if this job is truly something that suits you.
Most, if not all jobs, contain a portion known as the “Behavioural” interview. This is where you would talk about yourself, your interests, hobbies, the reason why you want this job, etc. This portion relies heavily on soft skills and you may need to practise with others to refine your skills.
For software development jobs, you may experience an additional portion known as the “Technical” interview. This is where your hard skills come in, and they’ll ask more specific questions about programming and computer science. You will also need to practise for this, which can be done alone as opposed to the behavioural portion which we recommend that you do with others.
Check out some of our advice below!

26
content/resources/internships/interview/technical.mdx
View File

@ -1,26 +0,0 @@
- This is where all the hard skills you mentioned on your resume are truly tested, in addition to your critical thinking and problem solving skills
- Depending on the job you apply to, you may be asked questions ranging from something that is extremely concrete to something that is extremely conceptual
- An example of a more concrete question would be “Demonstrate how you would call this API, which returns an array of objects, as a list in React?” or “Determine the number of prime numbers from 2 to N”
- An example of a more conceptual question would be “Describe what a RESTful API is” or “What is the time complexity of deletion in an AVL tree”
#### **Concrete Questions**
- You will most likely encounter this type of technical question in your interview
- Read the question carefully, understand the full question and ask clarification questions about it before proceeding
- People often skip important details in the question, which may change large parameters of the question
- Slow down, get a full understanding, and ask the interviewer anything about the question, as they will fully understand the question and can answer any related questions that may cause you to get stuck
- If you’re given a choice of language, choose one that you’re most comfortable using
- Discuss your approach to the problem prior to beginning
- Wait until the interviewer says you can begin, as they may not have everything set up for you to do the question
- While you’re doing the question, **THINK OUT LOUD**
- The interviewer is more concerned about the process as opposed to the answer
- Even if you make mistakes in your code, if you voice your thoughts, the interviewer may spot errors that are silly mistakes (which may be penalised less than if they didn’t know)
- This also allows the interviewer to help you if you get stuck
- Run some test cases and edges cases, and discuss those edge cases
- There are plenty of websites where you can practise and test yourself prior to the interview, such as LeetCode
#### **Conceptual Questions**
- A lot of these questions are trivia based, where you need extensive knowledge on a given technology, tool, framework, data structure, etc.
- Google is a good resource to go to for these types of questions, as there are a variety of questions that could be asked for your specific job
- Try your best to answer them to the best of your ability, and even if you’re unsure, it’s fine to make an educated guess

0
content/resources/internships/resources/index.mdx → content/resources/internships/resources.mdx
View File

51
content/resources/internships/resume/content.mdx → content/resources/internships/resume.mdx
View File

@ -1,3 +1,54 @@
## <span>Drafting your resume</span>
Your resume is the first thing an employer sees and the main thing that the employer will use to base their decision to interview you off of. You will need to make a good first impression to show that you’re the ideal candidate and that you have all the skills and qualifications necessary for the jobs you’re applying for.
Although anyone can state that they have the necessary qualifications and skills for a given job, you must demonstrate your ability through past experiences and/or projects, and describe them in detail to cement your skills.
### General Advice
- Follow the KISS principle
- KISS - Keep it simple, stupid!
- Often times, people try to cram in as much information, but being direct and straight to the point makes it easier to read
- The employer, more often than not, has hundreds of resume to go through and may only have a few seconds to read through an entire resume, so simplicity is often preferred as extra details may be overlooked
- All the description you include on your resume should be short, simple, concise, and to the point
- Make sure they’re relevant to the job posting
- It’s common for descriptions to start with a verb
- Highlight any metrics as it’s easy for people to understand
- Bold these in your resume so they catch the attention of the employer
### Template and Styling
- There’s no one template to follow or one template you should use
- There are countless templates you can find online, such as some on Overleaf, on Microsoft Word, etc.
- Some people might want to try to “game the system” by optimising for ATS (Applicant Tracking Systems), but there’s no correct answer for this
- There’s no one text editing software to use
- There’s a debate between using LaTeX as opposed to a WYSIWYG (What you see is what you get) word editor like Microsoft Word
- Using one or the other may have slight advantages, but overall, they make no difference
- The only answer is to use one that you’re comfortable using, as it’s just best to create something that someone can read
- You should use a **single** A4 or Letter page, and be able to fit everything on this one page
- Most people prefer to use narrow margins (1.27cm/0.5”) to fit everything in; however, it is safe to use normal margins (2.54cm/1”)
- Font selection is not much of a concern; however, keep it readable and professional
- This means avoiding fonts such as Comic Sans
- The argument between Sans Serif and Serif fonts doesn’t matter too much, readability matters the most
- Fill your page as much as you can!
- Leaving empty space may leave a bad impression, as it may look like you may not be interested and it doesn’t give an employer enough information to base a decision off of
- Look at the **Sections to Include** section for information to include that you may be missing
- If you’re running out of space on your page…
- Decrease your font size (while maintaining readability)
- So long as your page is readable, it’s perfectly fine to decrease your font size
- Make sure it’s not **cramped** as it can be extremely difficult to distinguish multiple lines of text if the font is too small
- There’s no definitive answer for the minimum size of font you can set, as fonts vary in size, but somewhere between 8pt and 10pt would be considered the bare minimum to be readable
- Decrease spacing between text
- Look out for lines that may only contain a few words
- Some lines may break into multiple lines, with the last line that consist of only a few words
- Try to rephrase that whole point such that it takes up less space, through the removal of some filler words, unnecessary adjectives/adverbs, etc.
- Lastly, you may just have **too much information!**
- You may be describing something in too much detail, may be mentioning too many projects/experiences, etc.
- Don’t overwhelm the reader!
- Remember, **quality > quantity!**
### Sections to Include
You should include the following sections in the following order
1. **Name and Contact Information**

28
content/resources/internships/resume/appearance.mdx
View File

@ -1,28 +0,0 @@
- There’s no one template to follow or one template you should use
- There are countless templates you can find online, such as some on Overleaf, on Microsoft Word, etc.
- Some people might want to try to “game the system” by optimising for ATS (Applicant Tracking Systems), but there’s no correct answer for this
- There’s no one text editing software to use
- There’s a debate between using LaTeX as opposed to a WYSIWYG (What you see is what you get) word editor like Microsoft Word
- Using one or the other may have slight advantages, but overall, they make no difference
- The only answer is to use one that you’re comfortable using, as it’s just best to create something that someone can read
- You should use a **single** A4 or Letter page, and be able to fit everything on this one page
- Most people prefer to use narrow margins (1.27cm/0.5”) to fit everything in; however, it is safe to use normal margins (2.54cm/1”)
- Font selection is not much of a concern; however, keep it readable and professional
- This means avoiding fonts such as Comic Sans
- The argument between Sans Serif and Serif fonts doesn’t matter too much, readability matters the most
- Fill your page as much as you can!
- Leaving empty space may leave a bad impression, as it may look like you may not be interested and it doesn’t give an employer enough information to base a decision off of
- Look at the **Sections to Include** section for information to include that you may be missing
- If you’re running out of space on your page…
- Decrease your font size (while maintaining readability)
- So long as your page is readable, it’s perfectly fine to decrease your font size
- Make sure it’s not **cramped** as it can be extremely difficult to distinguish multiple lines of text if the font is too small
- There’s no definitive answer for the minimum size of font you can set, as fonts vary in size, but somewhere between 8pt and 10pt would be considered the bare minimum to be readable
- Decrease spacing between text
- Look out for lines that may only contain a few words
- Some lines may break into multiple lines, with the last line that consist of only a few words
- Try to rephrase that whole point such that it takes up less space, through the removal of some filler words, unnecessary adjectives/adverbs, etc.
- Lastly, you may just have **too much information!**
- You may be describing something in too much detail, may be mentioning too many projects/experiences, etc.
- Don’t overwhelm the reader!
- Remember, **quality > quantity!**

9
content/resources/internships/resume/general.mdx
View File

@ -1,9 +0,0 @@
- Follow the KISS principle
- KISS - Keep it simple, stupid!
- Often times, people try to cram in as much information, but being direct and straight to the point makes it easier to read
- The employer, more often than not, has hundreds of resume to go through and may only have a few seconds to read through an entire resume, so simplicity is often preferred as extra details may be overlooked
- All the description you include on your resume should be short, simple, concise, and to the point
- Make sure they’re relevant to the job posting
- It’s common for descriptions to start with a verb
- Highlight any metrics as it’s easy for people to understand
- Bold these in your resume so they catch the attention of the employer

3
content/resources/internships/resume/preface.mdx
View File

@ -1,3 +0,0 @@
Your resume is the first thing an employer sees and the main thing that the employer will use to base their decision to interview you off of. You will need to make a good first impression to show that you’re the ideal candidate and that you have all the skills and qualifications necessary for the jobs you’re applying for.
Although anyone can state that they have the necessary qualifications and skills for a given job, you must demonstrate your ability through past experiences and/or projects, and describe them in detail to cement your skills.

25
pages/resources/internships/index.module.css
View File

@ -40,7 +40,7 @@
justify-content: space-between;
align-items: center;
border-bottom: 1px solid var(--light--author-text);
width: calc(61.52vw + 124.3px);
width: calc(50.52vw + 124.3px);
margin: calc(20rem / 16) auto;
}
@ -50,13 +50,14 @@
justify-content: center;
align-items: center;
margin: 0;
margin-bottom: calc(10rem / 16);
padding: calc(10rem / 16);
border-top-left-radius: calc(10rem / 16);
border-top-right-radius: calc(10rem / 16);
background-color: transparent;
color: var(--primary-accent);
font-size: calc(1.716vw + 7.566px);
font-weight: 700;
color: var(--text);
font-size: calc(0.7vw + 7.566px);
font-weight: 400;
cursor: pointer;
width: calc(100% / 3);
border: none;
@ -64,42 +65,42 @@
transition: background-color 0.2s ease-out;
}
.selector:hover {
background-color: var(--dark--primary-accent-lightest);
color: var(--link-hover);
}
.selected {
background-color: var(--light--author-text);
color: var(--primary-accent);
}
.selected:hover {
background-color: var(--light--author-text);
color: var(--primary-accent);
}
.subpagesWrapper {
overflow-x: hidden;
margin: calc(20rem / 14) calc(0.1924 * 100vw - 62.15px);
margin: 0 calc(0.1924 * 100vw);
}
.subpagesContainer {
display: grid;
grid-template-columns: repeat(3, minmax(0, 1fr));
grid-template-rows: repeat(1, minmax(0, 1fr));
width: calc(3 * (61.52vw + 124.3px));
width: calc(3 * (50.52vw + 124.3px));
transition: transform 0.6s cubic-bezier(0.88, 0.1, 0.64, 0.95);
}
.subpage0 {
transform: translateX(0);
}
.subpage1 {
transform: translateX(calc(-1 * (61.52vw + 124.3px)));
transform: translateX(calc(-1 * (50.52vw + 124.3px)));
}
.subpage2 {
transform: translateX(calc(-2 * (61.52vw + 124.3px)));
transform: translateX(calc(-2 * (50.52vw + 124.3px)));
}
.subpageContainer {
padding: 10px;
margin: 0 10px;
overflow-y: hidden;
transition: all 2.5s cubic-bezier(0.95, 0.34, 0, 1);
transition: all 6s cubic-bezier(0.95, 0.34, 0, 1);
}
.subpage {

172
pages/resources/internships/index.tsx
View File

@ -11,23 +11,15 @@ import {
import { Title } from "@/components/Title";
import Header from "../../../content/resources/internships/index.mdx";
import ResumePreface from "../../../content/resources/internships/resume/preface.mdx";
import ResumeGeneral from "../../../content/resources/internships/resume/general.mdx";
import ResumeAppearance from "../../../content/resources/internships/resume/appearance.mdx";
import ResumeContent from "../../../content/resources/internships/resume/content.mdx";
import InterviewPreface from "../../../content/resources/internships/interview/preface.mdx";
import InterviewGeneral from "../../../content/resources/internships/interview/general.mdx";
import InterviewBehavioural from "../../../content/resources/internships/interview/behavioural.mdx";
import InterviewTechnical from "../../../content/resources/internships/interview/technical.mdx";
import Resources from "../../../content/resources/internships/resources/index.mdx";
import Resume from "../../../content/resources/internships/resume.mdx";
import Interview from "../../../content/resources/internships/interview.mdx";
import Resources from "../../../content/resources/internships/resources.mdx";
import styles from "./index.module.css";
export default function Internships() {
const [currentSubpage, setCurrentSubpage] = React.useState(1);
const [currentResumePage, setCurrentResumePage] = React.useState(0);
const [currentInterviewPage, setCurrentInterviewPage] = React.useState(0);
return (
<>
<Title>Internships</Title>
@ -67,166 +59,24 @@ export default function Internships() {
: styles.subpage2)
}
>
<div className={styles.subpageContainer}
<div
className={styles.subpageContainer}
style={{
maxHeight: currentSubpage === 0 ? "100%" : "0",
}}
>
<div className={styles.subpage}>
<ResumePreface />
</div>
<div
className={styles.selectorContainer}
style={{
width: "100%",
}}
>
{["General", "Appearance", "Content"].map((name, i) => (
<button
className={
styles.selector +
" " +
(currentResumePage === i ? styles.selected : "")
}
key={name}
onClick={() => {
setCurrentResumePage(i);
}}
>
{name}
</button>
))}
</div>
<div
className={styles.subpagesWrapper}
style={{
width: "100%",
margin: "0 auto",
}}
>
<div
className={
styles.subpagesContainer +
" " +
(currentResumePage === 0
? styles.subpage0
: currentResumePage === 1
? styles.subpage1
: styles.subpage2)
}
>
<div
className={styles.subpageContainer}
style={{
maxHeight: currentResumePage === 0 ? "100%" : "0",
}}
>
<div className={styles.subpage}>
<ResumeGeneral />
</div>
</div>
<div
className={styles.subpageContainer}
style={{
maxHeight: currentResumePage === 1 ? "100%" : "0",
}}
>
<div className={styles.subpage}>
<ResumeAppearance />
</div>
</div>
<div
className={styles.subpageContainer}
style={{
maxHeight: currentResumePage === 2 ? "100%" : "0",
}}
>
<div className={styles.subpage}>
<ResumeContent />
</div>
</div>
</div>
<Resume />
</div>
</div>
<div className={styles.subpageContainer}
<div
className={styles.subpageContainer}
style={{
maxHeight: currentSubpage === 1 ? "100%" : "0",
}}
>
<div className={styles.subpage}>
<InterviewPreface />
</div>
<div
className={styles.selectorContainer}
style={{
width: "100%",
}}
>
{["General", "Behavioural", "Technical"].map((name, i) => (
<button
className={
styles.selector +
" " +
(currentInterviewPage === i ? styles.selected : "")
}
key={name}
onClick={() => {
setCurrentInterviewPage(i);
}}
>
{name}
</button>
))}
</div>
<div
className={styles.subpagesWrapper}
style={{
width: "100%",
margin: "0 auto",
}}
>
<div
className={
styles.subpagesContainer +
" " +
(currentInterviewPage === 0
? styles.subpage0
: currentInterviewPage === 1
? styles.subpage1
: styles.subpage2)
}
>
<div
className={styles.subpageContainer}
style={{
maxHeight: currentInterviewPage === 0 ? "100%" : "0",
}}
>
<div className={styles.subpage}>
<InterviewGeneral />
</div>
</div>
<div
className={styles.subpageContainer}
style={{
maxHeight: currentInterviewPage === 1 ? "100%" : "0",
}}
>
<div className={styles.subpage}>
<InterviewBehavioural />
</div>
</div>
<div
className={styles.subpageContainer}
style={{
maxHeight: currentInterviewPage === 2 ? "100%" : "0",
}}
>
<div className={styles.subpage}>
<InterviewTechnical />
</div>
</div>
</div>
<Interview />
</div>
</div>
<div
@ -241,10 +91,6 @@ export default function Internships() {
</div>
</div>
</div>
<DefaultLayout>
<ConnectWithUs />
<EmailSignup />
</DefaultLayout>
</>
);
}