Dave Nebot
LinkedIn (opens in a new tab)GitHub (opens in a new tab)Email Dave

Currently at Shure

I replace publishing systems while people are still using them.

I’m Dave Nebot, a senior software engineer in Illinois. I own the platform Shure’s technical documentation is authored in and published through — the CMS its writers open every morning, the print production suite, the PDF generation, and the public site at shure.com/docs. The job is to keep all of that boring, especially while it is being replaced.

  • Built the component CMS Shure’s technical writers author in, and the publishing side that turns their work into guides, print masters and downloadable PDFs.
  • Led two platform migrations: roughly 1,000 print publications into Acquia DAM, and the in-house CCMS into Heretto. Neither needed a publishing freeze or a rollback.
  • Built the previewer and admin panel behind ~350 publications, so a writer publishes per language without waiting on an engineer.
Get in touchRead the case studiesRésumé (PDF)

Central Illinois (US) · Remote only

The whole platform
The component CMS, print production, PDF generation, shure.com/docs — the authoring tool through to the customer download
Two migrations, led
The asset archive into Acquia DAM, the CCMS into Heretto. No publishing freeze, no rollback
Adoption, not just cutover
Standards, training and the rollout — the half of a migration that is people, not code
Dave Nebot

Senior Software Engineer · Full-Stack

  • Full-stack
  • Content platforms
  • Publishing pipelines
  • DAM / CCMS
  • Migrations & rollout
  • Next.js
  • React
  • TypeScript
  • Node.js
  • PHP
  • CI/CD
  • Heretto
  • DITA
  • Acquia DAM
  • Workflow automation
  • Metadata
  • Content ops
  • Performance

Impact

The systems I own, one by one

Named individually and sized, because “led two enterprise migrations” is the same sentence whether it moved four hundred assets or four million.

Shure — what I built

2018 – present

The systems Shure’s technical documentation is written in, built by, and published through.

  • The component CMS

    The tool the whole documentation team opens every morning

    Built the component CMS the technical writing team authors in — editor, administration surface, and the publishing side that turns their work into guides, print masters and downloadable PDFs.

  • Publication previewer and admin

    ~350 publications across the product line

    Where a writer previews a guide and then publishes or unpublishes it per language — the step that used to come to an engineer.

  • shure.com/docs

    Public, and the best proof of the rest of this list

    The public documentation platform, fed straight from the publishing pipeline so what a customer downloads matches what actually shipped.

  • Print production suite

    The archive of every Shure print publication

    Writers enter the press specification — colours, paper stock, printer, cover treatment — and upload the PDF. The application files the record and the asset, raises the print order, and tracks it to delivery.

  • Acquia DAM migration

    ~1,000 print publications, 2025

    Led the move of that archive into Acquia DAM — assets and their production metadata, migrated in waves, with no publishing freeze and nothing left behind.

  • In-house CCMS → Heretto

    Second platform migration, no rollback

    Migrated the CCMS and rebuilt the pipeline around it end to end: authoring, review, output generation, distribution.

  • PDF generation

    Every downloadable guide on the site

    Built the conversion and typography for the downloadable guides with PDFReactor, so a generated PDF looks like something a designer laid out.

  • Distributor pricebook

    Built for Global Marketing Operations

    Generates a distributor catalogue on demand from the product data, cut by region, so nobody assembles one by hand.

  • TalentLMS → Salesforce bridge

    Two systems that had never spoken

    LMS certifications land on the distributor's CRM record automatically, instead of being re-keyed by somebody.

  • Three environments, and the move to AWS

    Dev · staging · prod — on-premise, then AWS

    Ran development, staging and production for the platform, and moved all three from in-house servers onto AWS.

Case studies

How I work, in three of them

The problem, what I did, and what changed afterwards.

Replacing Shure's in-house asset archive with Acquia DAM

Roughly a thousand print publications and their production metadata, moved in 2025 without a publishing freeze.

  • Migration
  • Metadata
  • Governance
  • Change management

The problem

Assets lived in a home-grown system where metadata was inconsistent and handoffs were manual. Nobody could answer "is this the current version?" without asking a person, and that person was often me.

What I did

  • Sat with the teams that actually search for assets and built the metadata model around how they look for things, not around how the old database happened to be shaped.
  • Migrated in phases so publishing never stopped — each wave was validated against the old system before the old path was turned off.
  • Wrote the validation scripts and the adoption guide, then ran the training, because a migration nobody adopts is just a second system to maintain.

What changed

  • Asset ownership and versioning became something you can look up instead of something you have to ask about.
  • Governance rules now live in the platform's own controls rather than in tribal knowledge and a shared spreadsheet.
  • The old archive was switched off with nothing left behind — the migration ended, instead of leaving a second place people still had to check.

Rebuilding the docs pipeline: in-house CCMS → Heretto

