Fullstack Software Engineering Intern

Join BrewBase, a pioneering company in the field of sustainable protein production. As a Fullstack Software Engineering Intern, you will work closely with scientists to understand their processes and build software that meets their needs. You will have the opportunity to see your work in action and make immediate improvements based on user feedback. This internship offers a unique experience in a fast-paced startup environment, with a focus on sustainability and innovation.

• Collaborate with scientists to understand their processes and requirements, and translate them into software solutions.
• Design and implement software modules for BrewBase, focusing on schema design, API design, and user interfaces.
• Iterate on your work based on user feedback, ensuring that the software meets the needs of the scientists and improves their workflows.
• Full-stack. TypeScript, React, Postgres, comfortable across frontend and backend. You don’t need to have used our exact stack
• Fast learner. Excited to dive into fermentation biology, analytical chemistry, and food science — domains few software engineers ever touch
• Builder mentality. You’ve built things outside coursework. Side projects, open source, something that runs and has users. Show us, don’t describe
• You have taste. We care about interfaces that are dense, fast, and precise. If you have a point of view about UI, you’ll enjoy it here. If you think a modal solves problems, less so
• Mission driven. Rewriting how the world makes protein genuinely excites you
• Bonus points for: data visualisation done well, time-series data at scale, Python for analysis and automation, lab instrumentation or scientific software, a biology, chemistry or food science background, previous startup experience
• SQL, properly. Not an ORM’s worth. You should be comfortable in Postgres and know why a constraint beats a comment
• You think in data models. This is the one we weight hardest. The difficulty in BrewBase is almost never the React — it’s deciding what a thing is, and what has to still be true about it in two years. You should have designed a schema that someone else then had to live with, and have opinions about how that went