Hi there ,
We're looking for new colleagues to join our startup and develop a fast, intuitive and scalable community platform. If you're interested, we'd love to get to know you a bit over coffee.
We look forward to meeting you!
We're looking for an experienced Back-end engineer who has experience in a typed functional language like Scala, Haskell, OCaml, PureScript or Elm and is interested to learn F# .
We're Crowded : A b2b SaaS out-of-the-box community platform that comes in your brand and can be anything from a forum to an Upvoting Listicle platform, intranet or networking platform.
We work from Amsterdam, and are looking for full-time, self-directed people.
Our challenges are diverse as we run into anything from complex and performant tree traversals in SQL, authorization resolvers, parsers, events tooling for custom analytics, hand tuning SQL and other challenges like these.
What kind of company is Crowded?
We're a self-funded startup from Amsterdam, 3 years old, and growing. Our technology and UX is at the core of the company and it's a shared passion across the entire team (including sales / support).
Our daily focus is to build the most intuitive and flexible Social Platform there is.
Among our customers we serve :
What are we building?
Our backend is developed on the cross platform and recent .Net Core 2 platform. We write functional flavored C# and F# on macOS / linux.
And then we deploy it to our linux fleet. We strive to find the right abstractions to keep complexity low and we love keeping our stack simple.
We'd rather optimize on top of a few pieces we're expert on than repeatedly add new specialized infrastructure, this keep us sane as a small team.
We're building a customizable, extensible and white-label community platform . It takes many different shapes, from being a simple forum, to a full blown networking website or even a marketplace.
Currently 50+ different communities run on Crowded, on their own domain, with their own branding, each with vastly different configurations but all running the same software on our servers.
Our customers depend on our product daily and trust us with their brand and image so quality and stability is very important to us.
It's a nice engineering challenge to keep all parts functioning while we're continuously moving things around or introducing new functionality across all our different customers.
That's why we take a step back and look for the right abstractions pieces before we start building features. Each feature really has to add value to the whole and should be a good fit for a large portion of our customers.