Authoring, review, build and distribution — rewired end to end, with no publishing freeze and no rollback.

  • CCMS
  • DITA
  • Automation
  • Reliability

The problem

The legacy pipeline was fragile in a specific way: when a build failed, there was no good way to find out why. That made every release feel risky, so releases got batched, which made them riskier.

What I did

  • Mapped the real workflow first — including the undocumented manual steps people had quietly added to work around the tooling.
  • Rebuilt the pipeline around deterministic outputs and real error reporting, so a failed build says what broke instead of failing silently.
  • Ran the cutover with the web team in the loop, so every downstream consumer kept working through it — nobody found out from a broken page.

What changed

  • Publishing went from a batched, nervous event to a routine one.
  • When something does break, the pipeline says so — which is the difference between a ten-minute fix and an afternoon of guessing.

The admin surface behind ~350 publications

One place to see documentation state, instead of three systems and a person to ask.

  • Web platform
  • UX
  • Content ops
  • Integration

The problem

Answering "what's published, what's stale, what's in review?" meant checking the CCMS, the DAM, and the live site, then reconciling them by hand.

What I did

  • Built the interface around the question people were actually asking, rather than mirroring the internal system boundaries.
  • Wired it into the existing pipelines so what it shows is generated state, not a hand-maintained list that drifts.
  • Kept it boring and fast, because the people using it are not engineers and do not want a tour.
  • Put publish and unpublish in the writers' hands, per language, so shipping a guide in another language stopped needing an engineer.

What changed

  • Ops questions that used to take a Slack thread now take a page load.
  • Non-engineering stakeholders can self-serve, which is the only kind of visibility that survives me being on holiday.

Experience

The whole record, in order

Most recent first, across Spain, Italy and the US. Durations are computed from the dates, and the one role that overlapped says so.

Shure Incorporated

Senior Full Stack Developer · Full-time

Remote · Illinois

Nov 2018 – Present

7 yrs 10 mos

  • TypeScript
  • Angular
  • Next.js
  • Node.js
  • eXist-db
  • XQuery
  • DITA
  • AWS
  • PDFReactor
  • Salesforce
  • I own the systems Shure's technical documentation is written in, built by, and published through — from the authoring tool the writers open every morning to the pages a customer downloads at shure.com/docs.
  • Built the in-house component CMS the technical writing team authors in: the editor, the administration surface, and the publishing side that turns their work into guides, print masters, and downloadable PDFs.
  • Led the migration of the in-house asset archive into Acquia DAM in 2025 — roughly a thousand print publications with their production metadata, moved without a publishing freeze.
  • Led the second platform migration, the in-house CCMS to Heretto, and rebuilt the pipeline around it end to end — authoring, review, output generation, distribution — with no rollback.
  • Led the rollout for both migrations, not only the build: wrote the standards and the adoption guide, and ran the training for the teams who had to work in the new system on day one.
  • Ran the platform's three environments — development, staging and production — and moved all three from in-house servers onto AWS.
  • Started the platform on Angular and eXist-db/XQuery in 2018 and rebuilt the front end on Next.js in 2023.
  • Mentored two interns, mostly by writing down the parts of the system that had only ever lived in someone's head.

Manufacturing company (Illinois)

Quality Assurance Engineer · Full-time

Illinois

Mar 2018 – Nov 2018

9 mos

  • QA
  • Test planning
  • Defect triage
  • Release verification
  • Ran functional and regression testing ahead of production releases — the last check between a defect and a customer.
  • Wrote reproduction steps clear enough that developers could act on them without a follow-up conversation, and triaged priority with stakeholders.
  • Put structured test planning in place with engineering, so release sign-off became a decision rather than a hope.

AEDOS S.r.l.

Software Engineering Consultant · Independent consultant · remote

Remote from Central Illinois · client in Rome, Italy

Not US employment — an independent consulting engagement with my former employer in Rome, run remotely after I relocated to the United States.

Mar 2017 – Mar 2018

1 yr 1 mo

  • PHP
  • LAMP
  • MySQL
  • Consulting
  • Remote delivery
  • Kept building and maintaining the client applications I had been the maintainer of, so the team did not lose them.
  • Ran it entirely asynchronously across a seven-hour time difference — written handovers instead of meetings, which is the habit the rest of my remote career runs on.

AEDOS S.r.l.

Software Engineer · Full-time

Rome, Italy

May 2013 – Mar 2017

3 yrs 11 mos

  • PHP
  • LAMP
  • MySQL
  • Mobile web
  • Built and maintained the client web applications on a LAMP stack (Linux, Apache, MySQL, PHP) — the same applications the team kept me on to maintain afterwards.
  • Tested emerging mobile web techniques against real projects, and put into production only the ones that held up.
  • Worked in short delivery cycles with a bias toward reliability and maintainability, because someone else always inherits it.

