AI Best Practices (ai-best-practices.com) is a knowledge platform and toolset that helps enterprises benchmark and improve how they apply AI across their value chains. It pairs a content-rich Wiki — covering use cases, AI tools, ROI frameworks, and industry categorization — with Librarian, an AI-driven backend that curates, scores, and surfaces that content. The platform serves C-suite and VP-level decision-makers evaluating AI maturity, tooling, and vendor fit across industries.
AIBP is a product line built and operated by McFadyen Digital. This role owns the full-stack engineering of the AIBP web application portfolio (Wiki, Librarian, and the surrounding product surface) end-to-end — including how work is planned, ticketed, sequenced, and released.
Job Description
Do you want to own architecture, delivery, and release for a fast-moving AI-native product line — not just write code for one? Can you turn a rough roadmap into a sequence of self-contained, agent-ready Linear tickets without anyone needing to ask a follow-up question? Have you made Claude Code and Claude.ai your daily driver for coding, planning, and ticket-writing, and built your own skills, hooks, or MCP integrations on top of them? Can you judge in seconds when AI-generated code needs a second look — especially around auth, access control, or anything destructive? Do you thrive in fast, ambiguous, unscoped delivery rather than traditional phased client work? If you answered yes, then we want to talk to you!
We need a full-stack tech lead to own fast-moving AI-native products end-to-end — and to be the person who turns roadmap into shipped software through well-run Linear tickets, realistic timelines, and clean releases. We build with AI as a first-class part of the workflow: Claude (Claude Code and Claude.ai) is our daily driver for coding, ticket drafting, planning, and status reporting, alongside agentic coding tools, custom skills/hooks/MCP servers, and spec-driven plan/execute/verify loops. You'll work the same way — full-time, hands-on daily, owning architecture, planning, and delivery, and mentoring/reviewing other engineers.
Responsibilities
Top 5 responsibilities
1. Own architecture and technical direction across the AIBP web application portfolio — data model, auth/access control, API design, and deployment.
2. Ship full-stack features end-to-end — UI, backend logic, schema/migrations, and cloud deploy.
3. Plan and run the team's work in Linear as the single source of truth — break initiatives into tickets, sequence them against timelines, and keep status, priority, and dependencies accurate at all times.
4. Build and own delivery timelines and project plans, setting realistic estimates for a fast pace and flagging delays and blockers early with a clear cause and recovery plan.
5. Own the release process end-to-end — decide what ships, verify migration/deploy readiness, write release notes, and hold the rollback plan.
Additional Responsibilities
• Write and review tickets so they're self-contained and agent-ready — clear scope, acceptance criteria, and file/test pointers — whether executed by a person or an agentic coding tool.
• Use Claude (Claude Code and Claude.ai) as the default way of writing code, drafting/refining tickets, planning work, and producing status reports.
• Review PRs, mentor other engineers, and set technical and ticket-quality standards.
• Judge when AI output needs verification — especially auth, access control, and destructive data operations.
• Keep tests (unit/integration/E2E) and CI/CD gating healthy as things move fast.
• Report status concisely to stakeholders — what shipped, what's at risk, and what's needed to unblock it.
Linear & ticket quality: keep Linear accurate as the single source of truth (not a wiki or chat thread); maintain ticket hygiene — status, labels, priority, linked dependencies, sub-issue structure — continuously, not just before a status meeting.
Timeline & project planning: keep milestones, dependencies, and sequencing visibly current as scope shifts; surface risk and slippage the moment they're known, with a cause and recovery plan attached.
Release ownership: gate every release through CI/CD and required checks, confirm migration safety, and ensure release notes and a rollback plan exist for every release; run post-release monitoring and any hotfix path.