Skip to content

DENIS IZAIAS PEREIRA · SENIOR SOFTWARE ENGINEER

Full-stack JavaScript with deep frontend expertise.

For ten years I have built product interfaces. My specialty is frontend, working with React, Next.js and Vue. I also take ownership of Node.js, data, integrations, testing and deployment when the flow requires an end-to-end view.

While building my own product, DeNode, I turn real operations into software: self-service, delivery, an independent POS, local printing and fiscal integration with explicit responsibilities.

Curitiba, Brazil · working remotely

10 yearsFrontend development
React · VueInterfaces and design systems
Node.js · NestJSAPIs, data and integrations
DeNodeOwn product · architecture · deployment

01 / TECHNICAL CASE

DeNode: two independent products, connected by contracts.

A product and engineering case about data authority, operational continuity and recoverable integration, without a shared database or a mandatory dependency between Self-service and POS.
INDEPENDENT PRODUCT · EVOLVING

DeNode

Self-service owns channels and operations. The POS keeps checkout, sales, inventory and fiscal concerns within its own boundary. Each product works alone; when connected, they exchange versioned events and identities.

OPERATIONAL CONTEXT

Two independent products; one compatible operation.

Table ordering, QR Menu and Delivery serve different moments inside Self-service. The POS must remain useful at checkout even for clients that do not use those channels.
  • Catalog, combos, orders and channel origin remain in the Core.
  • Kitchen, waiters, couriers and scheduled orders evolve without Fiscal.
  • Checkout, tabs, inventory and fiscal state remain under POS authority.
SIMPLIFIED SYSTEM MAPDENODE / SYSTEM VIEW
PRODUCT 01 · AUTONOMOUS

DeNode Self-service

WORKS WITHOUT FISCAL
CHANNELS
Table orderingQR MenuDelivery
CATALOG AND OFFER

Products, categories, add-ons, combos, pizzas and per-channel availability.

OPERATIONS

Orders, tables, kitchen, stations, waiters, couriers and scheduled orders.

Own PostgreSQL · catalog · orders · operations
PRODUCT 02 · AUTONOMOUS

DeNode POS

WORKS ALONE AT CHECKOUT
NATIVE JOURNEYS
CheckoutTabsTables
SALES AND CONTROL

Local catalog, payments, inventory, cash register, optional kitchen and reports.

EXTERNAL EFFECTS

Decoupled FiscalProvider and PrintJob delivered to the local agent.

Own PostgreSQL · sales · cash · inventory · fiscal
OPTIONAL BRIDGE · OFF BY DEFAULTOrder + catalog Outboxes

versioned contract · HMAC · nonce

retry · idempotency · audit trail

Idempotent POS Inbox
IDENTITY ACROSS CATALOGS

The external projection never creates catalog entries, mappings or balances automatically.

  1. Product.idstable Core ID
  2. externalProductIdreceived reference
  3. versioned mappingexplicit and auditable link
  4. CatalogProduct.idlocal POS product
  5. inventoryPOS authority

Integration is optional and disabled by default. POS downtime does not stop orders, kitchen or delivery; pending events can be replayed with a complete audit trail.

ECOSYSTEM STACK

FrontendReact, Next.js, Vue, Nuxt and TypeScript
Backend and dataNode.js, Express, NestJS, PostgreSQL and Prisma
Real-time and paymentsSocket.IO, webhooks and Mercado Pago
Infrastructure and integrationsDocker, Dokploy, Evolution API / WhatsApp and local printing

02 / ENGINEERING DECISIONS

I start with the problem, ownership and real constraints.

Before choosing technology, I understand who uses the product, the path information follows, who owns each state and which dependencies must remain compatible. The solution evolves in stages, with stronger guarantees where risk requires them.
  1. 01

    Flows and dependencies

    I map who uses the product, the task path and the systems or people required to complete it.

  2. 02

    Ownership and authority

    I define what belongs to the interface, backend or a provider, and who validates rules and changes state.

  3. 03

    State and contracts

    I separate temporary interaction from persistent records and preserve layer contracts, including in prototypes.

  4. 04

    Compatibility and evolution

    I reuse what already works, isolate variations and deliver in stages without breaking the existing product.

  5. 05

    Validation and recovery

    I verify real dependencies, failure modes, state recovery and certification before considering a flow ready.

03 / EXPERIENCE

From critical interfaces to ownership of the whole product.

I have worked on products with security, scale, accessibility and integration requirements. In parallel, I build DeNode as my own product and own its architecture and operations.PDFDownload résuméPDF · 2 pages · full-stack version
GFT / Mastercard

Digital payments and authentication

Global payments project: Click to Pay integration between Mastercard and Cielo, Passkeys/WebAuthn, technical analysis, security and requirements certification.

Cast Group / Sebrae-SP

Public products and frontend leadership

Sebrae-SP Agenda with Vue, Nuxt and React: search, geolocation, filters and event journeys with UX, QA and backend teams.

Contabilizei

Financial products across two tenures

Account activation and recurring payments, responsive interfaces and automated tests across critical banking flows to protect against regressions.

DeNode

End-to-end product ownership

Architecture and evolution of Table ordering, QR Menu, Delivery and operations with Node.js APIs, PostgreSQL, real-time events and deployment.

View complete professional history
GFT Technologies / Mastercard

Senior Frontend Developer

Work on a global Mastercard project for digital payments and checkout experiences, including the Click to Pay integration between Mastercard and Cielo. Implementation and adaptation of Passkeys/WebAuthn features, API integrations, security requirements, technical analysis and certification.

Ana Gaming

Senior Frontend Developer

Built browser-based gamified promotional experiences for acquisition, engagement and retention within the Traffic squad. Structured components, state and API integrations as a reusable foundation for new campaigns using React, Next.js, TypeScript and Zustand. Worked with UX, backend and marketing, and contributed selectively to a Nuxt 4 and shadcn/ui backoffice.

Cast Group / Sebrae-SP

Senior Frontend Developer

Technical leadership in the evolution of digital solutions alongside UX, QA and backend teams. Built and maintained Vue, Nuxt, React, TypeScript, Vuetify and SCSS interfaces for navigation, search, geolocation, topic filters and both in-person and online event journeys.

Contabilizei

Frontend Developer

Developed banking features and payment flows, including account activation and recurring payments. Built responsive interfaces with Vue.js, SCSS and BEM, supported by component and critical-flow tests with Jest and Testing Library to strengthen regression protection.

Plataforma E-peça

Frontend Developer

Created scalable components, standardized the codebase and evolved the product-management backoffice. Worked with SSR, REST and GraphQL integrations, Vuex, Storybook and design-system practices.

Contabilizei

Frontend Developer

Developed interfaces for digital products with a focus on user experience, intuitive navigation and reusable components. Worked within a cross-functional squad with an emphasis on clean code and continuous maintenance.

Weevex

Junior Frontend Developer

Contributed from the beginning of the project that transformed locally installed logistics software into a web application.

TypeScriptReactNext.jsVue.jsNuxtNode.jsNestJSPostgreSQLPrismaSocket.IOMercado PagoEvolution APIDockerDokployJest
FRONTEND WORK

Product, interface architecture and quality.

React, Next.js, Vue, design systems, accessibility, testing, performance and API integration.

FULL-STACK WORK

Node.js, NestJS, data, integrations and deployment.

APIs, PostgreSQL, events, authentication, Docker and delivery with JavaScript and TypeScript.

04 / CONTACT

Open to frontend and full-stack opportunities.

I consider permanent roles, contractor engagements and project-based work. I want to contribute to teams that value product thinking, interface quality and technical decisions that hold up in production.