About
JUNI is a nonprofit ecosystem for science and spin-offs in Berlin. It operates programs across seven SaaS tools, including newsletters, events, community, CRM, forms, applications, and coworking, supported by a Postgres database intended to serve as the single source of truth for people.
Tasks
•Build the layer connecting the systems with the database in both directions
•Help shape the data model and determine when it needs to change rather than adapting it around a single source
•Integrate each system into the database through multiple inbound pipelines and resolve identities across systems
•Send database-defined states to the platforms that execute them
•Keep bidirectional synchronization reliable, including handling platform feedback and preventing unsubscribed people from being added again
•Deliver KPI data to a BI tool; dashboard building is not part of the role
•Make the data searchable in natural language
•Document decisions and maintain pipelines in GitHub
Requirements
•Experience integrating third-party APIs and webhooks, including pagination, retries, signature verification, rate limits, undocumented payload structures, delayed or out-of-order events, and sources that emit events without specifying what changed
•Experience with bidirectional synchronization, loop prevention, echo suppression, and conflict resolution
•Strong experience using Postgres as an application database, including plpgsql functions, triggers, constraints, and RLS to enforce write-time rules
•Treat idempotency as a core practice; pipelines must be safe to rerun without changing data
•Work cleanly with Git, migrations, pull requests, and reviews
•Experience handling personal data under GDPR and understanding its restrictions on data ingestion
•Written English proficiency for predominantly asynchronous work and readable documentation
Nice to have
•n8n or another orchestrator, Supabase
•Relevance work on a search index such as Elasticsearch, OpenSearch, or Meilisearch
•Experience as the sole person responsible for a system
•German
Conditions
•Freelance engagement, starting as soon as possible
•Initial term of three months, with further needs to be assessed afterward
•Remote collaboration is predominantly asynchronous, with live conversations planned at the beginning
