Senior Backend Engineer (f/m/d)
Predium · 🌍 Munich
Sponsorship verdict
No sponsorship evidence yet
No government record and no wording either way. Not a refusal — ask the recruiter.
- No government sponsor record hereThis employer posted directly and does not match a government sponsor register.
- The posting doesn’t mention sponsorshipSilence isn’t a refusal — ask the recruiter before investing much time.
- Can’t check pay against the visa rulesNo salary stated. Germany EU Blue Card needs at least €50,700 a year (shortage-occupation / recent-graduate: €45,934). Source: https://www.make-it-in-germany.com/en/visa-residence/types/eu-blue-card, rules effective 2026-01-01.
- Confirmed live todayWhen a source last listed this job as open.
A verdict summarises public evidence; it is not legal advice and never a guarantee — the employer and the immigration authority decide. Sign in to factor in where you can already work.
Or apply yourself on the official page →
Why not apply?
No register record and no sponsorship wording in the posting. Worth asking the employer before investing significant time.
SponsorApply flags time-wasters so your applications go where they can land. These come from the posting's own wording — read the original listing to confirm. See better-fit alternatives →
Sponsor Radar — Predium
This employer posted directly and does not match a government sponsor register.
Past sponsorship or register membership never guarantees sponsorship for this vacancy or for you. Full Sponsor Radar for Predium →
About the role
Our Opportunity Over the past three years, Predium has built the leading real estate intelligence platform for ESG and value management in the DACH region - with the strongest names in the industry as customers: asset managers, housing companies, banks. Our customer base, our data, our credibility - that's valuable capital for the next step. Investment, credit, and asset management decisions in real estate are still made in Excel, case by case. We're now building the AI analyst that takes this work off people's hands - working directly on the customer's own data, scalable without adding headcount. We're well-funded, and we're bringing AI into real estate. Your Mission As a Senior Backend Engineer, you own the systems behind our platform: the GraphQL API, the relational data model, the background processing that turns customer documents and spreadsheets into structured data, and the permission model that lets a single owner and a bank with hundreds of portfolios use the same product. Most of your work runs from schema design all the way to the resolver. You partner with product, design and other engineers to make sure we build what matters - not just what you have been told to do. You take real responsibility for production: when something is slow, you find out why, whether the answer is a bad query, application code or the infrastructure underneath. You also help us make AI reliable in production. Document extraction, long-running analysis jobs and agentic features are core to where the product is going, and we need people who make these workflows testable and dependable rather than impressive in a demo. Our company size of ~40 people ensures that the best idea wins and political discussions are kept aside. And every line of code helps to improve the carbon footprint of real estate properties. Tech stack: TypeScript (NestJS backend, React frontend), Hasura/GraphQL, PostgreSQL (multiple databases incl. PostGIS), queue-based job processing, AWS (ECS / Elastic Beanstalk, S3, SES, Textract), IaC, Claude but all agents welcome What you'll own • Build features across our Hasura GraphQL API, NestJS and Postgres. From schema design to resolver. • Model complex real estate and ESG domains in relational schemas. We run several Postgres databases side by side (one of them geospatial), and schema decisions here have consequences but also positive impact. • Own background processing: Excel imports, document extraction, long-running analysis jobs, 3D and image processing. Queues, retries, jobs that spawn other jobs - and figuring out what to do when step 3 of 7 fails at 2am. • Develop our permission model. Customers range from a single owner to enterprises with organization/portfolio/building-level access. • Integrate LLMs into backend workflows - especially document and data extraction - and make them reliable, verifyable and testable. • Debug production. Navigate Grafana dashboards and traces to find out why something is slow or failing, whether in the app, the CI/build pipeline or the infrastructure. • Spot overgrown or overly complex parts of the codebase and simplify them without being asked. Paying down complexity is part of the job. What success looks like • You have shipped features end-to-end across schema, API and background processing that our customers actively use. • Our async processing (imports, extraction, analysis jobs) is measurably more robust: fewer silent failures, clear retry and recovery paths, and observability that tells us what broke and why. • You have taken ownership of at least one core area e.g. the permission model, the job orchestration layer or the LLM extraction pipeline and are the person the team goes to for it. • You have raised the bar on testing and developer experience in the backend, and oth