Student Opportunities

We're proud of the diverse membership here at Blueprint. Join us and make an impact with our opportunities in product design, project management, or software development!

student

Our Teams

Project Teams

APPLICATION REQUIRED

Purpose: Work directly on projects with non-profit organizations (NPOs)!

Goal: Help deliver requested software solutions to NPOs and contribute to our mission of creating tech for social good!

Requirements: Project teams are year long commitments depending on the scope of the project. We are looking for technical leads, project managers, developers, and designers who can engage and collaborate within this time frame while also meeting deadlines.

Clipart of three people working on a project

Application Process

Written Application

1. Written Application

Our written application will open in a short and anonymized format where we can get a sense of what brings you to Blueprint!

Take Home Challenge

2. Take Home Challenge

Next, we will assign you a challenge that corresponds to your applied role and is to be completed on your own time (1-2 hours max).

Blueprint Games

3. Blueprint Games

After the challenge, we will invite you to an interactive and collaborative activity where you will solve a mock NPO problem.

Coffee Chat

4. Coffee Chat

Finally, we will invite you to speak with an executive board member to review each stage of the application process, ask questions, and talk!

Internal Teams

Internal Teams

NO APPLICATION

Tech Team

Purpose: Apply your coding skills and support internal development projects!

Goal: Help run Blueprint as an organization while also learning/improving programming skills!

Design Team

Purpose: Support the design process in the tech team and project teams!

Goal: Help strengthen collaboration between designers and developers while also learning/improving design skills!

Have any questions? Email us at blueprint@stevens.eduEmail

FAQs

Project Teams: The commitment is similar to taking a course at Stevens. There are typically weekly 1-hour meetings, and the rest of the work is asynchronous. Building software takes time, so you should expect to dedicate 4-10 a week to your project!

Internal Teams: Time commitments are a lot more flexible. You can choose your level of involvement. However, if you pick up a task on a specific project, you will be expected to complete it in a timely manner. Both the Tech and Design Teams have meetings (not mandatory) where members can receive tasks and ask questions.

Project teams are comprised of technical leads, project managers, developers, and designers.

  • Tech Leads – Oversee the project's technical implementation, including architecture, infrastructure, and deployment. They ensure the software is scalable, maintainable, and integrates effectively with cloud platforms.
  • Developers – Build the project by writing, reviewing, and testing code in various languages and frameworks. They work on both frontend and backend development to turn designs into functional products.
  • Designers – Conduct user research, create wireframes, and design UI/UX using tools like Figma. They ensure the final product is intuitive, accessible, and aligns with the nonprofit’s needs.
  • Product Managers – Act as the liaison between the team and the nonprofit, managing communication, feature scoping, and user feedback. They write user stories and help keep projects on track using Agile methodologies.

Check out our Wiki for more information on each role!

Project team applications occur during the Spring Semester and typically span the whole month of March. Students who complete the application process and are selected will join projects starting in the following Fall Semester.

Reach out to blueprint@stevens.edu and we’ll get back to you so you can join the Discord server! The Tech and Design Team are open year-round, and the goal of these teams is to allow students to learn at their own pace while contributing to Blueprint.

Since the applications for project teams occur in the Spring, freshmen are typically unable to join their first year. However, there are often a couple of members who drop from the project teams, and if you are active on the Internal Teams and express an interest to join, we may reach out to help fill the gaps!