Skip to content
Data, software & everyday workBased in Belgium

Beyond data pipelines, I build tools and improve workflows to help people get their work done with less effort and better results.

Explore my work ↗Get in touch
Hello, that's me ↙
Danil Zhuravlov
Curious about how things work. And how they could work better.
A personal collection of things I build.Take a look below ↓

01 / Selected work

Built from
a real reason.

Different projects. The same starting point: something could be easier, clearer, or more useful.

01 / CRMInternal tool · Adoption by choice

Built around people.
And their process.

I noticed sales colleagues struggling with their existing tools and Excel-based processes. Nobody had assigned me a CRM. I started building one.

I adapted the application to the way they already worked. They could keep using Excel, try the CRM, or combine both. Moving everything at once was never the condition for getting something useful.

The application exists; becoming the preferred choice is still the goal. I want real use and feedback to guide what comes next, until the value of using it is a reason to switch.

Keep ExcelUse bothTry the CRM
A design decision: give people time and choice.
02 / TaskTreePersonal project · Desktop application

My work.
In context.

The Microsoft 365 tools I had did not fit how I wanted to track priorities, project stages and completed work. So I built TaskTree around that view of my work.

Projects break down into nested tasks, with statuses and priorities that keep both the next action and the larger picture visible. Completed work stays part of the story.

I can use the interface or operate the application through conversation: ask about tasks, change a priority, or update a status. The assistant uses the same application API, so it works on the same task data. Python, Flask and SQLite keep the application and its data together on the desktop.

03 / JinPersonal project · Telegram

A familiar place
to pick things up.

I wanted help with everyday responsibilities without losing sight of my longer-term ambitions. I also did not want another application to maintain.

So I chose a familiar Telegram conversation. Jin has a name, a consistent personality and proactive responsibilities. Those are interaction decisions: how he remembers context, when he checks in, and when he should leave me space.

The current implementation includes tasks and reminders, saved project context and drafts, and bounded proactive suggestions with quiet hours and pause controls. It is a private project for my own use. How helpful that interaction feels over time is something I am still developing through use and feedback.

A Telegram conversation with Jin about a train journey and weekend plans. A personal name is redacted.
Jin in use: checking a journey and recalling weekend plans. Personal name redacted.

Also in my working life

Small changes.
Useful differences.

Bringing production into view

Geospatial production · Internal tooling

Production status was spread across batch scripts, message-queue consumers, spreadsheets and files. Understanding what was happening meant piecing those sources together by hand.

I brought that information into a desktop dashboard focused on what the production team needs. It gives colleagues a way to check progress without having to run scripts or keep the whole process in their heads.

Making silent failures visible

Data pipelines · Reliability

A pipeline step could fail silently, leaving an empty output file that might only be noticed much later.

I added checks that surface the failure and its reason earlier. The useful change is giving people something they can act on before more processing depends on a missing result.

Taking repetition out of a weekly task

Workflow automation · Internal tooling

A colleague repeated the same setup every week, with the same structure and different input for each project.

I turned that repeated sequence into a small Python tool. It is a modest piece of software with a clear purpose: take the mechanical steps out of a routine that still needs a person's judgment.

02 / How I work

Software should
earn its place
in your workflow.

I start by understanding how people already work and where things become difficult. Then I build a useful first improvement, introduce it gradually, and refine it with the people using it. Straightforward interfaces and automation help reduce effort without forcing everyone to change their process overnight.

  1. 01

    Notice the friction.

    I look for repeated effort and missed opportunities, including things nobody has put in a specification.

  2. 02

    Start with something useful.

    I build a manageable improvement around the team's existing process, with an interface people can use and fewer manual steps.

  3. 03

    Let real use and feedback shape what comes next.

    I listen, adjust and add incrementally. People need time and choice; the tool should give them a reason to use it.

03 / A little about me

Still learning.
Still building.

Ukrainian. Based in Belgium.

I'm a data engineer at Vansteelandt BV, where I've worked since March 2025.

My work includes geospatial production for aerial survey, automation, applied machine learning and quality control before deliverables reach clients. Building for colleagues who do not write code has made usable interfaces a practical priority.

I'm Ukrainian and now based in Belgium. The war changed my life profoundly. Being Ukrainian remains an important part of who I am, and those experiences have strengthened my determination to grow and contribute something meaningful through my work.

I came into engineering from outside it. I remember what it feels like not to know how the software works, and I try to keep that perspective when I build.

View my CV

04 / Let's talk

Interested in what I'm building, have an idea to share, or see a chance to collaborate? Get in touch.

Get in touch

hello@danil-zhuravlov.comLinkedIn ↗CV ↗