Technical direction
Architecture, standards, estimates and roadmaps, written down and then proven in working code. I review, mentor and make the calls nobody else wants to make.
Hi, I'm
a software engineer
Fourteen years of building the quiet machinery behind products people use every day: marketing platforms, CRMs, cloud infrastructure, data warehouses, and the occasional game world. I care how a system feels as much as how it runs, and I build it end to end, from the first line of the theme to the last node in the cluster.
Tap the scene to summon a wave, or to attack faster. Skeep heals, Cindy distracts, Paul hits. Allow game saves and your level, XP and waves stay in your browser.
Most teams split the work: one person shapes it, another builds it, a third keeps it alive. I've spent fourteen years doing all three, and it shows in the details.
I work independently, end to end. I set the architecture, write the code that proves it, and own the pipeline that ships it. Teams bring me in when the stakes are high and the brief is still taking shape: marketing platforms, Salesforce extensions, cloud infrastructure and data.
After hours, I build ZenithArch Shell, my own Linux desktop environment, and games in Unreal Engine and C++. It's where ideas get tested long before they reach a client.
Type, color, motion and copy get decided once, as tokens, and every screen inherits them.
Pipelines, rollbacks and monitoring go in first, so launch day is quiet.
From DNS and server config to the last hover state. Fewer handoffs, fewer gaps.
Original value, updated value, who changed it and when. Data you can trust is data you can explain.
Hire me for one of these or all of them. Most projects touch at least three.
Architecture, standards, estimates and roadmaps, written down and then proven in working code. I review, mentor and make the calls nobody else wants to make.
Design systems turned into production code. Type, color and motion defined once as tokens, so every screen feels deliberate and every Figma handoff lands intact.
WordPress built from scratch: custom themes, page-template systems, mu-plugins and REST endpoints, with Elementor only where it earns its place. Hardened, cached and fast.
Customer portals on Lightning Web Runtime, LWC components, Apex services and the glue that moves leads from website forms into the CRM.
AWS, containers and CI/CD that make releases routine, plus edge security: WAF rules, bot protection and rate limiting tuned against real traffic.
ETL pipelines and warehouses that keep the original and updated value side by side, with a full JSON audit trail. Reporting on BigQuery.
Chat-ops assistants that answer CRM questions in team chat, retrieval pipelines, and local models running on hardware you own.
Gameplay systems in Unreal Engine 5 with C++, small engines in C++20 and raylib, and the odd retro homebrew build for real hardware.
Nine disciplines, one person. Here's what I reach for, from the first prompt to the last backup.
Assistants I direct, and models I run on my own hardware.
Engines from AAA-grade 3D to pixel-perfect 2D.
Pipelines, containers and servers I configure myself.
The everyday toolkit for platforms and products.
CRM add-ons from portal to pipeline.
From brand assets to quick social graphics.
Locked down first, then made fast.
The machines behind the machines.
Pipelines with an audit trail, and dashboards that prove the work.
Out of the box, Salesforce stores your data. The add-ons I build put it to work: on the website, in the portal and in the chat your team already uses.
Java background, Apex in practice. Apex, the language behind Salesforce's server side, is a close cousin of Java: the same class syntax, interfaces and strong typing. The Java I trained on in college carries straight over, and the front end runs on Lightning Web Components, standard JavaScript.
Lightning Web Runtime sites with custom LWC components over live CRM records. Prototyped fast, then locked into a design system.
Classes, triggers and REST endpoints that keep business rules inside the platform instead of scattered across scripts.
Website inquiry forms mapped field by field into Account Engagement, with server-side proxies so nothing leaks client-side.
New leads pushed into the right team chat the moment they're created.
Mention a bot, ask about your pipeline, get the answer with a table and a CSV or XLSX attached. Read-only by design.
I use AI every day: to draft, to search, to try an idea in minutes instead of hours. But a model doesn't own the outcome. I do. Every line that ships has been read, understood and tested by a person who knows why it's there.
The tools got faster. The responsibility didn't move.
Architecture, trade-offs and the final call stay human. AI handles the legwork around them.
Clear specs, constraints and context go in. Judgement decides what comes out and what gets thrown away.
Generated code gets the same scrutiny as a teammate's: read line by line, tested, and questioned when it looks too confident.
Fourteen years of building by hand is what lets me spot when an answer is fluent but wrong.
Credentials, client records and anything private never get pasted into a tool.
Web development, then software engineering, then DevOps. I didn't leave any of them behind.
Independent, remote
Architecture and delivery for clients in real estate, AI and services: platforms built from scratch, Salesforce portals, servers on Kinsta and AWS, APIs, and the security work that keeps everything standing.
Enterprise B2B platform
Owned a high-traffic WordPress platform end to end: custom modules, backend-rendered navigation, performance and edge hardening.
Production infrastructure
Containerized services on AWS ECS, Docker and Kubernetes, and built the CI/CD pipelines that made releases predictable.
ETL and data warehousing
Warehouses and pipelines with original and updated values kept side by side and a detailed JSON audit of every change.
Full-stack, PHP first
Where it began: PHP, MySQL and JavaScript, shipping sites for real businesses and learning what breaks in production.
Object-oriented foundations
Java was the main language of my coursework. The habits it taught, strong types, clear classes and interfaces, are the same ones I use in Apex and C++ today.
My first full game
A fantasy RPG of magic against steam technology. It's still my dream project, and I'm rebuilding it now in Unreal Engine 5.
Linux internals, graphics, cloud
GPU and graphics programming, Wayland compositors, QML and cloud certifications. Building ZenithArch Shell is the best course I've taken.
Client names are left out on purpose. Ask me about any of these and I'll walk you through the details.
A QML-native desktop environment for Hyprland on Arch and CachyOS, built on Quickshell. Panel, control center, theming engine, lock screen, notification daemon and installer, all written from scratch. I direct the look and write every module.
Visit zenithshell.devA homeowner portal on Lightning Web Runtime: LWC components over live CRM data, prototyped first and then handed to design as the source of truth.
A bot on a persistent WebSocket that answers Salesforce questions when mentioned, returning tables plus CSV and XLSX files. Runs Claude Code with a read-only connector.
A server-side proxy mapping a homebuilder's inquiry forms into Account Engagement, with a REST picklist feeding the property selector.
Bot-shield and REST-guard mu-plugins, WAF and rate-limit tuning, and log audits for a high-traffic enterprise site.
A wave-defense roguelite written in modern C++ on top of raylib. Where I keep my low-level skills sharp.
Gameplay systems and mechanics in Unreal Engine 5, and the groundwork for the Knights of the Legend revival.
Watch the Unreal Engine demo on YouTubeMy daily driver: CachyOS with Hyprland, custom animations, pywal color sync and a fish workflow, plus a leaner dwl setup. It grew into ZenithArch Shell.
Explore the Hyprland riceAutomated pipelines keeping original and updated values side by side with a JSON audit trail, plus BigQuery reporting on GCP.
Client work pays the bills. These are the bets I make with my own time.
Co-founder
A small independent studio building software, games and AI tooling. I lead engineering: architecture, infrastructure and the internal tools the team runs on.
What we build
Creator & maintainer
A QML desktop environment for Hyprland on Arch and CachyOS. 200+ modules, built in public.
zenithshell.devSolo developer
A wave-defense roguelite written in modern C++ on raylib.
Creator
My college thesis RPG, magic against steam technology, rebuilt from the ground up in Unreal Engine 5.
From the people on the other side of the work: clients, teammates and the leads I've reported to.
Two small games, written for this page in plain JavaScript. Best scores stay in your browser.
CindyCalico. Head of QA, mostly by sleeping on the keyboard.
Heads up: Stack Typer is built for a real keyboard. On a phone it still works, but autocorrect and thumbs will fight you. All good? Go for it, I won't stop you.
Tell me what you're trying to ship, the deadline and what's already in place. I take on a few engagements at a time: architecture reviews, platform builds, Salesforce extensions, DevOps clean-ups and game systems. You'll hear back from me directly.
Email me directly
paul.hansen.yuki@gmail.comInclude what you're building, your deadline and what's already in place. I read and reply to every message myself.
Cindy learns from your 👍 👎 and topic picks. Only anonymous keywords leave this page; your name, if you share it, stays on this device.