Webmoda SLU

Web Designer · e-commerce support

Spain

2011 – 2013

1 yr 9 mos

  • Magento
  • Web design
  • E-commerce
  • Support
  • Web design for the storefront, working inside the Magento install the business ran on.
  • Front-line support for the shop: incidents triaged and fixed as they came in, which is where I learned how fast someone notices when a live store breaks.

Stockistas S.L.

Web Developer · e-commerce · Contract

Castellón de la Plana, Spain

2008 – 2011

3 yrs 9 mos

  • Magento
  • PHP
  • MySQL
  • E-commerce
  • Built and ran the online store for a clothing and accessories wholesaler — the whole e-commerce operation, on Magento.
  • Owned the storefront end to end — catalogue, checkout, and the stock integration behind it. My first production system, and the reason I have never been afraid of somebody else's database.

Portfolio

Selected work, most of it still live

Enterprise platforms, studio and client work, and the products in between. Every live card links straight to the running site.

Showing 7 projects.

01Featured projectEnterprise · 2018 – present

Shure Product Documentation

Enterprise docs platform · public at shure.com/docs

Shure Incorporated's own product site. My part: the publishing pipeline, the admin surface, and the DAM/CCMS integration behind it.

shure.com
Shure Product Documentation screenshot
2
Platform migrations led
5
Document categories
2018
On the platform since

The public documentation platform for Shure's product line, wired into the publishing pipeline so what a customer downloads matches what actually shipped — no hand-maintained index in between.

  • Faceted catalogUser guides, quick starts, command strings, system requirements and training — searchable across the product line.
  • Generated, not curatedPer-model downloads come straight out of the publishing pipeline, so nobody maintains a list by hand.
  • Locale-aware deliveryGuides are published per language, and the admin surface behind the site is wired into the DAM, the CCMS and the web team's consumers.
Enterprise WebContent OpsWorkflowHerettoAcquia DAM
Visit live site (opens in a new tab)Read the case studies
02Featured projectStudio · Client project

iNTERVOLUTIONS

Digital engineering studio · client work

Built for the studio. My part: the front end, the internationalisation, and the hosting it runs on.

intervolutions.com
iNTERVOLUTIONS screenshot
Solo
Delivered end to end
ES / EN
Languages
Static
Runtime cost

A studio site built to tell one continuous story, from the first line of code to the server that keeps it alive — bilingual, animation-heavy, and still built to load instantly on a cold cache.

  • Three-service narrativeDevelopment, IT consulting, hosting & cloud — a story rather than a flat service list.
  • Live case-study reelsCase-study reels and an interactive in-page terminal, with ES/EN routing that runs off one codebase.
  • Static Astro front endOn Cloudflare, so the motion never costs the visitor a slow first paint.
AstroTypeScriptTailwindCloudflarei18nMotion
Visit live site (opens in a new tab)See the work (opens in a new tab)
03Featured projectProduct · 2026

Tombatossals Softworks

Indie game studio · The Penumbra Directive · ES / EN / IT

tombasoft.com
Tombatossals Softworks screenshot
2 (unreleased)
Titles announced
ES / EN / IT
Locales
Static
Runtime cost

Site for the indie studio I founded, built as a declassified dossier: CRT terminal aesthetic, live telemetry HUD, and roadmap panels that read like intercepted paperwork.

  • Dossier-style product pagesOne per title, for The Penumbra Directive and El Míster.
  • Live telemetry panelA telemetry HUD in the page, with GitHub org stats pulled from the public API at runtime.
  • Trilingual and trackerlessES/EN/IT, fully static, zero third-party trackers — by design, and stated on the page.
AstroStatici18nMotionGame studioPerformance
Visit live site (opens in a new tab)The Penumbra Directive (opens in a new tab)
04Media · 2015

CriticaBits.com

Media platform · editorial structure · SEO-first publishing

criticabits.com
CriticaBits.com screenshot

Tech and retro-gaming publication with a strong editorial voice, a structured layout, and a WordPress setup built to still be maintainable a decade later. It is — the site has been running since 2015.

  • Editorial system
  • SEO structure
  • Editorial voice
WordPressSEOPublishingContent
Visit live site (opens in a new tab)Case study (opens in a new tab)
06App · 2014

Health records vault

Standalone application · healthcare context · secure data workflows

private — ask me about it
Health records vault screenshot

A patient-records vault application delivered for a healthcare provider in Europe, where access control mattered more than anything on screen. Not publicly viewable.

  • Healthcare context
  • Access control first
  • Standalone delivery
AppSecurityWorkflowDelivery
Ask me about it
07App · 2016

AnalizaTuWeb — site analysis tool

Web app · one input, one answer

private — ask me about it
AnalizaTuWeb — site analysis tool screenshot

