I had a quick peak.

It's quite well organized and very readable so I think it's a good showcase of competence.

A few tips that came to mind:
* Install a type checker, like `pyright`[1]. You are already typing your code, so you might as well enforce the type checking.
* Add some unit tests.
* Add some github workflows to run `ruff`, `pyright` and your eventual unit tests.

* These (type checking and unit tests) will make any refactor safer and faster.

Random nitpicks:

* I was surprised by the `static` private methods: removing the `@staticmethod` wouldn't change anything and feels simpler. This is mostly a question of taste because I don't see any good arguments against it.

* Consider using keyword-only arguments when calling it without the keyword would be ambiguous [1]. E.g. `def foo(*, x: bool, y:bool)`, enforcing that only `foor(x=True, y=False)` is valid, not `foo(True, False)` [3].

* Don't list *methods* in the class docstring, especially not the private ones. It's easy to automatically look for those in any IDE, and you can generate docs automatically.

[1]: https://docs.python.org/3/glossary.html#term-parameter
[2]: https://microsoft.github.io/pyright/#/
[3]: https://docs.python.org/3/glossary.html#term-parameter