Graphic Engineer

Job description

We’re not going to sell you on this role. In fact, our client specifically asked us to do the opposite: to be brutally honest about what this job actually entails.

Most candidates won’t want it. If you’re looking for work-life balance, predictable hours, or a comfortable corporate job, this is not a job for you.

What You’re Actually Signing Up For

• Extreme autonomy = extreme responsibility. Don’t expect task lists or daily standups where someone tells you what to do. They onboard carefully (one person at a time), but after that, you’re expected to know what needs to happen next and just do it. If you need hand-holding or structure, you’ll probably be let go.
• Tiny team by design. This means every single person must be an exceptional contributor, the best at what they do, no passengers.

Tech Stack

• Frontend: Svelte 5, TypeScript, Tailwind
• Backend: Golang
• Graphics: Custom WebGL/WebGPU wrapper
• Infra: GCP, Firebase, Cloudflare

Responsibilities

You’ll be building a rendering engine from scratch. Not maintaining existing code. Not tweaking features. Building the core infrastructure that makes real-time, AI-native design possible in the browser.

Specifically:

• Designing and implementing high-performance rendering systems (WebGL/WebGPU)
• Building real-time graphics, animations, and interactive canvas behaviors
• Obsessive performance optimization — every frame, every pixel, every millisecond
• Working with or building on top of engines like Fabric.js, Konva.js, Pixi.js, Two.js
• Collaborating with frontend engineers to integrate systems seamlessly
• Making architecture decisions that will define the product for years

Some weeks you might spend entirely on making something 10ms faster.

If that doesn’t excite you, this isn’t your job.

Requirements

• Deep knowledge of computer graphics and real-time rendering
• Real experience with canvas rendering engines (Fabric.js, Konva.js, Pixi.js, etc.)
• Strong math foundation — vectors, matrices, transformations, shaders
• Experience building graphics engines, simulation systems, or performance-critical browser applications
• Ability to work independently without hand-holding

Nice to have:

• CS or Math degree (but they care more about what you can actually do)
• Open-source contributions in rendering/graphics
• C++, Rust, or other low-level languages

Additional Comments

The opportunity:

• Building something that doesn’t exist yet : AI-native design tools where AI is a co-creator, not an assistant
• Backed by serious people who’ve built billion-dollar companies before
• Work with a 6-person team where everyone is technical and committed (no bureaucracy, no meetings about meetings)
• Ownership of critical systems. You’re not a cog, you’re building the machine
• Direct impact on architecture decisions that will define the product
• Autonomy to solve problems your way. If you know a better approach, you implement it
• Total compensation that reflects the values.

This role is for someone who:

• Reads the above and thinks “finally” instead of “no thanks”
• Has been frustrated by slow pace and politics at larger companies
• Wants genuine ownership and autonomy
• Is willing to sacrifice comfort for the chance to build something exceptional

This is NOT for someone who:

• Values stability and predictability
• Needs clear structure and management
• Wants to keep work contained to 40 hours/week
• Is exploring options casually

If you need structure, clear direction, or work-life boundaries to do your best work, we won’t work well together. If you thrive when left alone to solve hard problems and don’t mind sacrificing everything else to build something exceptional, then we should talk.