asunción · py open to LATAM + US ● available · 2026

Mauricio Martinez.

I ship multi-tenant SaaS for regulated industries. Founder of Nodica. Contributor to NPSP.

Selected work → contact [at] mauricio-martinez.com ↗
01 / About

A senior engineer who also runs the company.

I'm Mauricio. I founded Nodica, a consultancy registered in Paraguay and Delaware. I lead the engineering on every project.

Last few years: SIFEN-compliant invoicing in Paraguay. An offline-first PWA replacing EcoMatcher across 15,000 hectares. Cross-border payments between Brazil and Paraguay. Six departments of an architecture firm on a single platform.

When you work with me, you get both: the engineer writing the code and the founder accountable for the outcome. No translation layer between what's promised and what gets built.

based Asunción, Paraguay
role Senior Engineer · Founder
company Nodica · PY + DE LLC
open to LATAM + US · remote
availability 2026
languages en · es
products
Demit SIFEN invoicing · production
Agendica scheduling · production
Reachport outbound CRM · internal use · meta partner approval pending
02 / Experience · ~/experience

Eight years of work, queryable from a prompt.

Type, click a chip, or just read. The data is the same. tab autocompletes · ↑/↓ recalls history · ctrl+L clears

~/experience · zsh
interactive
mauricio@portfolio:~/experience $

Work experience

  1. Nodica — Founder & Lead Engineer

    Mar 2025 — Present · 1y 2m · Remote · LATAM & US clients

    Stack: TypeScript, NestJS, Next.js, PostgreSQL, Prisma, Clerk, BullMQ, AWS.

    • Founded and operate a software consultancy registered in Paraguay and Delaware (Stripe Atlas).
    • Translate client requirements into proposals, architecture diagrams, and delivered systems.
    • Run legal, commercial, and technical sides of the firm end-to-end.
    • Author custom Claude Code subagents over domain-specific manuals (SIFEN v150) — compliance research from hours to minutes.

    Impact:

    • Replaced EcoMatcher across a carbon-credit operation tracking 93 parcels across 15,000 hectares.
    • Demit (SIFEN-compliant invoicing) in production with paying tenants — near-zero rejection rate on first submission.
    • Architecture firm digital transformation adopted across all 6 departments, 50 internal users.

  2. VeXtar — Tech Lead

    Aug 2024 — Feb 2025 · 6m · Remote · Brazil + Paraguay

    Stack: NestJS, Next.js, React Native, PostgreSQL, AWS EC2, AWS RDS, Redis.

    • Led a team of 4 engineers building a cross-border payments platform across Brazil and Paraguay.
    • Designed queue-based workers decoupling payment-gateway callbacks from notifications and retries.
    • Idempotency keys at every boundary — gateway callbacks can arrive out-of-order, duplicate, or never at all.
    • Owned the state machine across gateways with asymmetric callback semantics.

    Impact:

    • Stable cross-border flow in production across multiple rails.
    • Reconciliation discrepancies tracked and resolved per-gateway instead of swallowed.
    • Mobile and web clients reflect state changes in seconds despite async gateway callbacks.

  3. Oktana — Software Engineer

    Dec 2020 — Aug 2024 · 3y 8m · Remote · US-hours collaboration

    Stack: React, Next.js, TypeScript, Node.js, Salesforce, Apex, PostgreSQL.

    • Built scalable React and Next.js frontends with SSR optimization, consuming REST APIs for Salesforce-integrated enterprise apps.
    • Worked with PostgreSQL designing schemas and queries for reporting and data-sync workflows alongside Salesforce.
    • Contributed to the Nonprofit Success Pack (NPSP), the open-source Salesforce package used by 40,000+ nonprofit organizations globally.
    • Managed GitLab CI/CD pipelines with Jest test suites.
    • Full Agile cycle on remote cross-functional teams with US-hours collaboration.

    Impact:

    • Merged PRs in SalesforceFoundation/NPSP — verifiable on the open source section of this site.
    • 3 years, 9 months on the same team — sustained delivery across multiple enterprise products.

  4. Softshop — Full-stack Engineer

    May 2019 — Nov 2020 · 1y 6m · Asunción, Paraguay

    Stack: Node.js, Express, React, PostgreSQL, MongoDB, Docker.

    • Built and maintained internal SaaS products across multiple verticals.
    • End-to-end ownership: schema design, API surface, frontend, deployment.
    • Introduced Docker-based local environments to standardize team setup.
    • Mentored two junior engineers through their first production deploys.

    Impact:

    • Reduced onboarding time for new engineers from days to under an hour.
    • Shipped three internal tools that replaced spreadsheet workflows for the operations team.

  5. Hendyla — Software Developer

    Sep 2017 — Apr 2019 · 1y 7m · Asunción, Paraguay

    Stack: PHP, Laravel, MySQL, jQuery, Bootstrap.

    • First role out of university. Built and maintained business management software for SMBs across Paraguay.
    • Customer-facing implementation work alongside engineering — taught me to translate business problems into schemas before writing code.
    • Wrote SQL by hand long before the ORM era. Still write SQL by hand when it matters.

    Impact:

    • Foundational years. Where I learned that the schema is the product.
    • Direct customer contact taught me to ask better questions before proposing solutions.
