NEXTELEVEN
01 Hiring · Primary path

Mansfield, Texas · Remote United States · U.S. citizen · No sponsorship required

Bring me the problem that will not stay fixed.

I’m Sean McDonnell. I work across support, implementation, backend systems, integrations, and applied AI. I trace failures to their source, build the repair, and leave the next person with evidence they can use.

Contact for roles ↗Download résumé ↓

Target roles

Work that crosses the interface and the system behind it.

Selected proof

Specific evidence. Explicit limits.

12

applications published on Apple’s App Store through NextEleven

Publication record only.
2

substantial private-client software systems completed

Client identities and outcomes withheld.
376

tests in the documented NextEleven Harness binary suite

A tested public proof of concept, not an adoption claim.
11

jobs passed in the documented cross-platform CI matrix

Including Windows build, release, lint, and tests.

Stack

Current working range.

LanguagesPython · Rust · TypeScript / JavaScript · Kotlin · Swift · SQL · Bash

Backend + dataFastAPI · REST APIs · PostgreSQL / pgvector · SQLite · Redis · Docker

AI + retrievalLLM APIs · tool calling · MCP · embeddings · RAG · hybrid retrieval · reranking · citations · evaluation

Interfaces + deliveryReact · Next.js · SwiftUI · Jetpack Compose · GitHub Actions · automated testing · CI

How I work

Investigate. Implement. Hand off.

  1. 01

    Investigation

    Reproduce the failure. Read the logs. Separate the visible symptom from the system that caused it.

  2. 02

    Implementation

    Define the boundary. Build the narrowest complete repair. Test normal operation and the failure paths that matter.

  3. 03

    Handoff

    Document the limits, checks, and operating path so the work can survive without the person who wrote it.

Role conversation

Contact me directly.

Contact for roles ↗LinkedIn ↗
02 Scoped consulting · Secondary path

One broken workflow. One accountable engineer.

NextEleven takes owner-operated engagements with a real boundary: a difficult failure, an incomplete implementation, a backend or integration, a retrieval workflow, or a system that needs stabilization and a usable handoff.

Start with the work that is failing now. Define done in writing. Expand only if the first piece proves useful.

Discuss a scoped build ↗