Executable architecture
Turn a technical direction into boundaries, modules, contracts, ADRs/RFCs and conventions the team can actually apply.
Founder of LRJI
Mohammed Hamdoune
Principal Software Architect · Senior Software Engineer
I work with teams that need to clarify architecture, accelerate delivery under constraints, or bring a critical system back to a maintainable level.
The LRJI profile is deliberately hybrid: architecture framing a CTO can use, Staff-level contribution in the codebase, and decision transfer so the team can keep moving after the engagement.
Positioning
An architect who stays close to the code
Architecture is valuable only when it changes concrete decisions: boundaries, tests, contracts, pipelines, runtime, ownership and the ability to ship. That is where the engagement sits.
Contribution
What Mohammed brings
Staff-level reinforcement
Work directly in TypeScript code, backend, frontend or platform layers when a decision must be proven through implementation.
Pragmatic modernization
Reduce debt, simplify disproportionate distributed systems and migrate progressively without blocking the product roadmap.
Field Work
Representative experience
Public references stay discreet, but they show the type of context where the profile is most useful: constrained systems, architecture to clarify and teams to realign.
Retail: 7 microservices to 1 backend
Reduced distributed complexity, one CI flow, 21 pods per environment brought down to 3 and simpler delivery.
Fleet management SaaSTypeScript bootstrap, tactical DDD, tRPC, PostgreSQL, GCP, tests and an operable product foundation.
Authentication platformKeycloak, Hexagonal Architecture, monorepo and clear separation between provider, use cases and infrastructure.
Method
Decision-oriented engagement
- 01
Read the real system
Codebase, incidents, delivery flow, product constraints, runtime and coordination costs.
- 02
Decide
Name the default decision, accepted risk, rejected alternatives and success criterion.
- 03
Prove it in code
Bring the decision into modules, tests, contracts, pipelines or runbooks.
- 04
Transfer
Make standards explicit so the team keeps autonomy after the engagement.
Domains
Where he is most useful
Architecture and delivery
- DDD
- Hexagonal Architecture
- ADRs/RFCs
- C4
- Technical debt
TypeScript engineering
- Node.js
- NestJS
- tRPC
- Vue
- React
- Vitest
Runtime and systems
- GCP
- Cloud Run
- Kubernetes
- Kafka
- RabbitMQ
- PostgreSQL
Go further