Senior Fullstack AI Engineer

Must-haves for every candidate

• B.E. / B.Tech in Computer Science or a related field (or equivalent degree).
• Strong written and spoken English youll write docs, review code, and communicate clearly with the team.
• Very strong prompting skills you can get reliable, high-quality results out of an LLM and know how to refine a prompt when it doesnt.
• Strong, hands-on proficiency with Claude Code we use Claude Code aggressively for day-to-day development, so this is core, not optional. You drive AI coding agents fluently: scoping work, steering them, and critically reviewing their output for correctness and security rather than accepting it blindly.

The Role — Senior Full-Stack Engineer

You’ll own features end-to-end across our Next.js application, our Python backend services, and the PostgreSQL data layer: from the API route and database schema to the React UI a recruiter actually clicks.

What you’ll do

• Build and own features end-to-end across the App Router stack — server components, API route handlers, repositories, and React UI.
• Build and maintain Python services — FastAPI/Flask microservices and Azure Functions / queue-driven cron workers that power sourcing, sync, integrations, and AI reporting.
• Design PostgreSQL schemas, write performant SQL/RPC functions, and reason about row-level security and multi-tenant data access.
• Integrate third-party services (storage, queues, payments/credits, messaging, external recruitment APIs) cleanly behind well-typed boundaries.
• Set patterns and review others’ code — raise the bar on typing, testing, and documentation.
• Diagnose production issues across the stack: a slow query, a flaky test, a realtime sync bug, a caching edge case.

What we’re looking for

• 5–7 years building and shipping production web applications.
• Deep TypeScript and modern React; real experience with a server-rendered React framework (Next.js strongly preferred).
• Strong Python — production experience with FastAPI and/or Flask, and comfort owning backend services and async/queue-driven workers.
• Strong SQL and relational data modelling — you can read a query plan and know why it’s slow.
• Fluent with Git — branching, rebasing, and a disciplined PR-based workflow; you write clean commits and give thorough code reviews.
• Experience in a multi-tenant or permissions-sensitive system; you take data isolation seriously.
• A track record of owning features, not just tickets — you think about the user, the edge cases, and the on-call cost.

Nice to have

• Supabase (or Postgres + RLS) in production.
• Realtime data, caching strategies (Redis), or background job processing.
• Comfort working near AI/LLM features.

Our stack

• Frontend: Next.js 14 (App Router), React, TypeScript
• Backend (TypeScript): Next.js route handlers (repository pattern)
• Backend (Python): FastAPI + Pydantic microservices, Flask/Flask-RESTful (AI + reporting), Azure Functions (durable) & queue-driven cron workers
• Data: PostgreSQL (Supabase) — RPC, Realtime, Row-Level Security,
• AI: LLMs via OpenRouter / OpenAI / Anthropic behind a provider-agnostic factory; embeddings

+ semantic search

• Infra: Azure (Blob Storage, Cache for Redis), Docker, Kubernetes
• Tooling & quality: Git + GitHub (PR-based workflow), Jest, ESLint, typed end-to-end, CI on every PR

How we work

• AI-first development — we use Claude Code aggressively across the codebase. You’ll be expected to ship faster with AI agents and hold a high bar on reviewing what they produce.
• Ownership over hand-offs — you own the feature from schema to UI (or service to job), including the docs.
• Documentation is shared memory — we write things down so the next engineer reads one file, not five.
• Quality is non-negotiable — typed, tested, reviewed; security and data isolation are first-class.
• Pragmatic, not dogmatic — we ship, we measure, we improve.