Portfolio / Work with me
Principal engineering / Selected engagements
Complex systems.Clear engineering decisions. I work with teams on software problems where architecture, domain complexity, modernisation or technical leadership matter.
Mohd. Paramasvara · Principal Full-Stack Engineer Based in Sabah, Malaysia. Remote-first project and contract work.
Explore the problems I work on ↓ 01 / Problems & evidence
Start with the system. 01 / System modernisation
Legacy software slowing delivery Untangle domain rules, improve integration boundaries and modernise the parts of a system that make change difficult.
Legacy insurance systems and campus platforms.
Inspect the related case study ↗ 02 / Complex product engineering
Business workflows that do not fit a simple app Model the rules behind permissions, contracts, policies and reporting, then build the interfaces and services around them.
Property, tenant and contract workflows across 20+ properties.
Inspect the related case study ↗ 03 / Architecture & delivery
Systems becoming hard to extend or operate Review data structures, APIs and delivery practices together to define a workable path from diagnosis to implementation.
Meeting systems with attendance, recordings and reporting integrations.
Inspect the related case study ↗ 04 / Applied AI integration
A knowledge workflow that needs more than an AI demo Explore RAG-based knowledge and onboarding tools around a defined workflow, with attention to data access and useful evaluation.
Résumé-listed RAG and knowledge-tool capabilities; discuss fit before defining a project.
View technical capabilities ↗ Inspect public engineering work ↗ 02 / Engagement fit
Agree the scope. Then own the work. Architecture review & technical diagnosis For teams facing unclear system boundaries, integration failures or difficult delivery decisions.
Useful inputs A specific problem, architecture context, relevant code or API contracts, and known operational constraints. Possible deliverables An agreed scope may include a findings document, prioritised risks and architectural options. Next step Bring the problem and the decisions you need to make to an introductory conversation. Related engineering work ↗ Modernisation & delivery For teams improving a legacy platform while existing business workflows still need to run.
Useful inputs The current codebase, business rules, consumer dependencies, test coverage and deployment constraints. Possible deliverables An agreed scope may include migration options, a phased implementation plan or hands-on delivery of a bounded change. Next step Start with the workflow or integration that makes change hardest. Related engineering work ↗ Project technical leadership For teams needing engineering direction alongside practical implementation of a complex product.
Useful inputs Product goals, current responsibilities, delivery risks and access to decision makers and technical context. Possible deliverables An agreed scope may include decision records, an implementation plan, delivery priorities or technical guidance alongside the team. Next step Discuss the decisions, responsibilities and involvement the project needs. Related engineering work ↗ Scope is agreed after an introductory conversation. These are examples of possible deliverables, not fixed packages. A useful starting point is a concrete problem, access to the relevant technical context, and someone who can make decisions. We can then agree scope, responsibilities and a project or contract arrangement.