About the firm
One architect, accountable end to end.
SoftArchium is deliberately small. You get the principal on the work — not a pitch from a senior name followed by delivery from a team you never met.
What the firm is
An independent practice built around distributed systems architecture, with three things attached to it that are genuinely the same discipline: fractional CTO advisory, product engineering on platforms like Meta, Shopify and Android, and corporate training for engineering teams.
They share a method. Find the real constraint — which is usually a boundary rather than a bottleneck. Design the change that removes it. Sequence the work so each step is independently valuable and independently reversible. Write the reasoning down so it outlives the engagement.
What it is not
Not a body shop, and not a firm that wins work on a senior architect and staffs it with juniors. The scale is the constraint that keeps that honest: there is one principal, so the number of concurrent engagements is small and stated up front.
There are no client logos on this site and no testimonials. Every engagement was under contract; none of them agreed to be marketing. What is published instead is the work itself, with the numbers as measured and the clients described rather than named.
Track record
Where the method came from.
- 2025 —
Principal Architect
Logistics platform engagement
End-to-end technical strategy and cloud architecture for a greenfield transport management system.
- 2021 —
Principal Engineer / Technical Consultant
SoftArchium
Independent practice: architecture, fractional CTO work, product engineering and training.
- 2020–21
Software Development Engineer III
Amazon (Alexa Devices)
Edge-to-cloud migration of a smart-home control plane; secured VP-level funding for a cross-org rollout.
- 2018–20
Senior Software Engineer / Consultant
Scan IT India
Monolith decomposed into twelve services; median response time 12s → 2s.
- 2007–18
Senior Software Engineer
Avaya
High-concurrency policy server at 5,000 req/s for US federal clients; telemetry that cut support workload 60%.
Employers are named as career history. Consulting clients are not — see the work for what those engagements produced.
How we work
Four things worth knowing before you engage.
Bring the mechanism, not the complaint
The most useful brief explains why something is broken, not just that it is. Half of any diagnosis is already in the client’s head — the job is getting it out and testing it.
Ideas are separable from the people holding them
A flaw found in a design is a debugging result, not an attack. Feedback is welcome in both directions, and the fastest path to a good architecture is usually an argument conducted properly.
Say it plainly
If an approach will not work, you will hear so directly and early, with the reasoning. That includes hearing that you do not need the engagement you were about to buy.
Leave something operable
The engagement is a success when the team runs the system without us — documented decisions, tested runbooks, and no single point of knowledge wearing a consultant’s badge.