School Policies


Welcome! This bootcamp prepares students with no programming experience to start careers as data engineers. We start with learning the Python programming language, then progress to more advanced tools. 

The program is thirty hours a week for twenty-five weeks, and consists of live instruction, solving exercises with classmates, and individual projects. It’s entirely online, and instructors are available throughout the day to offer guidance and resources. After nineteen weeks of coursework, students participate in a six-week internship.


The instructors for this course are Parham Parvizi and Alma Frankenstein.

Parham Parvizi


Discord: Par#2420

LinkedIn: parvister

Alma Frankenstein


Discord: alma_frankenstein

LinkedIn: alma-franken

Mission and Culture

Data Stack Academy aims to benefit our students, the companies that employ our graduates, our employees, and the culture of tech. We do this by:

Training Top Quality Graduates – Our curriculum, admissions process, rigorous expectations, daily timed challenges, and mentorship ensure that anyone with a certificate from Data Stack Academy is a skilled programmer.

Affirmative Action – We aim to be an incubator for highly-qualified programmers from demographics that are commonly marginalized in tech. We do this by providing scholarships to people from those demographics.

Diversity, Equity, and Inclusion – Part of Data Stack Academy’s mission is to make careers in tech accessible to people who often face barriers to entering that field. We strive to foster a culture where diversity is respected, and everyone, regardless of their social identity or background, can thrive.

Enrollment Process

