Skip to content

Senior Engineer (LiveWire/Vue/Inertia) - NAMI - Thiago

  • Remote
    • Philadelphia, Pennsylvania, United States
  • Technology

Job description

Context

The work this engineer will actually do: their hardest blocker is the event management app, which has a page that is one enormous Livewire component containing what is effectively six different morphing forms, with validation logic, display logic, and business logic fully entangled. Test coverage is thin, and where tests exist, they touch lines rather than assert behavior. Untangling that into something testable is the prerequisite to any Vue migration — and that untangling, not the Vue rewrite itself, is what they want help with. 


Job requirements

Must-have technical skills

  • Laravel, deep and current. Multi-app ecosystems with shared databases, not just

  • single-app CRUD.

  • Blade and Livewire — specifically the ability to decompose oversized Livewire components. This is legacy-codebase work, not greenfield Livewire.

  • Vue 3 with TypeScript. They are explicit about TypeScript and explicit about Vue 3, not Vue 2.

  • Inertia.js — the target architecture for all apps.

  • Livewire → Inertia/Vue migration experience. Candidates who have actually done one and can talk about what broke.

  • Testing. PHPUnit, Vitest for front-end unit tests, and Cypress for e2e. They practice "test-forward" development and want someone who strengthens that habit rather than working around it.

  • Refactoring judgment. Can look at coupled validation/display/business logic and stage a safe path out of it while keeping behavior intact under weak test coverage.

  • MySQL.

  • Git / GitHub.


Strongly preferred

  • Spatie package ecosystem — they use these frequently, including laravel-data and the TypeScript transformer.

  • Salesforce as an identity provider. SAML SSO via Socialite, shared auth/session store across apps, permission scopes derived from Salesforce at login. Someone who has worked with Salesforce-backed auth will ramp much faster.

  • Design system work — building shared component libraries across multiple apps.

  • DigitalOcean. "I think some DevOps experience would be nice. I mean, we're not heavy in like AWS or anything. We use DigitalOcean." Depth here is not required; willingness is.

  • AI-assisted development. They use Claude Code and asked directly whether our engineers are fluent with it. Candidates should be able to describe their own workflow and where they trust or don't trust agent output.

  • Reverse-proxy / app consolidation patterns.

or