README.md

How I work

I ask a lot of questions upfront. Not to slow things down — but because I'd rather spend 30 minutes understanding the real problem than 3 days solving the wrong one. Definitions matter. Context matters. I won't start until I know what "done" actually means.

I'm also the person you bring in when nobody has done it before. New tool, unfamiliar stack, blank-slate problem? Give it to me. I'll come back with something that works.

What I'm good at

• Translating technical complexity into something non-technical stakeholders can act on
• Seeing the systemic problem underneath the reported symptom
• Owning things end-to-end — from data model to dashboard to the person using it
• Working across teams: I've collaborated with Sales, CS, Product, and Dev, and I know how to speak each language
• Give me an investigation task and you'll make my day — digging through raw data, repos, and dependencies to find anomalies or trace the source of something broken is, genuinely, my idea of a good time

What I'm learning

Currently going deep on data engineering — Airflow, Spark, and cloud infrastructure. I want to own the full pipeline, not just the analytical layer on top of it.

Feedback

I'm very open to direct, constructive feedback — please don't feel the need to wrap it in compliments or caveats. Just say it.

On the flip side, I'm actively working on giving feedback more proactively. If you feel like I should have said something and didn't — prompt me. I won't be offended, and I'll probably have thoughts.

Communication

I prefer to keep conversations close to the context they belong in. If something relates to an existing issue, doc, or RFC — let's talk there, not in a separate thread that gets lost. That said, I use Slack's "Save for later" heavily and will often bring things back to the right place eventually.

When speaking verbally, I sometimes take a while to get to the point. If you notice this — call me out. I'm actively working on it and won't take it personally.

Location, time zone & work hours

📍 Warsaw, Poland — GMT+1 🇵🇱

I try to keep regular 9-to-5 hours as much as possible — I think sustainable rhythms make for better work. That said, I'm flexible when the situation genuinely calls for it.

My most productive window is roughly 10–4 pm, so if you need deep focus work from me, that's when you'll get my best.

Outside of work

I play squash, cook, and collect languages — I speak four and plan to add more (German, Italian, and Portuguese are next in line). I'm genuinely fascinated by different cultures and love moving through the world rather than just observing it.

India holds a special place — the country and the culture have a permanent spot in my heart.

Also: big cheese geek here. Ask me my favourite fun fact about cheese 🧀

How to work with me

• Give me deadlines for everything — I love control and organise every task across my day, week, and month.
• Give me context and a goal — I'll figure out the path
• Frequent check-ins beat a big review at the end
• Trust me to deliver, then look at the results
• I love structure: calendar blocks, clear task statuses, async updates
• I use Slack emoji statuses religiously 👀

Other quirks

I sometimes go deep trying to solve something on my own before asking for help. My self-taught instinct to "figure it out first" is strong (I'm working on it). If you see me stuck, feel free to nudge me.

When I'm thinking hard or under pressure, I can get very quiet and start frowning. It's not a mood — it's just how my brain looks from the outside when it's busy. Worth knowing upfront.

Oh, and I might be one of the few people on earth who actually enjoys writing documentation. Yes, voluntarily. No, I don't know what's wrong with me either.