What a Junior } should know

Follows team coding standards for C++/Qt. Uses clang-format and Qt Creator code style. Writes readable code with clear names. Passes code review without critical remarks.

Understands Qt ownership model: parent-child for QObject. Uses QScopedPointer and std::unique_ptr. Knows deletion rules for QObject without parent. Avoids dangling pointers through QPointer.

Understands basic multithreading in Qt: QThread usage for background tasks, signal-slot connections across threads, basic understanding of thread affinity in Qt event system. Follows team conventions for keeping UI responsive with worker threads.

Writes unit tests through Qt Test (QTest) with QCOMPARE and QVERIFY. Tests signals/slots through QSignalSpy. Understands test fixtures and data-driven tests in Qt Test.

Participates in code review as a reviewee for Qt/C++ code. Applies reviewer comments, understands coding standards. Leaves simple readability comments.

Uses Git for daily work: commit, push, pull, branch. Understands gitflow for Qt projects. Works with .gitignore to exclude Qt build artifacts.

Understands the fundamentals of MVVM Pattern. Applies basic practices in daily work. Follows recommendations from the team and documentation.

Knows Qt 6 and C++17 basics. Creates simple widgets through Qt Designer, uses signals/slots for connecting logic. Works in Qt Creator, builds projects through qmake/CMake.