Merge branch 'main' into su24-updates

data/recruitment.ts

@@ -1,7 +1,7 @@
 const recruitment = {
-  acceptingApplications: false,
+  acceptingApplications: true,
   applicationUrl: "https://tritonse.github.io/TSE-Application-Form/",
-  deadline: "Sunday, October 15th at 11:59PM PDT",
+  deadline: "Sunday, October 13th at 11:59PM PDT",
 } as const;
 
 export default recruitment;

pages/students.tsx

@@ -84,34 +84,25 @@ We host both internal and public events. To find our public events, follow us on
 
 Here is the knowledge we expect for each grade level. The interview questions might not cover all of these topics, and it might be possible to pass the interviews without knowing all of these topics, but our interview questions are designed with these expectations in mind.
 
-#### Freshmen
+#### First-years
 
 Approximately CSE 8A or equivalent:
 
 - Familiarity with at least one programming language
 - Basic datatypes: booleans, integers, floating-point numbers, strings, arrays/lists
 - Control flow structures: if/else statements, for/while loops
 - Functions
-- Exceptions
 - Unit testing concepts (no specific frameworks needed) and edge cases
 
-#### Sophomores
+#### Sophomores/Juniors/Seniors/Transfers
 
 Approximately CSE 12 or equivalent:
 
-- All of the topics for freshmen, listed above
-- Pointers or references, depending on the language you use
+- All of the topics for first-years, listed above
+- Analyzing time and space complexity
 - Recursion
-- Data structures: multidimensional arrays/lists, dynamic arrays, linked lists, stacks, queues, heaps, binary search trees, hash tables (also known as hash maps, dictionaries)
+- Data structures: multidimensional arrays/lists, dynamic arrays, stacks, queues, hash tables (also known as hash maps, dictionaries)
 - Algorithms: sorting, binary search
-- Object-oriented programming concepts: classes, constructors, instance variables, methods
-
-#### Juniors/Seniors
-
-- All of the topics for freshmen and sophomores, listed above
-- Analyzing time and space complexity
-- Trees and graphs
-- More challenging applications of the previously listed algorithms and data structures
 
 ### How can I prepare for the technical components of the developer recruitment process?
 
@@ -125,7 +116,7 @@ To prep for the technical interview:
 
 - Brush up on a high-level programming language. Python, Java, or JavaScript is preferred. C or C++ might work, but due to the nature of the interview tasks, it may be more difficult to use these languages. You will not be able to compile or run your code, so exact syntax/APIs are not that important, but we expect you to demonstrate familiarity with the language you choose.
 - Expect to solve one or more programming tasks, which may have multiple parts. Be mindful of edge cases, and discuss your approach with your interviewer before you start writing code.
-- You will be evaluated on your communication and problem-solving skills, the readability, maintainability, and correctness of your code, and (for juniors/seniors) the algorithmic performance of your code.
+- You will be evaluated on your communication and problem-solving skills, the readability, maintainability, and correctness of your code, and (for sophomores/juniors/seniors) the algorithmic performance of your code.
 
 ### What does being a developer look like at TSE?
 
@@ -138,11 +129,11 @@ We emulate the Agile Workflow to give our developers some insight on industry st
 
 Be prepared to present a past project you worked on. The presentation will be a total of 25 minutes, with 15 minutes of presentation and 10 minutes of questions. It is recommended to have either slides or some sort of visual component to your presentation.
 
-Be prepared to solve a design challenge. You will be given a prompt similar to an actual TSE project and will have 30 minutes to demonstrate your ability to think through and solve this problem. You should be prepared to both talk through your thought process as well as create some very low fidelity visuals to convey your ideas. We really want to understand what you are thinking the whole time, so please think out loud! If you get stuck at any point, the interviewer(s) will be there to help guide you
+Be prepared to solve a design challenge. You will be given a prompt similar to an actual TSE project and will have 30 minutes to demonstrate your ability to think through and solve this problem. You should be prepared to both talk through your thought process as well as create some very low fidelity visuals to convey your ideas. We really want to understand what you are thinking the whole time, so please think out loud! If you get stuck at any point, the interviewer(s) will be there to help guide you.
 
 ### What does being a designer look like at TSE?
 
-Designers communicate closely with our nonprofit clients in order to craft user flows, wireframes, and prototypes that align with their needs. Designers often take on projects in pairs. They are the ones creating the detailed plan for the end solution, which is then eventually handed off to TSE developers. There’s a variety of types of projects, ranging from website rebranding to internal software tools. Typically, designers spend 5-7 hours a week on TSE activities.
+Designers collaborate closely with their non-profit client, carefully listening to the client’s needs to create tailored solutions. Using design tools like Figma, they guide projects through the entire design process, including research, ideation, wireframing, prototyping, etc. Along the way, designers hand off their designs to developers, while remaining available to address any feasibility concerns. Projects vary in scope, from website rebranding to internal software tools, providing a dynamic range of challenges. On average, designers dedicate 5-7 hours per week to TSE activities.
           `}
         </CollapsibleSection>
         <CollapsibleSection title="TEST FAQs">