Ambiguous requirements, evolving production systems.
Hello, I’m Anna — a Senior Full-Stack Engineer with 8+ years of experience building multi-tenant products and internal admin platforms. As an independent contractor (2021–2025), I delivered several 0→1 systems end to end: virtual-goods admin with B-end payment reconciliation, a multi-tenant train-booking frontend, and a small multi-tenant content platform.
Most recently I shipped jobsignal.dev — a live multi-agent LLM pipeline (Python + Next.js + SQLite) with Tavily tool calling, schema validation, and golden-set eval gates that improved accuracy from 93% to 97.3%. I value clear documentation, async collaboration, and shipping systems that teams can actually maintain.
My Journey: From Code to Craft
JobSignal — LLM Application Engineering
jobsignal.dev parses Hacker News hiring posts through a multi-agent pipeline. Each stage has schema validation and verifier checks; a golden-set eval gate tracks quality over time (93% → 97% → 97.3%). The stack is Python for the agent pipeline, Next.js for the UI, and SQLite for storage. Tavily powers web search tool calling. The product is live and iterates on real hiring data.
Independent Development (2021–2025)
Across client engagements I owned full delivery cycles — from schema design to production monitoring. Highlights include a 0→1 internal admin for virtual goods (catalog, promos, multi-storefront config) with B-end Stripe/PayPal reconciliation (status sync, fee validation, anomaly alerts); a 0→1 multi-tenant train-booking frontend for travel-agency tenants; and a compact multi-tenant content platform with company accounts and multi-channel aggregation. I also unified access-control patterns across Go services and the frontend, plus third-party JWT auth integration.
Engineering Foundations & Tech Debt
Alongside feature work I focused on making codebases sustainable: frontend stack upgrades, test coverage, structured logging, and monitoring (Sentry, Grafana). For internal admin systems — virtual-goods ops and content distribution — I design streamlined B-end configurations, wrapping layout primitives into domain-specific, autocomplete-heavy components to systematically eliminate form fatigue and reduce operational cognitive load. Multi-tenant frontends (train booking, content platform) use custom in-house component layers instead. I’m comfortable across TypeScript/Next.js, Vue, Angular, Go, and Python — and I prefer incremental modernization over big-bang rewrites.
My Engineering Philosophy
📝Business-First Approach
I don't just clear tickets. I ask questions. "Will this database schema support our future growth?" "Is this UI intuitive for the admin staff?" I build with the long-term vision in mind.
📈Documentation is Culture
In a distributed team, if it isn't written down, it doesn't exist. I pride myself on writing clear migration docs, API specifications, and "Why-I-Did-This" commit messages.
🚀Reliability & Autonomy
I am comfortable navigating Linux environments, debugging SQL queries, and configuring GitHub Actions and GitLab CI/CD pipelines. I value the trust that comes with remote work and deliver results without needing constant supervision.
My Core Toolkit
- Frontend
- TypeScript / Next.js / Vue.js / Angular — Ant Design (internal admin), custom components (multi-tenant)
- Backend
- Go / Python / Node.js — RESTful APIs, Casbin RBAC, Interface Contracts
- Data
- PostgreSQL / MySQL / SQLite / Redis / Schema Design
- DevOps & Ops
- Git / GitHub Actions / GitLab CI / Eval gates / Sentry
Outside of the IDE
Systems need boundaries, and so do engineers. Outside the IDE, I reset through long-distance cycling and batch cooking — ingredient scaling and all.