SOFTWARE ENGINEER / SYSTEMS ARCHITECTPORTFOLIO — 2026

THE ART OF THINKING IN SYSTEMS

I engineer
what matters.

Complexity is inevitable. Chaos is optional. I turn difficult problems into systems that are understandable, resilient, and built to last.

THE PERSON BEHIND THE ALIASDan Radu Dragomir/NorAmarth

NOT MORE CODE.
BETTER REASONS TO WRITE IT.
BASED IN ROMANIA
WORKING BEYOND BORDERS

Engineer by trade.
Questioner by nature.

ONE PERSON. TWO SIGNATURES.Dan Radu Dragomiralso known as NorAmarth

I'm Radu to most people and NorAmarth online. The latter is a long-standing alias, not a different identity. I'm a software architect, engineer, and independent researcher based in Romania.

I work at the intersection of architecture, technical leadership, and the wonderfully stubborn question: why are we doing it this way? My work spans mature platforms, complex backend ecosystems, original research, and early-stage ideas. I care about the seams between components, the trade-offs behind decisions, and what happens when a system meets reality.

The ideas behind the work
I.ArchitectureBoundaries, trade-offs, resilience
II.EngineeringBackend systems, practical delivery
III.LeadershipClarity, ownership, mentoring
IV.ExplorationR&D, AI, better questions

BUILT FROM FIRST PRINCIPLES

Ideas with
some gravity.

These initiatives are in different stages of exploration and development. They're not trophies on a shelf. They're questions worth pursuing.

01 / R&D SYSTEMSIN DEVELOPMENT

Entyra↗

Rethinking project management for research and development. A place for uncertainty, exploration, evidence, and decisions, not just another board full of tickets.

R&DSYSTEM DESIGNPRODUCT THINKING
02 / HUMAN SYSTEMSIN DEVELOPMENT

AdSerta↗

A more transparent approach to recruiting. Matching people to actual needs, treating candidates as humans, and making decisions more explainable.

HR TECHNOLOGYMATCHINGEXPLAINABILITY
03 / BETTER EVALUATIONIN DEVELOPMENT

C.E.M.S.↗

Structured, assisted hiring conversations. Moving interviews away from improvisation and toward thoughtful, consistent, evidence-aware evaluation.

INTERVIEWSDECISION SUPPORTWORKFLOWS

Selected initiatives are described at a conceptual level. Implementation details and proprietary materials remain private.

WHEN THE PROCESS ITSELF NEEDS RETHINKING

Make space for
the unknown.

Some of the hardest engineering problems are not technical problems at all. They are problems of how we explore, learn, converge, and decide.

ORIGINAL FRAMEWORK / WORK IN DEVELOPMENT2026

P.I.N.E.S.

Partial Implementation with Necessary Entropy for Synthesis

A framework for high-uncertainty, cognitively demanding work: protect what must stay true, give exploration room to discover what isn't known, and let implementation and synthesis inform each other.

01
Stable invariantsKeep the real objectives and non-negotiable constraints visible.
02
Bounded entropyAllow uncertainty where it is useful, without surrendering control.
03
Explicit transitionsMake convergence, evidence, and decision boundaries deliberate.

Theoretical and operational research by Dan Radu Dragomir. Presented here as an evolving framework, not an established industry standard.

AN INDEPENDENT RESEARCH ESSAYJANUARY / 2026

INTELLIGENCE / ARSUS / LEARNING AFFINITIES

O analiză conceptuală a evoluției intelectuale umane

Inteligență, Arsus, Afinități și Învățare

A conceptual exploration of intellectual evolution, distinguishing information from intelligence, learning, and the act of applying intelligence. Introduces arsus as a decision-making concept and considers the role of learning affinities.

AUTHORDan Radu DragomirLANGUAGERomanian
View the essay on OSF

Conceptual / exploratory manuscript. Not presented as empirical validation or peer-reviewed findings.

THE THOUGHTS BEHIND THE CODE

Published ideas.
Open questions.

Engineering, hiring, AI, education, and the human consequences of systems designed without asking what they are optimizing for.

FEATURED ESSAY / AUG 2026

Before We Leave
the Room.

On the accelerating power of AI, the temptation to measure the wrong things, and why responsibility has to grow alongside capability.

Find this essay on my LinkedIn profile

NO MAGIC. JUST CLEAR THINKING.

Good architecture
starts with better questions.

01 /

Understand before building.

A precise problem statement is worth more than a fast implementation of the wrong thing.

02 /

Design for failure, not fantasy.

Feedback loops, recovery paths, observability, and honest constraints are not optional extras.

03 /

Make complexity earn its keep.

The simplest architecture that meets the real requirements usually wins. Dogma is not a design pattern.

04 /

Leave systems understandable.

Build so the next engineer can question, extend, and improve the work without needing an archaeologist.

Under the
hood.

Deepest experience in PHP and backend architecture, with a broader engineering toolkit shaped by the problem rather than fashionable acronyms.

COREPHP 8+ / Symfony / Laravel
ALSO WORKING WITHJava / Python / Go
PLATFORMS & SYSTEMSLinux / SQL & NoSQL / APIs / Distributed systems
EXPLORINGLocal LLMs / Agentic workflows / R&D tooling

OPEN TO INTERESTING PROBLEMS

Have a hard
problem?

I like complex systems, candid conversations, and problems that don't come with a ready-made answer. If that sounds familiar, let's connect.

Find me on GitHub Or connect with me on LinkedIn ↗

GET IN TOUCH THROUGH GITHUB OR LINKEDIN.
NO LEAD FORMS. NO TRACKING PIXELS. NO NONSENSE.