Front-end · Back-end · Integrations · Implementations

Priyam Maniya
building the systems
companies run on.

Software engineer across front-end, back-end, integrations and implementations. I build internal platforms, ERP integrations and tools that replace manual work with something dependable.

Focus

Internal platforms & ERP integrations

Stack

React · Node · SQL · REST APIs

Shipped

4 systems in daily use

About NO. 01

I make manual work disappear into software.

A generalist engineer — as comfortable in the database and the API layer as in the interface on top of them.

Most of what I build is internal: the systems a team touches every day and stops thinking about because they simply work. I care about systems that hold up under real daily use more than about how they look in a demo — give me a process that lives in spreadsheets and email threads, and I will turn it into something with structure, history and a single source of truth.

4Systems shipped
3Layers, end to end
0Spreadsheets left behind
React Node.js SQL REST NetSuite
Software engineer
Priyam Maniya
What I take on
Internal platforms, integrations and ERP implementations, full-stack builds.
Selected work NO. 02

Four systems, quietly running.

Expand any project for the problem, the approach and what came of it.

01 Full-stack · internal Internal HR Platform A single, secure system of record for every employee lifecycle event. Full-stackRole-based accessInternal tools 2026
Problem

HR ran on scattered spreadsheets and email threads — no single source of truth, no audit trail, and onboarding steps that lived in someone’s head.

Approach

Built a full-stack internal application: authentication, role-based access, structured employee records and automated workflows for the repeating tasks.

Outcome

Now the HR team’s day-to-day system of record, replacing manual spreadsheet upkeep with one reliable tool.

02 Integrations · ERP NetSuite Integration & ERP Management Middleware connecting the ERP to the systems that actually run operations. IntegrationsNetSuiteERP 2026
Problem

Order, inventory and finance data sat in disconnected systems, so the same records were re-entered by hand and reconciled after the fact.

Approach

Built an integration layer over NetSuite’s REST/SuiteTalk APIs with retry handling, field mapping and reconciliation checks between systems.

Outcome

Manual re-entry across finance and operations is gone; ERP data stays consistent in near real time.

03 Full-stack · workflow Bid Tracker An internal tool that tracks every incoming bid from request to response. Full-stackWorkflowInternal tools 2026
Problem

Incoming bids were tracked ad hoc across inboxes and spreadsheets, so status and deadlines were easy to lose and nobody had the full picture.

Approach

Built a tracker with structured bid records, explicit status stages, owner assignment and deadline visibility for the whole team.

Outcome

One place to see every active bid and where it stands, at a glance.

04 Web · static Local Vendor Website A fast, clean site for a local vendor with no prior online presence. WebStatic sitePerformance 2026
Problem

The business could only be found by word of mouth or in person — no site, nothing searchable.

Approach

Designed and built a lightweight static site covering who they are, what they offer and how to reach them, tuned for fast loads on mobile.

Outcome

A permanent, searchable presence customers can actually find and contact.

What I take on NO. 03

Three kinds of work, end to end.

Scoped small enough to ship, owned deep enough to maintain.

S/01

Internal platforms

The system a team lives in all day: structured records, authentication, role-based access and workflows for the steps people currently repeat by hand.

AuthWorkflowsAudit trail
S/02

Integrations & ERP

Making two systems agree. Field mapping, retry handling and reconciliation over REST and SuiteTalk, so nobody re-keys the same record twice.

NetSuiteRESTReconciliation
S/03

Full-stack builds

Schema, service layer and interface from one pair of hands — including the small, fast public sites that just need to load and be found.

ReactNode.jsSQL
How I work NO. 04

Ship the smallest thing that removes the manual step.

Then harden it. Scope creep kills internal tools faster than bad code does.

Strength

Owning a surface end to end — schema, service layer and the interface — instead of handing off at the boundary.

Bias

Boring, legible, dependable. Clever code is a liability in a system someone else maintains.

Process

Sit with whoever does the work by hand, map the real path (not the documented one), cut what nobody needs, then build against the messy edge cases first.

Stack

React and Node across the interface and service layer, SQL underneath, REST and SuiteTalk out to NetSuite. Chosen because it is legible to whoever maintains it next.

Tools
ReactNode.jsSQLRESTNetSuite
Contact NO. 05

Have something worth building?

Internal tools, integrations, full-stack builds.

Direct priyam.maniya@outlook.com
Direct enquiries
Replies within two days