Vision and execution — the architect in the middle.
Arktaria wants an architect who lives in the balance between strategy and technology — the central sparring partner who turns ambiguous business goals into scalable system landscapes, then coaches the teams who build them. That is the seat Fauzul has held for a decade. He has dropped into demanding enterprise projects across Oslo, London, Zurich, Dubai and Quebec; owned solution architecture end-to-end (microservices, event-driven pipelines, API platforms, multi-tenant OIDC/RBAC); and — most relevant here — coordinated 's deployed engineering pod for a Norwegian fintech (Frontgo / Frontpayment), setting the team's engineering practices, advising the Vipps and core-financing integrations, and running a clean handover to the in-house team. He treats AI as a first-class architecture tool (a Claude-based natural-language CMS running in a client's production stack), builds compliance in by design (HIPAA, GDPR, OIDC/RBAC), and has already coached engineers who now lead teams in Norway. He's relocating to Oslo to help build Arktaria's architecture community from the ground up.
I own architecture end-to-end in demanding customer projects — turning ambiguous business goals into scalable, robust system landscapes (microservices, event-driven, API platforms, multi-tenant boundaries) and quality-assuring them to production.
AI-augmented delivery
Wise use of AI as a first-class architecture tool, not a bolted-on demo: a Claude-based natural-language CMS running in a client's production stack, plus event-driven agentic builds — exactly the balance of strategy and technology Arktaria is built around.
Mentoring & community
I coach architects and engineers and set engineering practices for deployed pods — having grown a team to 22 and coached alumni who now lead in Norway. Building Arktaria's architecture community from the ground up is the work I most want to own.
01 / Delivered in Norway
Already delivered in Norway
Strength lies in the balance between vision and execution — between strategy and technology. That balance is the seat I've held for a decade: the architect in the middle who turns ambiguity into systems and coaches the teams who build them.
In production
A deployed engineering pod for a Norwegian fintech — Frontgo / Frontpayment
Frontpayment needed to scale a core financing system and integrate Vipps — Norway's dominant payment network — to establish product-market fit, without immediately hiring in a high-cost market. deployed a dedicated pod (one lead backend, two fullstack). The client's own project manager owned the roadmap; I owned the engineering side — setting the pod's practices, advising the Vipps and financing integrations, leading hiring/HR, and keeping delivery aligned through weekly and monthly syncs under strict NDA. After roughly a year, we handed the whole codebase and infrastructure to Frontgo's incoming in-house team, cleanly.
Vipps + core-financing integration shipped to product-market fit, with engineering standards the in-house team could inherit.
Manager-to-manager delivery — requirement-gap unblocking and high-autonomy coordination across the Norway/Dhaka boundary.
Compliance and identity built in by design — the same OIDC/RBAC, HIPAA and GDPR discipline I bring to every engagement.
Two alumni now lead teams in Norway; I'm relocating to Oslo to do this work on-site, not from a distance.
01
Norway delivery — Frontgo · Vipps
Coordinated a deployed engineering pod for a Norwegian fintech: engineering practices, Vipps + financing integration, clean handover to the in-house team.
02
AI-augmented architecture — Claude-as-CMS
A natural-language CMS in a client's production stack: plain-English request → reviewed PR → automated edge deploy. Wise use of AI, designed in.
03
Compliance & identity — Anygum · EKAGRA
Federated OIDC + instance-level RBAC and a HIPAA-compliant EHR pipeline. Security, auditability and data governance from day one.
02 / Role fit
Point by point
The role is Principal Solutions Architect at an early-stage Nordic consultancy — holistic ownership of architecture in demanding customer projects, plus mentoring and community-building from the ground up. Here is how a decade of end-to-end enterprise delivery, real Norwegian client work, and AI-augmented architecture maps onto each point. Pick a topic to explore the evidence.
Strong fit
8+ years as a solutions, systems, or enterprise architect (or senior developer) with responsibility for holistic architecture.
Evidence
A decade co-founding and running , dropping into ambiguous enterprise environments across Oslo, London, Zurich, Dubai, Montreal and Florida — owning solution architecture end-to-end and leading delivery by example. The IC architecture arc (UX Engineer → Principal → Principal Staff SWE) ran 2017–2022 before the management and CIO chapters, so the holistic-architect responsibility is the through-line, not a recent add-on.
Strong fit
Solid experience with modern architecture principles: microservices, event-driven architecture, DDD, Event Sourcing, CQRS, and API design.
Evidence
Designs system landscapes around these patterns in production: microservices and event-driven pipelines (AWS SNS/SQS, n8n orchestration), API platforms (REST, ConnectRPC/gRPC), and DDD bounded contexts — splits a federated software marketplace into isolated per-org instances that (ERP) runs on. Comfortable applying CQRS / event-sourcing where read/write asymmetry or auditability demands it.
Strong fit
Translate business goals into scalable, robust, maintainable, cost-effective technical solutions, and quality-assure architecture and code.
Evidence
Validates the problem and success criteria before over-building, then frames the architecture around the outcome and quality-assures it to ship. Replaced manual deploys with GitHub Actions + AWS pipelines for a 4x faster time-to-market (75% reduction in cycle time), and runs cost-effective operations by default ('s off-peak spend eliminated via on-demand Cloud Run; single-digit-MB edge delivery for ). End-to-end ownership from empty canvas → CI/CD → production.
Strong fit
Cloud platform experience (Azure, AWS, or GCP).
Evidence
Deep, hands-on across AWS (Lambda, DynamoDB, SNS/SQS) and Google Cloud (Cloud Run), plus Cloudflare Workers at the edge — architecting and operating production workloads, not just deploying to them.
Adaptation
Primary depth is AWS and GCP rather than Azure. Many Norwegian enterprises are Microsoft-first, so I'd lean into Azure deliberately from day one — the cloud concepts (managed identity, event buses, container/serverless runtimes, IaC) port directly, and certifying / shipping on Azure is a weeks-not-months ramp on top of two production clouds I already run.
Adaptable
Container technology (Kubernetes, Docker).
Evidence
Strong with Docker and serverless container runtimes (Cloud Run, Lambda, Cloudflare Workers) — containerised services, build pipelines, and edge deployment are native.
Adaptation
Production depth is in Docker and managed/serverless containers rather than self-managed Kubernetes. The mental model — declarative deploys, health/readiness, autoscaling, secrets, observability — is already how I ship; standing up and operating K8s is an incremental ramp, fastest closed by running a real workload on it in the first weeks.
Strong fit
Strong understanding of DevOps, CI/CD, and modern development practices; effective cross-functional and agile delivery.
Evidence
GitHub Actions + AWS CI/CD pipelines, GitOps, Terraform/IaC, structured logging and observability — comfortable enough with infrastructure-as-code to have hosted a GitOps-with-Terraform webinar session. CSPO-certified; ran remote-first (+50% productivity, +100% satisfaction) and coordinated a cross-functional Norwegian client pod through weekly/monthly agile cadences.
Strong fit
Mentor architects and developers, contribute to competency development, and help build the architecture community.
Evidence
Grew 's team to 22 and coached engineers onward — two alumni now lead teams in Norway, one is in graduate study in Canada on my recommendation, and a UX designer I trained is taking his next career step in Germany. Set the engineering practices for the deployed Frontgo pod, and write/teach in public (design-engineer pattern papers, developer-productivity essays). Building an architecture community from the ground up is exactly the early-stage work I want.
Strong fit
Support customer meetings, bidding processes, and solution descriptions; understanding of AI in architecture, security, and data governance (desired).
Evidence
Client-facing by default — ran manager-to-manager syncs and requirement-gap unblocking for Frontgo, and pitched/scoped engagements as a co-founder. Treats AI as a first-class architecture tool (a Claude-based natural-language CMS in a client's production stack) and compliance as a product surface: federated OIDC + instance-level RBAC (), HIPAA EHR (), GDPR + EU VAT ().
Ask Fauzul's AI
03 / Signal
Strengths & honest gaps
Holistic architect across demanding client projects
A decade dropping into ambiguous enterprise environments and pulling robust, scalable architecture out of fuzzy briefs — Oslo, London, Zurich, Dubai, Montreal, Florida. Microservices, event-driven pipelines, API platforms, and multi-tenant OIDC/RBAC, owned end-to-end from empty canvas to production — held together by the testing, CI gates and observability that keep an architecture maintainable, not just shipped. The kind of central sparring-partner work Arktaria is built around.
A real Norwegian track record — already delivered here
Coordinated 's deployed engineering pod (1 backend, 2 fullstack) for a Norwegian fintech, Frontgo / Frontpayment: set the team's engineering practices, advised the Vipps and core-financing integrations, led hiring/HR, and ran a clean handover to the in-house team — alongside further NDA deliveries for Nordic clients. Two alumni now lead teams in Norway. I'm relocating to Oslo to do this work on-site, not from a distance.
AI as a first-class architecture tool
Arktaria puts wise use of AI at the centre of how it designs and builds — so do I. A Claude-based natural-language CMS runs in production for a 26-year-old export house (plain-English request → reviewed PR → automated deploy), plus event-driven agentic 0→1 builds (, ). AI used as designed-in architecture, not a bolted-on demo.
Mentor and community-builder for an early-stage firm
Grew a team to 22, built career pathways, and coached engineers into senior roles abroad — and set engineering standards for deployed client pods by raising the bar with people, not over them. Arktaria is building expertise, culture and quality from the ground up; that is the part of the work I most want to help shape.
Closing the gaps
Norwegian language (English is fully fluent; the role wants Norwegian + English).
Ongoing from day one
I won't pretend to speak Norwegian yet — but I've delivered for Norwegian clients in English for years, and I have a public, multi-year discipline of learning a language daily (a 900+ day French streak). I'll commit to Norwegian with that same persistence so I can carry customer and team conversations in it, and I can be fully effective in English from the first week while I close it.
Azure and self-managed Kubernetes depth (primary clouds are AWS/GCP; containers are Docker + serverless).
4–8 weeks
Norwegian enterprises skew Microsoft-first, so I'd deliberately ramp Azure and stand up real Kubernetes workloads early. The architecture concepts port directly from two production clouds and years of Docker/IaC; the fastest close is shipping a real customer workload on Azure + K8s in the first weeks, not a course.
Ask Fauzul's AI
04 / Candid answers
Our opinions, answered
Candid answers — why a co-founder wants the architect seat, the honest read on Norwegian and on Azure/Kubernetes depth, how the AI work is Claude-led but model-agnostic, and how I'd adapt into Nordic working culture. Ask the agent anything else.
You co-founded and run ELO as CIO — why step into a Principal Solutions Architect seat at Arktaria?
F
Fauzul Kabir Chowdhurycandid read · 1 min
Because architecture in the room with a customer is the work I love most, stripped of the agency overhead. As CIO my role drifted into running a client-services business; the part that lights me up is being the central sparring partner — turning an ambiguous business goal into a scalable system landscape and coaching the team that builds it. Arktaria lets me do exactly that, and the early-stage, build-the-culture-from-scratch mandate is a feature, not a risk, for me: I've grown a 22-person engineering org and an architecture practice before, and I'd rather help shape Arktaria's from the ground up than maintain someone else's.
The role wants strong Norwegian and English. You don't speak Norwegian — how will you be effective with Norwegian customers and teams?
F
Fauzul Kabir Chowdhurycandid read · 1 min
I'm honest that I don't speak Norwegian yet. Two things make me confident anyway. First, I've already delivered for Norwegian clients — I coordinated 's deployed pod for Frontgo / Frontpayment, running manager-to-manager syncs in English through to a clean handover, and two of my alumni now lead teams in Norway. English is the working language of most Nordic engineering rooms, so I'm fully effective from week one. Second, I have a public, multi-year habit of learning a language every single day — a 900+ day French streak — so 'I'll learn Norwegian' isn't a promise, it's a pattern I can prove. I'll commit to it with that same persistence so I can carry customer and team conversations in Norwegian, not just survive them.
Your shipped AI work is Claude-led. Is that a problem, and are you actually current on the architecture patterns the JD lists?
F
Fauzul Kabir Chowdhurycandid read · 1 min
My production AI has been Claude-led because that's what I reached for — but the skill is model-agnostic: prompt design, agent orchestration (A2A, MCP, n8n), RAG and eval rigor transfer across providers, and I'd use whatever the customer's stack and data-governance posture demands. On the architecture patterns, they're not theory for me: microservices and event-driven pipelines (SNS/SQS, n8n) in production, API platforms (REST, ConnectRPC), and DDD bounded contexts at that isolate per-org instances. I'm candid that Event Sourcing / CQRS show up where read/write asymmetry or auditability justify them rather than everywhere — I architect to the problem, not to the buzzword.
Norwegian enterprises are heavily Microsoft/Azure. Your depth is AWS and GCP. Does that hurt you?
F
Fauzul Kabir Chowdhurycandid read · 1 min
It's the most honest gap, and I won't wave it away. My production depth is AWS and GCP (plus Cloudflare at the edge), not Azure. But cloud architecture is mostly portable — managed identity, event buses, container and serverless runtimes, IaC, observability — and running two clouds in anger means the third is a ramp, not a restart. Given the Norwegian market, I'd lean into Azure deliberately from day one and close it the fastest way I know: by shipping a real customer workload on it in the first weeks, rather than collecting certificates in the abstract.
This is an early-stage company building culture from the ground up. How do you adapt into Nordic working culture specifically?
F
Fauzul Kabir Chowdhurycandid read · 1 min
I've spent years delivering into Norwegian and Nordic engineering rooms, so the working norms aren't foreign to me — flat hierarchy, trust and autonomy over command-and-control, decisions by genuine buy-in rather than authority, and a real respect for work-life balance and for the people who deliver. That actually matches how I already lead: I moved to remote-first on trust, coached people into ownership, and handed mission-critical operations over with autonomy. Building Arktaria's architecture community means setting standards people want to follow, not enforcing them — and doing it as a teammate who's there to learn the culture, not impose one.
The start date is September 1, 2026 in Oslo. Are you set up to relocate and be on-site?
F
Fauzul Kabir Chowdhurycandid read · 1 min
Yes — Oslo on-site is the point, not a cost I tolerate. I'm intentional about basing this chapter in Oslo, I've delivered for Norwegian clients before, and I relocate as soon as the work-permit process allows; I can start remote-first on local hours immediately if useful while that completes. There are also real roots pulling me toward the region — my best friend lives in Oslo, and my sister is in the UK, someone I'd love to be closer to — so this is somewhere I want to settle, not just a posting. Being in the room with customers and the team is exactly the part of this role I want.
Ask Fauzul's AI
05 / Track record
The stack & the builds
The stack and the builds that prove it — a deployed pod in Norway with Vipps, AI-augmented delivery, federated identity, and HIPAA-grade compliance. Explore any topic below.
Coordinated ELO's dedicated engineering pod for Frontgo (Frontpayment's engineering arm) in Norway. The project itself was owned and driven by the client's dedicated project manager; Fauzul's role was to keep the three-engineer pod aligned — setting engineering practices, advising on the Vipps and financing integrations, unblocking communication and requirement gaps, leading hiring/HR, and running the weekly and monthly syncs — through to a clean handover to the in-house team.
Anygum is a working marketplace-style platform where anyone can host their own API and builders can compose bespoke apps that pull services from multiple vendors. Identity runs through Cloudsight — custom auth on Auth0 — so provider and consumer context share single sign-on, RBAC and org controls, multi-instance of the same app for different teams, easy telemetry, and a single payment funnel for consumption. Ideation started as an internal auth problem for SaaS distribution; it was spun out as Anygum. Elobooks.net uses it. Distribution limited wider market reach; the product itself works.
Strategic health-tech partnership and equity investment in Bangladesh's most advanced clinical practice for wound care, diabetes, and nephrology. Spearheaded high-utility, HIPAA-compliant EHR clinical dashboards and scaled digital patient advocacy.
Editorial export site for Global Jute Trading Ltd — a Dhaka-based sourcing & exporting house with 26 years as a company and 35 years of jute trading under its principals. Built to support their push into deeper international markets, with a particular focus on Canada.
Agentic news scraper & editorial audio briefing network. Scrapes tech and business news via Firecrawl, curates & scripts dual-host dialogues with Kimi via OpenRouter, and renders high-fidelity multilingual voices via Gemini TTS on Azure.
Ask Fauzul's AI
Bli med på laget.
Relocating to Oslo, Norway — ready to be the architect in the room, on-site from day one. Fully effective in English now; committed to Norwegian with the persistence behind a multi-year French streak.
