06Frontend EngineerFeb 2026Remote · Lagos, Nigeria
BamBamLoad
Multi-application e-commerce SaaS
- Product
- B2B building-materials marketplace
- Apps
- Buyer, supplier, admin, public website
- My focus
- Supplier and admin workflows, shared table and modal patterns
- Team
- Small team, alongside a senior engineer
- Stack
- Next.js 16
- React 19
- TypeScript
- Turborepo
- Tailwind CSS 4
- TanStack Query
- TanStack Table
- zod
The product
BamBamLoad is a marketplace where contractors and builders buy sand and building materials directly from suppliers. Buyers browse, negotiate and check out; suppliers manage products, inventory, orders and their team; operations staff approve suppliers and oversee payments.
The frontend is a Turborepo monorepo of Next.js App Router apps (buyer, supplier, admin and the public website) on shared UI, utility and query packages.
My role
I worked as a frontend engineer in a small team, alongside a senior engineer. I built the interface workflows and shared patterns described here. Connecting several of these screens to the live API was done together with the team.
Product and supplier management
The supplier and admin apps are table-heavy, so most of this work went into one table that every list screen could share.
A shared data table with server pagination
Built on TanStack Table in the shared UI package. Passing a serverPagination prop turns the table into a display shell: it stops paginating in memory, works out the page count from the server total and only reports page changes to the caller. Without the prop it paginates client-side, so older screens kept working. The page list shortens with ellipses and shows fewer numbers on small screens.
Skeletons that match the real table
The loading skeleton mirrors the table's border, header, rows and optional toolbar and pagination, with cell widths that vary by row so it does not read as a grey block. It is used for first load, refetches and in-flight mutations.
Tooltips only when text is actually cut off
A column can opt in to truncation. The cell measures itself and shows a tooltip only when its text overflows, so short values never get a pointless tooltip.
Supplier product list
Search, status and page live in the URL, so a filtered list can be refreshed or shared. Search is debounced, any filter change returns to page one, and there is a single clear-filters action. Row actions (view, edit, archive, unarchive, delete) are shown or hidden by product status, and the table supports row selection.
Bulk upload
Suppliers can add many products at once through a spreadsheet dropzone that opens as a modal over the product list.
Archive and delete
Delete has two states. If the product cannot be deleted because orders reference it, the same modal changes to explain why and recommends archiving instead, so the supplier is never left at a dead end.
Supplier review for the admin team
Approve, reject and suspend dialogs with required reasons, a commission dialog, document review and tabbed supplier detail (KYC, overview, financials, audit), with phone numbers validated by libphonenumber.
Modal workflows on parallel and intercepting routes
Supplier actions such as add, edit, archive, accept order or change role open as modals, but each one is a real route.
Modals with URLs
Each section has a @modal parallel slot with intercepting routes. Clicking an action navigates to its URL; Next.js intercepts it and draws the modal over the list, which stays mounted underneath.
One RouteModal wrapper
A small wrapper owns open state and closing. It supports two close strategies, going back or replacing with a base URL, guards against double navigation, and shares its close handler through context so modal content does not need props drilled into it.
Same behaviour from a link or a pasted URL
Closing by replace gives the same result whether the modal was opened from the list or loaded directly. On a hard refresh the real route renders the same modal component, in most cases together with the list behind it.
No stale modals
Empty default and catch-all files in the slot make sure a modal's content is cleared when the user navigates back to the list.
Sign-in returns somewhere sensible
If a session expires while a modal is open, the login form strips the modal segment from the return path, so the user lands on the page rather than on a bare modal URL.
Reuse on detail pages
A second wrapper provides the same context from local state, so the archive, delete and order modals can also open over a product's detail page without changing the route.
Routes and schema conventions
A single ROUTES object
I introduced one typed route map for every app, with dynamic paths as functions, for example ACTIONS.EDIT(id). I then replaced hand-written template strings across the supplier app with it, which also fixed links that were missing a leading slash. It is now imported in well over a hundred files.
One way to name and place schemas
Form schemas live under lib/schemas by domain, are named in capitals with a _SCHEMA suffix, and their types are always inferred from the schema, never written by hand. I applied this across the admin, buyer and supplier apps in one pass and wrote the convention down for the team.
Multi-step forms on one schema
The add-product wizard uses a single schema. A typed map says which fields belong to each step, and the wizard validates only those fields before moving on.