Independent engineering / Phil Arfuso

Senior engineering.
Steady progress.

Senior Full-Stack Engineer & Software Consultant

Project-based development and ongoing, part-time engineering support for founders and agencies.

Tell me what you’re building

Available for contract and consulting work

Ways to work together

What do you need help with?

Bring a defined piece of work, add ongoing engineering support, or start with a review of your application.

Project development

For a new feature, an application build, or extra development capacity for your agency.

Typical deliverables

  • Working features across interface and backend
  • Tests, review, and release support
  • A clear handoff to your team
Scope and working arrangement

Focused development for an existing product, a new feature, or an agency delivery gap. I work across React, Next.js, TypeScript, APIs, and PostgreSQL.

A defined project or agreed blocks of engineering capacity, working with your existing team and tools.

Deliverables, dependencies, and release responsibilities are agreed before work begins. Additional scope is discussed separately.

Discuss project work

Ongoing engineering

Keep an existing product moving with regular development, maintenance, and technical decisions.

Typical deliverables

  • A prioritized engineering plan
  • Features, maintenance, and modernization
  • Documented decisions and regular progress updates
Scope and working arrangement

Hands-on engineering with the continuity to understand your system, make practical technical decisions, and carry improvements through delivery.

Fractional engineering with agreed part-time capacity, priorities, and a regular communication rhythm. Technical leadership can be included when its responsibilities and decision authority are explicitly scoped.

Capacity, response expectations, and support responsibilities are explicit. This is not unlimited support or an on-call service.

Discuss ongoing support

Technical assessment

Review an existing application or investigate a technical concern before deciding what to build or change.

Typical deliverables

  • Evidence-backed findings and constraints
  • Prioritized recommendations
  • A readout and scoped options for follow-on work
Scope and working arrangement

A focused review of an existing application or a specific technical concern, turning observations into a practical path forward.

A short, separately scoped engagement with agreed questions, access, and a written readout.

The review is limited to the agreed system and questions. Implementation, certification, and ongoing support are separate engagements.

Discuss an assessment

Relevant experience

Examples from an enterprise platform, a product I co-own, and a client website.

Conceptual platform illustration

MEMX

Full-stack developer

Built portal tools and full-stack features at MEMX. My manager established the database-driven market architecture; I built the frontend system around it.

Case study
Domani’s Today screen, with daily progress, a top priority, and a short task list.
Domani · production app

Domani

Co-owner & full-stack developer

Co-own Domani with a UX designer. We make product and design decisions together; I carry engineering through development, releases, analytics, and production support.

Case study
Photography displayed within a framed Iffer’s Pictures website composition.
Client website · design and development

Iffer’s Pictures

Designer & developer

Shaped a photography portfolio from discovery and copy through visual design and development.

Case study

Getting started

How we’d work together

  1. Start with the context

    Tell me about your product, the problem, and the timing. An informal email is enough to begin.

  2. Find a useful starting point

    We discuss fit, constraints, and what success would look like, then agree a bounded scope or capacity arrangement.

  3. Build with a clear rhythm

    Work moves through implementation, review, and delivery with visible progress. Any follow-on engagement is agreed separately.