The general process for enrollment is:

    1. Ensure access to a reliable internet connection, and a computer with at least 16GB of memory and working mic and camera.
    2. Secure financing.
    3. Sign the registration form.

    These are covered in detail on the ‘Admissions‘ page.



    The tuition includes admission to our 19 week long course, 6 weeks internship program, and one year of post-graduation career services.

    Our payment options are:

        • Standard tuition: $14,750
          This is the standard tuition if you choose to pay using financing options (loans or ISA) or a payment plan (installments).

        • Up-front Discount: $12,550
          Discounted tuition if you choose to pay in full before the start of the class.

      Other Fees

          • Registration Fee: $50
            Non-refundable registration fee to cover enrollment and admin costs.

        Refunds and Cancellation Policy

        If a student chooses to leave the program permanently, they will be refunded according to the following schedule:

            • The $50 registration fee will not be refunded unless they cancel enrollment, in writing, within five days of signing the enrollment agreement.

            • If they attended classes, tuition will be prorated for the amount of coursework they attended, excluding the internship.

            • In the case of a student attending multiple cohorts before withdrawing permanently, tuition will be prorated based on the cohort that was attended the longest.

          Students must state their intent to withdraw from the program in writing, via email, to Students are considered enrolled in the program until the timestamp on their intent to withdraw email. Refunds will be paid within 30 days of receiving notice to withdraw.

          Prorating is based only on the coursework part of the program, excluding the internship. If a student cancels before the start of class, the full tuition will be refunded. Students who used a financing option may have to work with the financing company for a refund.

          If a student chooses to leave the program permanently and later wants to re-enroll, they will have to pay full tuition, as well as the registration fee. 

          Pausing Enrollment 

          A student can pause enrollment at any time, for any reason. They can choose to pick up where they left off with the next cohort, or they may start from the beginning.  If more than six months elapse between the student pause enrollment and re-enrolling, they are required to backtrack three units (three weeks) prior to the point where they left off. Students who backtrack are expected to participate, attend class, and turn in code reviews like any other student. When re-enrolling, the student has a clean slate of absences, tardies, and academic warning passes.

          Students are allowed to pause enrollment three times before they must begin the enrollment process, pay full tuition, and start at the beginning of the program as a new student.

          If a student would like to pause enrollment, they must email their instructors clearly stating their intent. Students who financed tuition through Mia Share or Meritize should arrange a repayment plan with their financing company; this is outside of Data Stack Academy’s purview.


          We provide limited scholarships to those who can not afford the full tuition. Scholarships are based on:

            • The strength of the scholarship application

            • Stated membership in an identity group that has historically been marginalized in tech

            Please see the ‘Scholarships‘ page for details.

            Student Expectations and Code of Conduct

            Code of Conduct

            Data Stack is committed to providing a vibrant, productive, safe, and supportive environment for learning. Students spend most of their time working with other students and supporting each other with the material and exercises. It is crucial that we treat each other with respect, care, compassion, and patience.

            In attending Data Stack, everyone must agree to follow the code of conduct:

                • Be respectful: treat people how you would like to be treated.

                • Show compassion: be aware that students take different routes to learning, and accommodate your classmates.

                • Help others in helping you: tell other students about harmful behavior or your special needs.

                • Be professional: treat this as your profession. Show up on time, show up ready, and dress appropriately.

                • Challenge yourself and others: be curious, explore, and support others in exploring.

                • Strive to be exceptional: pay attention to detail, understand every topic, and ask questions.

                • Educate yourself about other cultures and norms: ignorance is not an excuse for any harmful behavior.

              Data Stack Academy has a zero-tolerance policy on sexual harassment, discriminatory behaviors, or derogatory language.

              Student Expectations

              In addition to contributing to a safe, supportive learning environment, we expect students to present themselves at school like they would at a job. This includes being:

              Professional – Professionalism includes punctuality, politeness, being prepared for class, participating, turning in work on time, and responding to emails.

              Mutually Supportive – Working with others can be challenging. Students are expected to be patient and helpful with their classmates, knowing that they’ll need to ask for patience and help at times, too. We approach success as a collaboration, and not a competition.

              Self-directed – Programmers need to be good at research. Teachers are here for guidance, but students are generally expected to research answers on their own.

              Humble – We want students to take pride in their achievements! At the same time, students will be more successful in learning and collaboration if they ask for help when they truly need it, and when they acknowledge that there’s always more to learn.

              Respectful, compassionate, and open-minded: As colleagues and classmates we commit to always treat everyone with the utmost respect. We listen to our colleagues’ questions and are patient, as we all have different pace and methods in learning. Programming is full of wonders, and sometimes even what appears to be the “wrong” paths at first will lead us to great discoveries. 

              Code of Conduct Violations Reporting, Grievances, and Mediation Process

              If for any reason you feel a student or staff member has violated the Code of Conduct, or if Data Stack is not meeting your needs in any way, please talk with a staff member. We encourage students to speak up whenever they feel uncomfortable.

              In order to resolve issues we recommend following the steps:

                  1. We encourage students, whenever possible, to resolve conflicts directly.
                  2. Speak with a Data Stack instructor, administrator, advisor, or staff. 
                  3. Use the online Code of Conduct Complaint Form. You can fill this form anonymously if you prefer.
                  4. If you aren’t able to resolve your grievance via the methods above, email with the subject “Student Grievance” and list your specific grievances. Include supporting documentation, if there is any.

                Administrators will talk to both parties and gather as much information as possible, and then decide how to proceed. Students may request that an instructor, administrator, or someone from outside the organization be brought in to mediate. Because the entire complaint and mediation process must be thoroughly documented, meetings may be recorded with the participants’ consent, or communication may have to be over email. 

                Persistent Code of Conduct violations may result in expulsion. Data Stack staff may decide to expel the offending party upon their first offense depending on the severity of the issue.

                Data Stack will do its best to address and resolve any complaints within 15 days.

                Class Structure

                Course Syllabus Overview

                The program is 25 weeks long, 30 hours/week. It’s broken down into 17 weeks of core curriculum, 2 weeks of career training, and a required 6-week internship. 

                Each chapter is a week of class. Monday-Thursday is live instruction and pair programming, and Friday is an independent code review.

                Core Curriculum

                Each week of the core curriculum is a different unit, composed of four lessons (“episodes”). Instructors may modify the curriculum to accommodate the needs of the class.

                Section 1: Foundations
                1. Intro
                2. Python pt. 1
                3. Python pt. 2
                4. Pandas
                5. Team Week

                  Section 2: Data Modeling, SQL, and the Cloud
                  6. SQL
                  7. Cloud, BigQuery, Looker Studio
                  8. Data Modeling
                  9. Data Build Tool (dbt)
                  10. Team Week

                  Section 3: Airflow and Spark
                  11. Airflow pt.1
                  12. Airflow pt.2
                  13. Spark pt.1
                  14. Spark pt.2
                  15. Team Week

                    Section 4: Capstones
                    16. Visualization
                    17. Capstones

                      The curriculum (including code examples, written lessons, setup instructions, and exercises) is stored in a GitHub repository:


                      This repository is private. Access will be granted after enrollment.

                      Daily Cadence

                      Classes meet live (online) Monday through Thursday, with the following schedule. All times are in PST.


                      • 9:00-9:45  –  Team meeting and lesson
                      • 9:45-12:00 –  Pair programming
                      • 12:00-12:45 –  Lunch break


                      • 12:45-1:30 –  Timed coding challenge
                      • 1:30-3:15 –  Pair programming
                      • 3:15-3:45 –  Team retro

                      Students pair over Discord. All other meeting are on Google Meet, at this link:


                      Data Stack Academy observes the following holidays:

                          • New Year’s Day

                          • Martin Luther King Jr Day

                          • Nowruz (Spring Equinox)

                          • Memorial Day

                          • Juneteenth

                          • Independence Day

                          • Labor Day

                          • Yom Kippur

                          • Veterans Day

                          • The week of Thanksgiving

                          • The last week of December

                        Student Assessment

                        Performance Monitoring

                        Instructors monitor performance using:

                            • Daily timed challenges

                            • Code review assessment projects

                            • Attendance and participation

                          Daily Timed Challenges

                          Every day, our students are challenged to solve small programming questions. These questions are timed, and we review other students’ answers as a team. The point of these challenges is to practice basic concepts, and to practice for technical interviews. 

                          Although these challenges are not graded, instructors use them to gauge student understanding. If a student is struggling with a topic, the instructor will schedule a one-on-one time to mentor them.

                          These exercises are one of the main difference makers in the quality of our graduates, and students are expected to participate. Failing to participate will result in losing one academic warning pass. 

                          Code Review Assessment Projects

                          Code review (CR) projects are the school’s main method for measuring student progress. Each Friday, the students are presented with a coding project that uses the material covered by that week’s lessons. Students upload their code reviews to their online GitHub repository, and submit a link to the repository.

                          Code reviews are emailed at 8am PST Friday morning, and are due at 5pm PST the following Saturday.  

                          To submit a code review, students should email a link to the GitHub repository containing the CR, as well as any comments, to 

                          The purposes of the code reviews are to formally evaluate that the student has understood that week’s materials, and to build the student’s GitHub portfolio.


                          Students can expect grades and feedback by the end of the following Tuesday. If a code review doesn’t pass the first time, students are allowed until 8am on the Monday nine days from the initial due date to resubmit, and can expect feedback on the resubmission by end of day the following Wednesday. 

                          If they need to resubmit a third time, the final due date is 8am Monday, a week from the first resubmission date (16 days from the initial deadline). 

                          If a project doesn’t pass by the final deadline, the student will likely be asked to start from the beginning with a later cohort. 

                          Students are entitled to one resubmission and one twenty-minute meeting with a teacher to discuss their code review. If a student turns in a resubmission before the deadline, they can request grading and feedback early, and/or request multiple meetings or resubmissions. The instructor can choose to honor these requests if their schedule allows. 

                          Each code review lists the acceptance criteria needed to pass the project objectives. The acceptance criteria are graded as pass/fail. In order to pass the code review, students must pass all of its acceptance criteria. 

                          Students must pass all code review projects in order to pass the course.

                          Academic Policies



                          A student is considered absent if they miss an hour or more of class. Students are allowed 7 absences during the 19 weeks of in-person instruction. If a student misses more than that, they will likely be asked to rejoin from the beginning when the next cohort starts. Instructors may make exceptions based on the student’s circumstances and ability to keep up with the coursework.


                          In addition to the 7 allowed absences, students may arrive up to 5 minutes late, or leave more than 5 minutes early, up to 10 times total. More than that, and they will likely be asked to rejoin when the next cohort starts.

                          Instructors will take attendance during morning meetings, afternoon meetings, and retrospective. They may also check in on programming pairs at any point in the day to confirm attendance.


                          Students are expected to be present and attentive during lessons and pairing, to participate in daily timed challenges, and to present group projects and capstones. If a student needs exceptions or accommodations for this policy, they need to have it approved in writing in advance. If an instructor notices a pattern of non-participation from a student, they will address it both in a meeting and in writing. If the pattern continues, the student may be asked to start from the beginning with a later cohort.

                          Academic Warning Policy

                          Each student starts the course with 15 academic warning passes. A pass is used when:

                              • They were present but didn’t participate in a time challenge

                              • They turn in a code review up to an hour late

                              • The student can’t explain part of the code in their code review when asked

                              • The first submission of a code review they turn in is “empty”, meaning that only the boilerplate parts of the repo exist, without any original code

                              • The second submission of a code review also fails

                            After a student uses 5 passes, they will receive an emailed warning. When they use 10, they will receive an emailed warning and a meeting to discuss the pattern. If they use all 15 passes, they will likely be asked to join the next cohort.

                            Similarly, students will receive an emailed warning after 4 tardies or 3 absences, and an emailed warning and a meeting after 7 tardies or 5 absences.

                            Academic Honesty

                            We take academic honesty very seriously. We understand that code often converges on the same solution, and that much of programming is looking up solutions. However, if a student finds a coding solution online, they are expected to be able to explain how it works. They are not allowed to copy and paste other people’s code directly.

                            Instructors may ask students to meet to talk about their code reviews. At these meetings, the instructor may ask the student to explain a section of their code. If they can’t, they lose one of their passes as outlined in the Academic Warning Policy. This is limited to one lost pass per code review.

                            If it’s apparent that a student has plagiarized code for their code review (for instance, if there are anomalies in the code like comments, variable names, or errors that match other code published online), they may be expelled.

                            Progress Reporting

                            Students are expected to track their own deadlines, academic warning passes, and attendance. However, they are welcome to ask their instructors if they have questions.

                            Several times throughout the course all students will be issued a progress report form, with a record of their passed/failed code reviews, absences, tardies, and academic warning passes. They will be asked to sign their acknowledgment that received and understood it.

                            Asking for Help

                            Asking for Help on Classwork

                            One of the core abilities Data Stack Academy aims to teach students self-direction, and students are expected to first research solutions to programming questions on their own. If they can’t find the answer they should talk to their pair, and then to other pairs in the class. If they’re still stuck after that, instructors are available to help.

                            Students can ask for help from instructors by:

                                • Bringing up questions during the morning meeting, the afternoon meeting, or retro.

                                • Asking a teacher for a one-on-one meeting.

                                • Sending an email.

                                • Posting questions on Discord, our team messaging app. 


                              Parham Parvizi


                              Alma Frankenstein


                              Instructors are not available to help outside of live class hours, including during code review days. 

                              Asking for Help on Code Reviews

                              If a student needs help with a code review, they may request a meeting with a teacher, limited to one meeting per week. Instructors can offer direction, but not directly give answers. Students are not allowed to ask other students for help on the code reviews.

                              Group Projects

                              This course includes group projects. These projects are intended as portfolio pieces, and as a way for students to practice collaboration in planning and on GitHub.

                                  • Format:
                                        • Mon-Thurs working as a group on a single GitHub repository

                                        • Friday each student (except the one already hosting the shared repository) forks the shared repository, and works on the project independently. This is the code review for that week. Students submit a link to their GitHub repo and follow the same deadline schedule as any other code review.

                                    • Group presentation is on Thursday afternoon. Students should spend some time on Thursday morning getting ready to present.

                                    • Every student is expected to present their work. Presentations should be 5-10 minutes per person, and can be about the overview of the project, a part they worked on, challenges they encountered, and/or future improvements.

                                  Each student is graded on:

                                      • Participating in the presentation

                                      • At least 20 commits on the shared repository

                                      • At least 8 commits on their forked project on Friday

                                    Capstone Project

                                    The capstone is intended as a portfolio centerpiece. It should showcase the student’s skills. Students may do any project they like for the capstone, but it should include tools covered by the Data Stack curriculum.

                                    Each student will have 10 minutes on the Thursday of capstone week to present to the class. They are expected to continue to work on their project on Friday, like a regular code review, and submit a GitHub link for grading. The grading criteria are:

                                        • The project includes an informative README, a .gitignore file, and a requirements.txt file

                                        • The README includes an informative illustration, like a chart, DAG, or pipeline

                                        • The repository has at least 20 commits

                                        • The student presented their project to the class

                                      Merit Badges

                                      Badges encourage students to help classmates and put in extra effort. They’re based on earning points.

                                      Examples of ways to earn badges are:

                                          • Using the fewest academic warning passes at the end of the course
                                                • Earn Badge: Top student

                                            • Answering bonus questions on code reviews
                                                  • Earn Points: labeled in CR

                                                  • Earn Badge: 5pts

                                              • Above and beyond on Code Reviews
                                                    • Earn Points: teacher discretion

                                                    • Earn Badge: 10pts

                                                • Helping classmates
                                                      • Earn Points: nominated at retro, 1pt

                                                      • Earn Badge: 3pts

                                                  • Doing research and sharing it with the team
                                                        • Earn Points: 1-3pts, teacher discretion

                                                        • Earn Badge: 5pts

                                                    • Finding errors in the curriculum
                                                        • Earn Points: 1pt per correction
                                                        • Earn Badge: 3pts

                                                  Students are encouraged to show off their badges on LinkedIn profiles and resumes. In addition to Data Stack Academy’s badges, students are encouraged to try for badges earned through GitHub Achievements. Earning the ‘dbt Fundamentals’ badge created by Fishtown Analytics is part of this course.

                                                  Role of Instructors

                                                  The role of instructors is to guide, support, and evaluate students. They are available for help in the ways outlined in the ‘Asking for Help’ section. Students are expected to be independent, self-directed, and responsible for tracking deadlines and meetings.

                                                  Role of Mentors

                                                  Students may request to meet for office hours with mentors to talk about career or class concerns not directly related to the class curriculum, such as outside coding projects, dealing with impostor syndrome, or career development.


                                                  For each cohort, Data Stack will assemble a set of host internship companies. Students interview with several companies. Students and companies rank their match preferences, and students are matched with a host company based on a match-making system. 

                                                  The internship is thirty hours a week for 6 weeks, and it is unpaid. Students must complete their internship in order to graduate from the program. Data Stack Academy advisors prepare students for internship interviews and support them during their internship.

                                                  Internship Eligibility Requirements

                                                  In order to participate in the internship program, students must:

                                                      1. Complete all coursework
                                                      2. Pass all code review projects
                                                      3. Complete a Capstone Project

                                                    Internship Agreements

                                                    Internships are intended to benefit both the student and the host company. 

                                                    The contacts for the host companies agree to:

                                                        • Act as mentors for the interns.

                                                        • Be responsive to questions or concerns.

                                                        • Communicate with students and Data Stack Academy.

                                                        • Schedule regular meetings with the interns.

                                                        • Provide thirty hours worth of relevant work a week.

                                                        • Have clearly-outlined projects for the interns to work on. The projects should be related to what the interns studied and/or are interested in, and should help build the interns knowledge and portfolios.

                                                        • Give the interns the access, direction, and resources they need.

                                                      In return, the interns agree to:

                                                          • Honor Data Stack Academy’s code of conduct at their internship.

                                                          • Be a public representative of our school, knowing that giving our graduates a bad reputation harms their classmates and future graduates.

                                                          • Be punctual, participate in meetings, ask questions, and do their best.

                                                          • Do at least 30 hours of work per week.

                                                          • Let Data Stack Academy know if there are any issues with the internship.

                                                          • Advocate for themselves in getting useful experience from the internship, and/or let us know if they need an advocate.

                                                        Paid Internships

                                                        Companies often elect to continue to work with our graduates after the unpaid internship portion. These internships give the host companies an opportunity to further evaluate interns before offering them a position, and they provide our graduates with additional experience and a chance for employment.

                                                        Students can, of course, independently agree to any arrangement they choose with the host company. Alternatively, they may be elected to participate in the paid internship program facilitated by Data Stack Academy.

                                                        These internships are set as short-term contracts. The budget and availability is completely based on the host company. Data Stack Academy offers mentorship, and facilitates the paperwork between our graduates and the host company. We help negotiate a pay rate that suits the needs of both the graduate and the company. 

                                                        Career Services

                                                        The main objective of Data Stack Academy is to get our graduates employed in the field. We measure the success of the school by graduate employment rates, and are highly motivated to see our students succeed.

                                                        While our students are the primary contributor to their own success, the instructors for this course will support them with career services. During the course, students will be working with their instructors to prepare for internship and job interviews. After graduation, the instructors will continue to act as an advisor for a year, or until the graduate finds a job, whichever comes first. Post-graduation support includes guiding graduates through job listings, interviews, and salary negotiations. Career services are available for a year after graduation.

                                                        The last two weeks of the program are devoted to career preparation. Activities include:

                                                            1. Making a LinkedIn profile:
                                                              LinkedIn is a common way for people in the tech field to network and search for jobs.
                                                            2. Crafting a resume:
                                                              Students collaborate with their advisor to create their professional resume. This resume highlights their technical skills, school projects, and previous working experience. 
                                                            3. Polishing a GitHub portfolio:
                                                              GitHub is the number one tool used by programmers to showcase their technical abilities. During the course, the students will create a number of projects to add to their GitHub portfolio. Students will work with their advisor to learn how to best showcase these projects to potential employers. 
                                                            4. Job Searching Skills:
                                                              Navigating job listings can be a challenging task in tech. We’re here to help.
                                                            5. Technical Interview Preparation:
                                                              Employers often use technical coding challenges during their interview process to assess the skills of junior developers. The main way we prepare students for technical interviews is with the daily timed coding challenges. 
                                                            6. Mock Interviews:
                                                              During these practice interviews, advisors help students work on their soft skills, such as talking about qualifications and answering interview questions.

                                                          Applying for Jobs

                                                          After graduation, students are encouraged to apply for at least ten jobs per week. Advisors will guide students and help them navigate job listings and interviews, and conduct mock interviews to help prepare students and train them on how to highlight their valuable skills and personalities.

                                                          In addition, advisors will discuss jobs hacks with students in order to land their first jobs. These hacks include seeking positions at data consulting companies, searching for freelancing jobs, or talking with recruiters. 

                                                          Other Policies

                                                          Recording Policy

                                                          Data Stack Academy sometimes records daily lessons and makes these available to the public. By attending class, students consent to be recorded and have their image shared. If a student needs an exemption from this policy beyond turning off their camera, they must request it in writing. 

                                                          Pairs are not allowed to record one another without explicit, documented permission.

                                                          Intellectual Property

                                                          The GitHub repository containing Data Stack Academy’s curriculum is private, and cannot be shared.

                                                          Failure to Address Issues

                                                          If a student has reported a grievance in writing and it hasn’t been addressed within 15 days, they can contact the Oregon Higher Education Coordinating Commission, as outlined below:

                                                          Students aggrieved by action of the school should attempt to resolve these problems with the appropriate school officials. Should this procedure fail students may contact:

                                                          Oregon Higher Education Coordinating Commission

                                                          Office of Post-Secondary Education

                                                          3225 25th Street SE

                                                          Salem, OR 97302

                                                          After consultation with appropriate Commission staff and if the complaint alleges a violation of Oregon Revised Statutes 345.010 to 345.470 or standards of the Oregon Administrative Rules 715-045-0001 through 715-045-0210, the Commission will begin the complaint investigation process as defined in OAR 715-045-0023 Appeals and Complaints.

                                                          Accommodations and Exceptions

                                                          Students may need to ask for accommodations or exceptions due to life circumstances or different learning styles, and we are happy to make reasonable accommodations. “Reasonable” might include deadline extensions, slowing the pace of a lecture, or scheduling extra mentoring sessions. Accommodations may not be made if they put undue burden on teachers, administrators, or fellow students. Regardless of accommodations, all students are expected to learn all the material and meet all the course requirements.

                                                          Requests for accommodations or exceptions must be made in writing, via email, to If a student is requesting a deadline extension, it must be approved by the instructor ahead of time. Requests for extensions on code reviews should be sent by the end of the day the Wednesday before the assignment is due.

                                                          Mental Health

                                                          Bootcamp can be overwhelming, and we highly encourage students to take care of their mental health. If a student needs academic support, outside resources, or accommodation around mental health concerns, they should reach out to a Data Stack staff member to collaborate on how we can best support them.  

                                                          Certificate Award

                                                          A certificate of completion will be awarded when the student successfully passes all coursework and completes their internship.

                                                          We also strongly encourage students to get external certifications, such as the ones provided by Google or Microsoft. We especially recommend Google Cloud’s Professional Data Engineering certification. Our curriculum has a Google Cloud emphasis, so students are already well prepared for this certification.

                                                          A student may graduate up to three weeks early (after week 16 of the coursework) and still receive a certificate if they are offered a job in the field before the end of classes. They must state their request to graduate early in writing, via email to The student will be prorated tuition according to the number of weeks they attend class.

                                                          Tools and Resources

                                                          Resources Provided by Data Stack

                                                          Our classes are conducted completely remotely. We use a number of tools to ensure our students collaborate and stay connected.

                                                              • Google Meet:
                                                                We use Google Meet for video conferencing. Our lectures, daily timed challenges, and meetings use a Google Meet conference call. Students are encouraged to turn on their camera and microphone to participate.

                                                              • Discord:
                                                                Our students use Discord to pair up for lessons and exercises. Instructors are also available via Discord during the day to answer questions or meet with students.

                                                              • Miro Boards:
                                                                Miro is an online whiteboard tool. We use miro during the creative and collaborative phases of our group projects.

                                                              • Koalendar:
                                                                Koalendar is an online scheduling tool to request meetings with our instructors and mentors.

                                                            Hardware Requirements

                                                            We require that students meet the following requirements to ensure that they have the proper hardware to excel in the program:

                                                              • Internet:
                                                                10MB/s up and down internet connection. Students pair throughout the day, and need a strong and viable internet to share their screen and image.

                                                              • CPU and Memory:
                                                                An Intel i7 or Ryzen 7 equivalent chip with 16GB of memory. Data engineering tasks are very CPU/Memory intensive, and students will be sharing their screen on top of that. Typically we do not require a very fast graphic card for data engineering (although data science workloads do).

                                                              Note: A brand new MacBook Pro or similar laptops with these specs can be very pricey. We recommend buying used hardware and installing a Linux operating system.

                                                              There is a great Portland based non-profit called Free Geek that sells pre-owned laptops with Ubuntu pre-installed for affordable prices. Their listings are online, and can be shipped. This is also a great place to donate your old hardware.

                                                                • Microphone and Camera
                                                                  Students are required to pair up and share their screen and camera. Please ensure that you have a working microphone and camera.