Skip to main content
Mati Data, home

Check the answers yourself

The questions hiring managers and clients ask before a first call. Each answer links to public work you can open and verify.

  1. Can you design and build a data pipeline end to end?

    Yes. Two public pipelines run from a source API through PostgreSQL, Debezium and ClickHouse to tested dbt marts, with orchestration and monitoring around them, and each design decision is written up.

  2. Do you test and monitor what you build?

    Every figure in the evidence ledger on the home page links to the file behind it: the tests, the alert rules and the monitor that reconciles row counts between the source and the warehouse.

  3. Can you explain the trade-offs behind a design?

    Each case study has a section on decisions and trade-offs, and the architecture page sets out how I choose between a warehouse, a lake and a lakehouse, and between ETL, ELT and change data capture.

  4. Do you document what you build?

    Each public pipeline has its requirements, a data catalogue of every table and column, the naming conventions the code follows, and a design report with the trade-offs.

  5. Do you work on AI as well as data?

    Yes, as a second discipline that sits on good data: a retrieval assistant over local documents, OCR for Ethiopic script, and research on quantising small Amharic language models.

  6. Are your credentials real?

    Each one links to the issuer's own page, so you can check it rather than take my word for it. The DataCamp tracks are career tracks, not vendor certifications.

  7. Have you led or taught other engineers?

    I led the Google Developer Student Club at Wolaita Sodo University, and my community and teaching work is listed on the About page.

  8. What do people you have worked with say?

    A recommendation from a senior data engineer I worked with is on the About page, and every recommendation I have received is on LinkedIn.

  9. Where is your production experience?

    On the CV, role by role, with the platforms I built on and what they were for.

Still have a question?

Ask it directly, or see how an engagement would start on the services page.

Get in touch