Backend / Platform Engineering Partner

Djaminn is building a music collaboration platform that helps musicians find each other, connect, and work together. We are looking for an experienced backend/platform engineering partner or small senior team to help us build the technical foundation for the next stage of the product. The right team will bring backend engineering, cloud infrastructure, search, discovery, and practical AI implementation experience, with one named technical lead responsible for communication and delivery. We want to work with people who can understand the product deeply enough to spot the real technical problems, not only complete assigned tickets. A good example is search. A musician searching for “soft piano” or “female drummer” may be expressing a sound, mood, role, identity, instrument, collaboration need, or creative intent. Those searches only work if the platform has been designed to understand and index meaning across profiles, music, projects, images, tags, activity, and interpreted metadata. We need a team that can see those product questions early and shape the backend around them. The work will include designing and building scalable backend services and APIs, improving the platform architecture, supporting features such as profiles, discovery, collaboration matching, messaging, notifications, projects, and community workflows, and making sure the system remains reliable as usage grows. Search and discovery are especially important. We want users to be able to type what they are looking for and get useful results across artists, songs, projects, bands, genres, instruments, moods, and collaboration needs. This may involve keyword search, structured metadata, ranking, recommendations, semantic search, vector search, and interpreted data from music, profiles, images, and user behaviour. We need practical judgement on what to build now, what to avoid over-engineering, and what foundation to lay for later. The team should also be able to own or improve the cloud and DevOps side: deployment pipelines, environments, monitoring, logging, security, backups, performance, reliability, and infrastructure as code where appropriate. We want production systems that are maintainable, observable, and well documented. We expect a clear working structure. There should be one named technical lead as the main point of contact, regular planning and prioritisation meetings, short progress updates during the week, technical reviews, sprint demos every one or two weeks, a visible backlog, clear owners, documented architecture decisions, and honest communication about risks and trade-offs. Djaminn must retain full ownership of the code, infrastructure, accounts, documentation, and technical decisions. We are especially interested in teams who have experience with: Social platforms Creator tools Marketplaces Community products Matching systems Recommendation systems Search-heavy products Music, audio, or creator communities AI-assisted discovery When applying, please share: Examples of products or platforms you have helped build The role your team played in those projects Evidence of backend systems running in production at meaningful scale Examples of search, recommendation, matching, semantic search, AI-powered discovery, or interpreted metadata systems you have delivered Details of your cloud and DevOps experience The proposed team structure Who would act as the technical lead and main point of contact How you usually work with clients Your preferred delivery cadence References or case studies, where available We are looking for a practical senior team with strong product instincts, clear communication, and the ability to turn fuzzy product needs into robust technical systems. The goal is to build a platform that helps musicians discover the right people, sounds, projects, and opportunities as Djaminn grows. For a first selection procedure, we will schedule the preferred suppliers for 20 minutes presentation.