Founding Engineer

Headquarters: Copenhagen, Denmark URL: https://memora.dk/ About Us At Memora, we're digitizing one of the oldest and most overlooked categories on earth: the cemetery. Most still run on paper maps, spreadsheets, and institutional memory. We are replacing this with an ecosystem for everyone who touches a cemetery: the leadership running it, the field teams maintaining it, the families visiting it, and the local partners serving them. We're backed by leading investors and guided by a team of experienced founders and engineers from well known tech names reimagining a category long overdue change. We're deliberately lean, and will keep it that way. Job Description This is a remote position. Founding Engineer - Memora We're hiring a Founding Engineer to step into one of the broadest roles on the team: A hands-on IC role with real product and cultural ownership. The Why Memora is growing rapidly. We need an awesome engineer in the team who can lead from all angles of the technical stack: • IaC end-to-end (Terraform, AWS, deploys, observability) • Data ingestion pipelines (large exports, QGIS, PostGIS, multi tenant setups) • Shipping core product features across NestJS, React, and React Native (Expo) mobile apps • Being a thoughtful, methodical technical voice in a small team where every engineer has outsized influence The What (real examples from what we shipped in the last 30 days) • Attribute-based filter systems across PostGIS, NestJS APIs, the React, and PMTiles-backed map tiles, so our clients can visualize by contracts, preservation status to even the flower season. • Data import pipelines that convert raw PDF cemetery maps into geo-referenced GeoPackages in QGIS, then ingesting into PostGIS. Owning the end-to-end onboarding for new clientele. • Terraform: multi-AZ RDS, ECS Fargate autoscaling, CI workflows, AI guardrails, WAF, SNS, and much more. • AI: Designing, evaluating and building harnesses where prompts for summaries and activity can be elegantly delivered to communities, tuning guardrails. • Production foundations such as RLS (multi-tenancy), idempotency keys + optimistic locking... so on The Stack • Backend: NestJS, TypeScript, MikroORM, PostgreSQL + PostGIS, Inngest for durable workflows • Web: React, TanStack Query, MapLibre + PMTiles • Mobile: React Native + Expo, Expo Router, native iOS/Android push • Infra: AWS (ECS Fargate, RDS, S3, CloudFront, SNS, Bedrock, WAF), Terraform, GH actions (OIDC), Logto • Observability: Grafana Cloud, Sentry, CloudWatch • Geospatial tooling: QGIS, GeoPackage, PMTiles • AI: AWS Bedrock + guardrails, Promptfoo for evals Who you are Must have: • Typically 8+ years building production software, including at least one role at a growth startup or as a founding/early engineer with sizeable revenue • Full-stack: comfortable shipping in TypeScript across backend (Node/NestJS or similar) and React-based frontends • Hands-on cloud infrastructure experience: you've owned a Terraform stack on AWS, not just consumed one • Strong relational database fundamentals: you've designed schemas, optimized queries, run migrations against large live datasets • Comfortable operating in a small team without a clear playbook: you can scope your own work, write your own docs, and triage your own bugs Strongly preferred: • React Native / Expo experience shipping to App Store + Play Store • PostGIS or any production geospatial work • Experience with row-level security, multi-tenancy patterns, or compliance-sensitive data (we're GDPR + public-sector) • Production AI/LLM work prompt design, evals, guardrails • B2B/B2G SaaS experience: sales cycles, real customer relationships, public-sector quirks Bonus: • Experience with cemetery, GIS, or public records systems A Note on AI Yes, we lean hard on AI coding tools: Claude, Perplexity, Cursor, etc. and we expect you to as well. Engineers who refuse them aren't a fit, but neither are vibe coders. We ship to municipalities managing data for real families, so the bar is robust, well-tested, human-reviewed code, not "the model said it worked." We treat these tools like a sharp junior pair-programmer: fast, occasionally brilliant, frequently wrong, and never the final authority. That means reading every diff, spotting when its tests are theatre, pushing back on its first "all-inclusive plan" building workflows with planning and review gates baked in, and being able to ship the same feature with the tools turned off. "AI wrote it" is never a defence in a postmortem. If that distinction is obvious to you, we should talk. If your instinct is to paste this post into Claude and ask for "the final application, make no mistakes", wrong place. We're hiring humans, not the sub-agents we already work with and know well. How we work We're building Memora to be the kind of company we'd want to work for ourselves: high trust, low bureaucracy, and full of people who care deeply about doin