Fullstack Web Development Peer Tutor

Reports To: TTPR Program Manager Weeks (12) Week 1: Warp, Cursor, Claude Code + HTML/CSS/JS/Git (Solo Git) Week 2: Codex, Claude Cowork + HTML/CSS/JS/Git (Collaborative Git) Week 3: ReactJS + APIsWeek 4: ServerWeek 5: Database Week 6: Client-Side Routing + ReviewWeek 7: CRUD (Solo) + Deployment + Security Week 8: Capstone I (Groups of 4) Week 9: Capstone II (Groups of 4) Week 10: Capstone III (Groups of 4) Week 11: Capstone III (Groups of 4) Week 12: Capstone III (Groups of 4) + Demo DayInstructional Staff Standard Duties

• Review the material to prepare for help tickets
• Provide resources to students for technical knowledge and technical skillset support
• Complete help tickets for troubleshooting: tool installation, tool configuration, problem-solving related to in-class assignments, homework assignments, or capstone projects
• Identify blockers for a student's project
• Guide students to verbalize their thought process
• Unblock students through advisement, technical project management techniques, or by escalating to another instructional staff member
• Function as a scrum master for capstone projects and also contribute to brainstorming about frontend design, file structure, and project scope (you might be asked to diagram on a whiteboard when in-person or a digital whiteboard when remote)
• Participate in 1 weekly sync up meeting with the instructional staff by default, and with the program manager if available
• Review if a classwork or homework submission was submitted with: a link, an accessible link, a link to the proper project, time of last commit, sum of commits, and amount of commits per group member (use Trello?)
• Hold a mandatory office hour M-Th (no office hour on Friday) (two thirty-minute segments)
• Track individual aggregate contributions at the end of each capstone project by commit history, by copying and pasting it into an internal document
• Flag areas of improvement in student progress within an internal document
• Proctor monthly quiz with assigned students
• Conduct exit interview with assigned students

REQUIRED SKILLS: Applicants must have completed (or are approaching completion of) the most recent TTP Residency Program at BMCC, including a minimum of two capstone projects with active contribution during the Summer 2025 occupational training period Associate degree or associate degree-seeking in computer science or related fields Proficient in fullstack web development (HTML, CSS, JavaScript, Node, Express, React, Redux, Relational DBMS, ORMs) Proficient in developer tools such as CLI/Terminal, Postman, VS Code, Postico, pgAdminProficient in a project management tool(s) such as Jira, ClickUp, Monday, Asana, Notion, or Trello Proficient in industry-standard Git workflows and GitHub (GitHub Projects, GitHub Pages) Proficient in developer operations as it pertains to CI/CD and/or deployment/hosting using Netlify and/or Vercel Familiarity with: implementation details of Open Authorization protocolPREFERRED SKILLSPrior experience working at a Software Engineering/Cybersecurity/Data Science Bootcamp, an instructional (technical) role in a CUNY or CUNY-related program, or as a collegiate adjunct for a computer science course Familiarity with: Figma, Lucidchart, Tailwind, Bulma, Rate Limiting, Hashing/Salting, CORSFamiliarity of: AWS/GCP/Azure, Firebase, UI/UX principles, React Native, TypeScriptDESIRED SKILLSPrior experience as an apprentice, intern, freelance, associate, junior, or senior software engineer Prior experience as a or in: solutions engineer, sales engineer, quality assurance, quality engineer, software development engineer in test (SDET), scrum master, or UI/UX and Graphic Design & Digital DesignPrior experience in other fields such as but not limited to: Data Engineering, Data Science, Cybersecurity, Artificial Intelligence Prior experience with: hackathons, open-source contribution, bug bounties, published scholarly works and research, computer science degree, TA/SI equivalent during undergraduate or graduate studies Examples of bugs you should be able to troubleshoot:1: A student says: "node -v isn't working" and you inform them that nodeJS is not yet installed.2: A student is running their client code on one local server (Port 3000) and their backend code on another local server (Port 1234). With respect to Port 3000, they make an AJAX request through their browser to the local server on Port 1234. The student receives a CORS error. They send the same request through Postman. The student does not receive a CORS error. They put in a help ticket to have a thorough understanding of why this is happening, as well as some possible solutions (forward proxy or whitelisting).3: A student puts in a help ticket to install postgres on a device running Mac OS. Another student puts in a help ticket to install postgres on a device running Windows OS.4: A student wants to practice responsive web design, so they take ownership of some open issues on their GitHub project management board for it. They accidentally use a media feature incorrectly such as using min-width versus max-width. You must be able to help them identify this mix up, and provide a solution as to why the style never applied to the intended screen, in a constructive and effective way.5: A student sets up Okta's Auth0, however the first login fails despite it working upon refresh. It is up to you to discuss with the student, articulate the solution, and if necessary, share the working code.6: A student puts in a help ticket that just reads as "getting error: detached HEAD state, please help in breakout room 8". You should be able to explain to them git's