A website analysis tool with a deliberately narrow scope: you paste a URL, you get a report you can forward to a client as-is. No dashboard, no onboarding, no account.

  • Tool-first UX
  • Forwardable output
  • Scoped deliberately
Web AppUXDataAutomation
Ask me about it

Skills

Where I'd back myself

Not every library I've touched — three areas, and what each one buys you.

Full-stack engineering

Front end through integration — I ship the whole thing, then document it.

  • Production React/Next.js and TypeScript, with an architecture the next developer can read.
  • APIs and integrations built to be debugged at 2am by someone who is not me.
  • Performance treated as a requirement, not a cleanup task: measured before and after.

What that buys you: code the next person can take over, and handovers that do not need me on a call.

  • TypeScript
  • Next.js
  • React
  • Angular
  • Node.js
  • PHP
  • Ruby on Rails
  • PostgreSQL
  • MariaDB
  • AWS
  • Shell

Content platforms & publishing

CCMS and DAM migrations, pipelines, governance, and getting people to actually use them.

  • Rebuild content pipelines end to end — authoring → review → publish → outputs → distribution — while the old one is still publishing.
  • Design metadata and governance models around how teams search, not around the old schema.
  • Replace manual steps with automation and validation, and put ownership somewhere a person can look up instead of asking.

What that buys you: publishing that is routine instead of risky, and a lot less "ask Dave".

  • Heretto
  • Component CMS
  • DITA
  • XQuery
  • eXist-db
  • Acquia DAM
  • PDFReactor
  • Salesforce

Leading the rollout

The part of a migration that is people, not code.

  • Write the standards down, then keep them current — an out-of-date runbook is worse than none.
  • Coach directly and consistently, and review code the way you would want yours reviewed: specific, not encouraging.
  • Plan around the humans: training, adoption, and the fact that everyone is already busy.

What that buys you: migrations that get adopted rather than tolerated.

  • Team leadership
  • Coaching
  • Change management
  • Training
  • Stakeholder comms
  • Standards

Education

Education and honors

One degree, two majors — the engineering half and the leadership half.

Bellevue University

Bachelor of Science — double major in Computer Information Systems and Business Management & Leadership

  • GPA 3.99/4.00
  • Summa Cum Laude
  • Omega Nu Lambda honor society

Earned in full while working full-time as an engineer.

The business and leadership major was the deliberate half — I want to run engineering organisations, not only build for them.

Programme details(opens in a new tab)

Honors

  • Omega Nu Lambda honor society · Invited on academic standing.

Languages

Languages I work in

Four, across three countries I've actually lived in.

  • English

    Full professional proficiency

    Daily at work

    My working language in US roles since 2018 — technical work, cross-functional alignment, and coaching.

    • Engineering
    • Stakeholder comms
    • Leadership

  • Español

    Native

    Native

    Native speaker. I write, review and ship Spanish-language content.

    • Engineering
    • Writing
    • Content

  • Català

    Native

    Native

    Native speaker.

    • Writing
    • Localisation

  • Italiano

    Full professional proficiency

    Professional

    Full professional proficiency, from four years working in Italy.

    • Engineering
    • Client work

Volunteering

Giving back

Skills pointed at places that need them and have no budget for them.

None of this was employment, which is why it sits here rather than in the work history above. It is also some of the work I am most glad to have done.

  • A children's advocacy non-profit

    2020 – present · 5 yrs 11 mos

    Technical consultant · unpaid

    Illinois

    I look after the technical side for a small children's advocacy non-profit, as an unpaid collaborator — the public site, the way donations come in, and the infrastructure underneath both. Organisations this size rarely have anyone in-house to ask about any of it; a lot of the value is simply being the person they can ask.

    • Built and maintain their website
    • Set up and support online donations, so giving works on the first try and the receipts are right
    • Hosting, domains, DNS and certificates — the things that quietly expire and take a site with them
    • Backups and recovery, tested rather than assumed
    • The person they call when something breaks, which is the part that actually matters

  • Municipal civil protection corps

    2004 – 2013

    Volunteer officer · unpaid

    Spain

    Trained and on call with a municipal volunteer emergency corps, alongside study and work.

    • Event control and public safety support
    • Basic first aid
    • Evacuation support
    • Preventive patrols
    • Response to floods, fires, snowfall and search operations
    • Directing the public and assisting traffic control under police coordination

Contact

What are you trying to replace?

Tell me what you're building. I'll give you a straight answer about whether I'm the right person for it — including when I'm not.

Email is the fastest way to reach me

Tell me what you’re working on and I’ll come back with a straight answer about whether I’m a fit — including when I’m not.

Email Dave

[email protected]

LinkedInopens in a new tabGitHubopens in a new tab

Where I’m at right now

Happy where I am and not looking. I'll always make time for a conversation about leading an engineering team, though. Remote only.