TEMOERI SJAMOJANI — DIRECTOR OF SOFTWARE DEVELOPMENT
Aligning people,product & engineeringin one direction.
I build high-performing engineering organizations and turn business ambition into secure, scalable SaaS — with .NET & Azure platforms, AI-driven software delivery and teams that own what they ship.
Every portfolio says "I'm technical". This one proves it — type a command, or click a chip. There may be hidden ones.
temoeri@edge — zsh LIVE
02 — The log
Nine years, one direction.
git log --career --oneline — from hands-on engineering to directing engineering organizations. Every stage still compiles.
a1f9e2c2023 → NOWHEAD → main
feat(tma)!: Director of Software Development
Leading TMA's software organization across multiple teams — engineering strategy, responsible AI adoption, architecture, quality and delivery. Building an engineering org that scales.
7c3d9142020 → 2023
feat(certigon): Head of Software Engineering & Team Lead
Promoted to lead the engineering team. Architecture standards, coaching, delivery and budgets — while staying hands-on with the hardest technical work.
2b8ff032019 → 2020
feat(certigon): Full-Stack Software Developer
C# / .NET, ASP.NET, nopCommerce, SQL Server, Vue.js — shipped on Azure with Azure DevOps.
e04a7d12017 → 2019
init(uwkm): Software Developer
Python/Django e-commerce and CMS platforms, Electron desktop apps, custom client integrations. Where the habit of shipping started.
c9d2e88MEANWHILE
docs(han): B.Sc. HBO-ICT — earned alongside a full-time dev role
Same story at Deltion College before it (MBO 4). Studying while shipping, twice — discipline is a feature, not a phase.
03 — Writing
Thinking out loud, in public.
Notes from the intersection of AI-driven delivery, architecture and leadership. New pieces land here first, then on LinkedIn.
AI-enabled engineering fails as a tool rollout and works as an org redesign: how roles, reviews, architecture and decisions change when AI writes the code.
On 2 August 2026 the EU AI Act's high-risk obligations became binding. Employment AI is explicitly listed. The deadline rewards the discipline you already owed.
OpenAI paused a model too good at cyberattacks while Google's architects left to automate discovery. The frontier's own people just changed the signal to read.
Four frontier models shipped in a month and a fifth is already rumored. The teams that win are not the ones who pick right — they're the ones who stop picking.
A build log: wire Kimi K3, Fable 5 and GPT-5.6 Sol behind one interface, run a ten-case golden set from your own work, and score cost-per-win, not Elo.
A 2.8T open-weight model topped the frontend arena and undercut Opus on price. The interesting number was never the Elo — it's what a director does next.
Evals are the unit tests of non-deterministic software. Why demos deceive, what a minimal suite looks like, and why defining 'correct' is a leadership job.
Every AI guardrail encodes a risk appetite someone chose — usually a framework default nobody agreed to. Why leaders should own that policy explicitly.
AI observability is a decision-rights problem, not a dashboards problem. The tracing is an afternoon of work; deciding who owns model quality is the job.
A build log: an LLM PR reviewer with schema-locked output, confidence gates, a human-escalation flag, and an eval suite that keeps the reviewer honest.
Engineering hiring looks resilient while new-grad hiring collapses. The junior role was the senior pipeline, and deleting it is a choice, not a market force.
AI coding agents amplify whatever architecture they meet. Well-factored systems get compounding speed; tangled ones get faster mess. Here's the mechanism.
Velocity without direction is waste. Why clarity — of intent, ownership and architecture — is the engineering leader's first job, and how to create it.