Konrad Kaliciński
I build knowledge graphs on Neo4j, and I help teams work out whether they need one before they pay for it.
BACKGROUND
I have been writing software for a living since 2007: content platforms and e-commerce first, then four years building web applications for a company in Zurich, then senior full-stack and front-end roles. I am based in Wrocław, Poland, and work remotely in English and Polish. When a modelling workshop needs your experts and me in one room, I come to you for the day.
Knowledge graphs are where that work now points. The parts I care about are the unglamorous ones: modelling a messy domain so the questions people actually ask have an answer, getting data from several sources into one structure without losing where each fact came from, and testing the graph so you know it is right.
PUBLISHED ON THE NEO4J DEVELOPER BLOG
- Building an Ontology for a Knowledge Graph Is a Process, Not a Diagram(Jun 2026)
- The Ontologies You Shouldn't Build Yourself: A Field Guide for Knowledge Graph Builders(Jul 2026)
- POLE+O: The 5-Type Ontology That Solves the Hardest Part of Building a Knowledge Graph(May 2026)
- Knowledge Graphs Are the Accountability Layer for High-Stakes AI(May 2026)
- What are Spatio-Temporal Knowledge Graphs? And when do you actually need one?(May 2026)
Plus a weekly article on Medium: what works, what does not, and what teams get wrong.
CERTIFICATIONS
WHAT I WORK ON
- Ontology and schema design, starting from the questions the graph has to answer
- Ingestion from public registers, documents and existing databases, with provenance kept
- Question answering over a graph (GraphRAG, text-to-Cypher) with answers you can trace
- Testing a graph: competency questions as acceptance tests, invariant checks in Cypher
- Graph algorithms (Neo4j GDS) for dependency, risk and similarity questions
GRAPHS YOU CAN TRY
- Polish plant-protection register: public register + labels, live Q&A
- SEC 10-K filings: 25 annual reports of 5 companies, live Q&A
HOW I WORK
- One person, directly. You talk to the person who builds the graph.
- I start by checking whether a graph is the right tool. Sometimes the answer is vector search, SQL or a better spreadsheet, and I will say so.
- Scope and success criteria are agreed up front, as questions the graph must answer.
- I take on one project at a time, so start dates are agreed, not immediate.
CONTACT
The quickest way to reach me about a project is the contact form. For everything else, and for shorter notes on graph work, I am on LinkedIn and Medium.