Product leadership · Building · Enabling teams
I’m Angelina Filip. I have more than 25 years in technology, including around 11 years in product and leadership roles since Carus. I lead and enable teams, work with stakeholders to make decisions, and help people overcome obstacles and take ownership. I also design, code, test and build products myself.
People leadership, product judgement and stakeholder management are a large part of my work. I connect the decisions about what to build with the people and systems needed to deliver it.
Most recent full-time contract · 2025–2026
At Sanoma Learning, I supported publishers in Belgium, the Netherlands, Finland, Sweden and Poland with day-to-day SAP Order-to-Invoice feature development and delivery. I also led Nowa Era’s KSeF implementation across SAP and Pagero through testing, go-live and hypercare, so the Polish publisher was compliant on time when mandatory e-invoicing came into force.
Across RTE, PO and PM roles, I have hired people, coached them, led performance reviews, handled stakeholder and customer feedback, and set expectations around quality, integrity and engineering practice. The job titles changed. The people leadership did not.
I listen before judging. Sometimes one senior person is dominating the room. Sometimes management is ignoring valid engineering risk. Sometimes experienced people are being micromanaged across a cultural divide. I work out which challenge we actually have, make expectations clear and give people enough trust to take ownership.
How I enable and lead teamsI work with stakeholders to understand what matters, make the choices clear and agree on priorities. Teams need that context to make good decisions. Stakeholders need an honest picture of progress, risks and dependencies.
WEBZY is my main independent product today. Alongside it are smaller products, experiments and examples from my work in enterprise software. Each case explains my part in the work and where the product stands.
01 · Independent product · Active development · 2026
I built WEBZY from the foundations up. Then I caught myself making people operate those foundations instead of simply using the product.
Read the case
02 · Independent product retrospective · 2026
I asked AI for a prompt, gave it to Lovable and watched a plausible-looking app appear. Now I know better: a prompt is not a product definition.
Read the case
03 · People leadership · International teams · Product organisations
I have repeatedly inherited teams described as challenging or slow. I listened first, found the actual challenge and gave strong people room to contribute and take ownership.
Read the case
04 · Product judgment · Interaction design · Shipped work
Small feature requests often expose a larger broken journey. I find that larger challenge, question weak solutions and work with the team to ship something coherent.
Read the case
05 · AI workspace for crochet and knitting · Working Lovable product · 2026
I know crochet well enough to know when a confident answer is dangerous. I designed YarnSmith to help makers analyse photos, check patterns, calculate gauge and match yarn without pretending estimates are facts.
Read the case
06 · Universal SSH Key Manager · Enterprise security
Large companies had decades of SSH keys and no reliable picture of who could access what. UKM had to find that invisible mess, explain it and help people clean it up safely.
Read the case
07 · PostgreSQL advisor · Independent prototype
A pricing calculator could tell me what a PostgreSQL configuration would cost, provided I already knew which configuration I needed. I built a focused AI prototype to explore the missing step.
Read the case
08 · CROSHIKO · Shopify website · Independent hobby business · 2026
I wanted one place for patterns, tutorials, experiments and whatever craft I wander into next. So I rebuilt CROSHIKO on Shopify instead of pretending a hobby has a stable roadmap.
Read the case
09 · Portfolio design · Information architecture · AI-assisted build
I built a polished portfolio with the wrong structure, watched people get lost and rebuilt it around what they actually needed to understand.
Read the caseUnderstand the problem, question the assumptions, make a decision and test it against what happens. I enjoy the difficult parts, and I care about finishing.
First decide who is trying to do what. Then decide which parts of the machinery they genuinely need to see.
Expert software often contains real complexity. Keep it. Remove the accidental mess created by databases, implementation shortcuts and years of additions.
This is a journey rule. Consistent components can still lead people through the wrong sequence of work. A design system cannot rescue the wrong product structure.
Keyboard use, visible focus, contrast, useful touch targets and forgiving controls belong in the normal definition of working software.
Some of my best judgment came from building the wrong thing, finding out why it failed and changing how I work. Hiding the mistake would waste the most valuable part.
Performance challenges are real. So are unclear decisions, ignored technical risk, bad incentives and team dynamics that silence useful voices. Find the actual challenge before labelling the people.
My work extended beyond engineering even before Carus. At Nokia and Nokia Siemens Networks, I also worked as a Fault Coordinator and Competence Development Specialist. Since Carus, my roles have centred on product ownership, product management and leading teams.
Built and maintained the Siemens Telecom Innovation Centre intranet and internal tools, using web technologies, LDAP and Python.
Worked on Webhancer’s corporate website, including backend, frontend, information structure and visual design.
Spent more than seven years in global telecommunications across systems engineering, fault coordination and competence development.
Designed and built Universal SSH Key Manager, from complex access journeys and visual design through frontend implementation.
Led a distributed web team and helped turn ferry reservation software into clearer customer journeys and shipped mobile products.
Owned high-availability and platform work across international teams in regulated clinical-trial software.
Led identity and access work, fixed fragmented login and SSO journeys, reviewed design quality and led a remote multicultural team.
Owned SAP Order-to-Invoice product work across five countries, including leading Poland’s KSeF implementation through go-live and hypercare.
Built and tested AI products in startups and independently, including WEBZY, YarnSmith, PostgreSQL Advisor and other focused prototypes.
I like complicated products, direct conversations and work that still has something difficult left to solve.
I have spent more than 25 years building products from almost every side: software engineer, full-stack developer, UI and UX designer, frontend owner, Product Owner and Product Manager. Those job boundaries are useful for organisation charts. Real product problems rarely respect them.
I genuinely like complicated products. I just refuse to dump their internal complications on the user. When something does not make sense, I do not pretend that it does.
When I am not building enterprise products, I make things with yarn, fabric, beads, wood and whatever else catches my attention. Crochet is the long-running obsession. Craft is wonderfully honest: if the structure is wrong, decoration will not save it. And yes, I also build AI tools and other passion software projects for fun :D