I’m a freelance software engineer. In the last ten years, my primary activity, aside from managing Fhoster (a tech startup I founded in 2008), has been working as a functional analyst on all complex projects the company develops in-house.

As an analyst, I interact at all levels (both managerial and operational) with clients of all sizes, striving to create an interactive relationship aimed not only at deeply understanding the Customer’s needs, but also at identifying early any incomplete, ambiguous, or inconsistent requirements.

In this context, I leverage the experience, and technical skills accumulated in my first 20 years of work as a developer, designer, architect, and project leader to identify potentially problematic or overly expensive functional requirements relative to project budgets, and to proactively guide the analysis to identify alternative, equally satisfactory requirements for the client.

On a methodological level, alongside process modelling, I also create and maintain an up-to-date conceptual model of the managed data, establishing a complete and unambiguous glossary (or ontology) of the terms used during interviews and in the formalization of functional requirements, ensuring a precise definition of their meanings. In my experience, this approach minimizes misunderstandings between the analyst and the Customer, offers a common mental map to evaluate the coverage of the analysis effort, and ultimately reduces friction, significantly improving the efficiency of the analysis process.

Having spent more than two years working abroad (in the Netherlands and the UK) and having worked with foreign partners, I am fluent in English (C1 level in oral comprehension and interaction, C1 level in reading and writing).