ABOUT GLASSFLOW:

GlassFlow is a startup building the open-source data streaming infra for the next generation of developers and AI companies: Easy to use, massively scalable and optimized for the AI era.
We’re a Berlin startup with a Silicon Valley mentality, backed with $4.8m from Upfront Ventures, the CEO of GitHub, the ex-CTO of Aiven, and more world-class investors.
The founders are serial entrepreneurs with more +10y of experience in building and selling data products.

YOU ARE:

• Deep expertise in Go.
• Hungry, competitive, and resilient.
• Someone with impressive achievements that prove you’re a 10x builder.
• A fast learner who thrives in chaos.
• Hands-on, pragmatic, and deeply technical.
• Actively looking for startup culture.

PREVIOUS EXPERIENCE THAT COULD BE HELPFUL:

• Experience with public or private clouds (AWS / GCP / Azure)
• Experience with K8s, Docker, Docker Compose
• Experience developing on and using queue systems like Kafka, SQS, and RabbitMQ
• Worked in fast-growing environments or early-stage startups
• Openness to using AI tools in coding (e.g., Cursor) is considered a plus
• Ability to adapt quickly and make compromises in writing code when necessary

WHY IS THIS ROLE SPECIAL

This isn’t just another backend role. As a Founding Engineer at GlassFlow, you’ll be shaping the core technology, culture, and trajectory of the company. The code you write will power pipelines for billions of data events created by enterprises around the world.
You’ll be working in a fast, high-ownership environment where speed matters, curiosity is rewarded, and ambition is the norm.

WHAT YOU’LL DO

• Build and scale high-performance, low-latency systems in GoLang.
• Take complete ownership of projects from idea to production.
• Ship fast, break things, learn, and ship again.
• Help define the technical culture of GlassFlow.
• Work directly with the founders to solve problems in a way that no one has solved before in real-time data infrastructure.

THIS ROLE IS NOT FOR YOU IF YOU:

• Expect long and detailed roadmaps.
• Need a structured process or step-by-step instructions.
• Want the “safe” path.
• Are afraid of chaos.
• Can’t handle pressure.
• Want “perfect” code.
• Are afraid of wearing multiple hats.