Following

A1: Beginner
A2: Basic
B1: Intermediate
B2: Advanced Intermediate
C1: Advanced
C2: Proficient

I have designed reusable APIs and complex domain models using generics, discriminated unions, and strict type checking
I regularly build production applications with TypeScript using interfaces and standard types
I have mainly used TypeScript in existing codebases with limited ownership of type design
My experience is primarily with JavaScript, with little or no TypeScript
I have no experience with TypeScript

I have built and maintained production applications with Elm
I have used another functional language, such as Haskell, F#, OCaml, or Clojure, in production
I apply functional programming patterns in TypeScript/JavaScript but have not used Elm professionally
I have limited functional programming experience, but I am willing to learn Elm and use it as my primary language
I am not interested in working primarily with Elm

Canvas 2D API
WebGL, directly or through libraries such as Three.js or PixiJS
SVG with custom interaction and rendering logic
DOM/CSS with custom animation and interaction logic
Only prebuilt UI or charting components
None of the above

Excessive layout or style recalculation, including layout thrashing
Slow or excessive painting and compositing
Dropped animation frames caused by main-thread work
Canvas/WebGL bottlenecks, such as excessive draw calls or inefficient redraws
Memory leaks or excessive allocations affecting interactive performance
I have not personally diagnosed and resolved rendering performance problems

I designed explicit state transitions and coordinated input, animation, and rendering, including edge cases such as interrupted interactions
I managed custom interactions using component state and event handlers, with limited coordination across animations
I mainly relied on a library or game engine’s existing interaction model without significantly extending it
I have not implemented complex interaction logic

I designed constrained APIs or data models and used generated/property-based tests to check invariants across configurations
I implemented runtime validation and automated tests covering valid, invalid, and boundary configurations
I tested a fixed set of expected configurations, mainly through examples or manual testing
I relied on the caller or content author to provide valid configurations
I have not built configurable components with these requirements

I implemented deterministic state updates separately from rendering and side effects, allowing interaction logic to be tested independently
I separated some business logic, but interaction state and rendering remained closely coupled
I implemented most interaction logic directly inside UI components or rendering callbacks
I have mainly worked with existing architectures without owning these decisions

I use AI tools consistently across development tasks and have a defined approach to reviewing and validating their output
I use AI tools regularly, mainly for code completion or generating small pieces of code
I occasionally use AI tools for explanations or troubleshooting
I do not currently use AI tools