Senior engineering · End-to-end delivery
Interfaces, typed boundaries, asynchronous work, deployment, and recovery. Direct engineering involvement across the product and the systems that keep it running.
Engineering in practice
Illustrative code excerpts, simplified to show one decision at a time. Each makes an assumption, failure, or lifecycle easier to reason about.
Validate external responses before they enter the application. An unexpected shape becomes an identifiable integration failure.
async function loadUser(id: string) {
const response = await fetch(`/api/users/${id}`);
const data = await response.json();
return data.profile.name;
}const User = z.object({
id: z.string().uuid(),
profile: z.object({ name: z.string() })
});
async function loadUser(id: string) {
const response = await fetch(`/api/users/${id}`);
if (!response.ok) throw new Error("HTTP failure");
const user = User.parse(await response.json());
return user.profile.name;
}Represent expected failures in the return type so callers must decide how to handle them. Record useful context for diagnosis.
async function loadReport(id: string) {
try {
return await reports.get(id);
} catch {
return null;
}
}type ReportResult =
| { ok: true; report: Report }
| { ok: false; reason: "unavailable" };
async function loadReport(id: string): Promise<ReportResult> {
try {
return { ok: true, report: await reports.get(id) };
} catch (error) {
telemetry.capture(error, { reportId: id });
return { ok: false, reason: "unavailable" };
}
}Declare infrastructure in version control so changes can be reviewed and environments reproduced. This excerpt shows storage configuration, not a complete deployment.
Azure Portal
→ Create storage account manually
→ Choose settings from memory
→ Repeat for the next environmentresource "azurerm_storage_account" "results" {
name = var.storage_name
resource_group_name = var.resource_group_name
location = var.location
account_tier = "Standard"
account_replication_type = "LRS"
min_tls_version = "TLS1_2"
allow_nested_items_to_be_public = false
}Compute derived values and give subscriptions an explicit lifetime. Immutable updates avoid stale state and cleanup prevents duplicate listeners.
useEffect(() => {
socket.on("item", (item: Item) => {
items.push(item);
setItems([...items]);
});
}, [items]);useEffect(() => {
const receive = (item: Item) => {
setItems(current => [...current, item]);
};
socket.on("item", receive);
return () => { socket.off("item", receive); };
}, [socket]);
const total = items.reduce(
(sum, item) => sum + item.value, 0
);Selected work
Explore the constraints, architecture, and operating decisions behind four shipped products.
Recruitment · AI workflows
A multi-tenant product with typed APIs, asynchronous inference, explicit access boundaries, and an operating layer designed alongside the user journeys.
Geodata · Consumer product
A geospatial simulation core connected to address preflight, one-off payments, queue-based rendering, and private result delivery.
Mobile · AI voice coaching
Cross-platform voice coaching with long-form audio sessions, persistent conversation context, subscriptions, and ongoing store delivery.
Public data · Discovery platform
Fragmented government datasets shaped into school and municipality views with filtering, comparisons, analytics, and structured discovery.
Janus Jektvik · Founder
You work directly with Janus, a software consultant whose experience spans backend, frontend, mobile, cloud, and regulated environments.
I stay involved from product decisions through implementation and operation. The architecture should serve the work, and the work should stay understandable. Additional capacity comes in when the project calls for it.
Previous roles at Dawn Health and Netcompany span health software, enterprise systems, and banking. That experience informs how I approach product delivery today.
More about JanusA new product, an architecture decision, or a system that needs attention. Bring the context and we can talk through the constraints and the work ahead.
Change your perspective ↑