03 / Selected work

Four systems shipped. All still in production.

Most of this is confidential. Each card leads with the decision; tap for the diagram and full notes.

case · 01
93 parcels · 15,000 hectares
company Nodica role   lead engineer year   2025 – 2026 status in production
offline (field) online (server) capture replay on reconnect allocate Tablet · PWA IndexedDB queue Background job Allocation
illustrative · simplified for confidentiality
Problem
Surveyors covered 93 parcels across 15,000 hectares, often spending full days in zones with no usable mobile signal. The client needed every visit captured in the field to be recoverable later regardless of how long the device had been off the network, since a single lost visit cost a return trip and an awkward chain-of-custody gap that auditors took seriously.
Constraints
Full-day offline on mid-range Android tablets, with hard idempotency so the same parcel-visit resubmitted from a different device never duplicates. Audit-grade traceability of every edit, and no migration window since the existing operation kept running while the replacement rolled out.
Decision
PWA with an IndexedDB write queue keyed by (parcel × visit × surveyor), so resyncs are content-addressed and naturally idempotent; a service worker replays the queue on reconnect. Server side, an asynchronous background job ingests synced batches and allocates each scan to its parcel, visit, and surveyor.
Outcome
Replaced EcoMatcher across the operation in the first rollout window. Cycle time dropped about 40% with zero confirmed data loss in 12 months of production use.
stack
Next.jsTypeScriptIndexedDB
case · 02
50 users · 6 departments · one platform
company Nodica role   lead engineer year   2025 – 2026 status in production
design_ready schedule_approved budget_request progress_milestone Design P&C Construction A&F
illustrative · simplified for confidentiality
Problem
Six departments coordinated architectural projects across email threads, shared spreadsheets, and tribal knowledge, so the firm needed a single source of truth where any department could see the live state of a project without pinging four people across four systems. They also needed cross-departmental hand-offs treated as first-class objects so coordination overhead wouldn't keep scaling with headcount.
Constraints
Each department spoke its own vocabulary: a 'milestone' in design meant something different in accounting. No firm-wide freeze was possible since every department had live engagements running, and technical comfort spanned long-time spreadsheet users through ops folks ready to wire up their own workflows.
Decision
FastAPI + React with PostgreSQL as the source of truth. The call that mattered was modeling cross-departmental hand-offs as first-class event objects, with a workflow graph (visual, editable by ops) defining which events trigger which downstream tasks. Each department keeps its internal language; ops adds new project types in the graph without code changes.
Outcome
Adopted across all 6 departments without a flag day. Cross-departmental visibility now lives in a single dashboard the team can drive on its own, and ops onboards new project types in the graph editor with no engineering ticket.
stack
FastAPIReactPostgreSQLAWS EC2Python
case · 03
Regulated · multi-tenant
company Nodica role   founder · lead engineer year   2025 – 2026 status in production
Clerk JWT API Key signed XML poll batch result Operators ERP / Odoo Demit SIFEN
illustrative · simplified for confidentiality
Problem
Every electronic invoice in Paraguay must validate against SIFEN's v150 XML schema, carry a signed fiscal code (CDC), and round-trip through a sync or async acknowledgement flow before it counts as issued. Tenants don't want to know any of that; they want to send an invoice and have it stick.
Constraints
Compliance is non-negotiable since a rejected invoice can block real-world business. The async batch flow is protocol-tracked and polled, so every issuance path has to be idempotent at the boundary. Tenant isolation has to hold cleanly across data, certificates, and counters, and the same API has to serve both human operators and ERP integrations without forking.
Decision
NestJS + Prisma + PostgreSQL with a dual-auth boundary (Clerk JWT for the operators app, scoped API keys for ERP modules) behind a single guard. SIFEN exchange runs through an internal SOAP layer that signs, validates against the official XSDs offline, submits, and reconciles batches via a Prisma-backed state machine polled on a schedule. To keep the v150 spec tractable, I authored three Claude Code subagents scoped to the Manual + XSDs, turning compliance research from hours into minutes per edge case.
Outcome
In production with paying tenants and near-zero rejection on first submission. The subagent-over-manual pattern is now standard practice in the firm for any compliance-heavy spec we onboard.
stack
NestJSPrismaPostgreSQLNext.jsClerkBullMQRedis
case · 04
40,000+ nonprofits · open source
company Oktana role   contributor year   2022 status open source
fig · see live PR list in the open source section
illustrative · simplified for confidentiality
Problem
NPSP powers donor and program management at 40,000+ nonprofits, so contributing meant working inside Salesforce.org's review process, which is rightfully strict for code that ships to that much live production usage. The areas the contributions targeted were recurring-donation handling and the rollup engine that summarizes child-record amounts onto parent objects, where edge cases compound quickly.
Constraints
Apex with platform-enforced test coverage, and the Salesforce metadata API for any declarative change. Reviews handled by Salesforce.org engineers familiar with edge cases the contributor had to learn cold, and every test ran in a fresh Developer Edition org reproducing the reported issue from a clean state.
Decision
Kept every contribution narrow: one recurring-donation or rollup edge case per PR with a focused regression test, no bundled cleanup. Reproduced reported issues in a clean Developer Edition org first so review conversations focused on the fix, and followed the package's existing naming and structure conventions instead of imposing new style.
Outcome
Merged PRs in SalesforceFoundation/NPSP, pulled live in the open source section below. Code now runs alongside the rest of the package at the 40,000+ nonprofits relying on it; the contributions are small in line-count intentionally, the value was landing them at all within that review bar.
04 / Open source

Contributions to NPSP.
Salesforce's open source package for nonprofits.

New features and components for the donations module, the part that handles how those organizations record and manage giving. Merged upstream through reviewed PRs.

SalesforceFoundation / NPSP · merged PRs · 3d old
#6970
jun 2022
Recurring Donations Mobile
SalesforceFoundation/NPSP
+665 −145 ↗
#6961
jun 2022
Recurring Donation Actions Design
SalesforceFoundation/NPSP
+348 −3 ↗
#6982
jun 2022
Cancel recurring donation
SalesforceFoundation/NPSP
+134 −41 ↗
#7018
jul 2022
Frequency for every 1st and 15th case
SalesforceFoundation/NPSP
+173 −163 ↗
#6921
apr 2022
Multi-Currency support
SalesforceFoundation/NPSP
+84 −72 ↗
#6897
mar 2022
Giving Summary component redesign
SalesforceFoundation/NPSP
+65 −33 ↗
Used by 40,000+ nonprofits globally. see my full pr history here
contribution calendar · public commits · custom palette
72 contributions · 2022 17 merged PRs in public repos 4 peak day
github snapshot 3d old
05 / Infrastructure

How this site is built.

Hover any node: why I chose it, and where it matters, what I deliberately didn't.

mauricio-martinez.com infrastructure: Route 53, CloudFront, S3, and GitHub Actions, plus rejected alternatives (contact form, PaaS, WAF). AWS · us-east-1 considered · rejected deploy · sync · invalidate alias /* static GitHub Actions build · deploy Route 53 DNS + ACM CloudFront CDN S3 static origin Contact form Lambda + SES Vercel / Netlify managed PaaS AWS WAF managed ruleset
Static by default
The whole site is HTML on S3 behind CloudFront. No backend, no servers, nothing to operate at runtime. Cents per month at this traffic.
Reject, on purpose
The clearest signal here is what I left out: no Lambda, no WAF, no PaaS. Each one would add surface or cost for nothing this site needs.
One trust boundary
Everything lives in one AWS account, defined in Terraform end to end: Route 53, ACM, CloudFront, S3. One environment: prod.
Contact without a backend
A plain mailto link, not a form. Nothing to spam, nothing to deliver, nothing to break.
iac: terraform · s3 state + lockfile · single env (prod)
ci: gha · oidc · build · s3 sync · cf invalidate
runtime: none · static html behind cloudfront
cost: cents/month
06 / Technical stack

Six categories. No logo grid.

What I actually reach for, by category.

01

Languages & Frameworks

TypeScriptNode.jsNestJSNext.jsReactAstroReact NativePythonFastAPI
02

Databases & ORMs

PostgreSQLPrismaMongoDB
03

AI-first Tooling

Claude Codecustom subagentsCLAUDE.mdCursorCopilot
04

Auth & Multi-tenant

ClerkTenant IsolationNextAuthRBAC
05

Background & APIs

BullMQRedisRESTGraphQL
06

Cloud & DevOps

AWS LambdaS3CloudFrontTerraformGitHub ActionsEC2RDSDynamoDBSSMSESHetznerDockerGitLab CI/CD
07 / Contact

Let's talk about
the system you're
about to build.

Consulting via Nodica, or senior eng / EM roles. I reply within a business day.

email   contact [at] mauricio-martinez.com ↗ linkedin   /in/mauricio-martinez-dev ↗ calendar   agendica.app/mauriciomartinez ↗ company   nodica.io ↗ colophon   /humans.txt ↗
live · region us-east-1 · served s3 + cloudfront · commit 919b2c6