Descripción de la oferta
***** SHORT VERSION *****
Los candidatos deben tomarse el tiempo de leer atentamente todos los elementos de este anuncio de empleo. Por favor, envíen su solicitud sin demora.
We're building an AI-native platform with autonomous agents, smart workflows, and real-time voice interactions. Looking for a Full-Stack Engineer.
Salary: €60k-€80k
Hybrid: BCN 3 Days, Remote: 2 Days. Don't apply if you're not from Barcelona.
Team: of 3 co-founders now. 6 by the end of the year. You will be our 1st employee!
Feel free to send me a direct message and tell me whatever you'd like.
***** LONG VERSION *****
Key Information:
Who are we? We're a SaaS AI hiring startup, founded in October 2025.
What are we aiming for? To offer a simple, unique, and differentiated solution that addresses some of the recruiter's most painful problems.
What drives/obsesses us? One of the founders has +20 years of recruiting experience, founded and , and has tested every ATS on the market — he'll be a heavy daily user.
Product: AI Interviews/Agents + Omnichannel/All-In-One: WhatsApp + LinkedIn + Email. We'll be the first to launch something key in the fast detection of talent.
Market: Primarily the US, but global from day one.
Customers: ICP: We are going Enterprise & Mid market (High Volume Recruiting)
Product: will be extremely simple: only the features that solve the recruiter's biggest pains.
Risks: Like in any startup, they exist, and we'll explain them during the interview.
Founding team:
Funding: Well-funded with 2 years of runway. Investors: +10 successful entrepreneurs with exits in their projects.
Goal 2026: full focus on acquiring customers.
Tech & Challenges
You'll own features from the first commit to production monitoring. We ship fast, identify what's imperfect, and build systems as friction emerges.
1. Ship Features Fast, Build Platform as You Go
Design and ship end-to-end features (Next.js frontend → FastAPI backend → Supabase)
Identify when manual deploys/testing/monitoring hurt, automate them.
Create reusable patterns for common integration needs (data-access, webhooks, auth, data sync)
You'll ship the feature this week, automate the deployment next week, extract patterns the month after.
2. Integration Architecture for HR Tech Stack
Design API patterns that work for ATS, HRIS,, LinkedIn, email providers, and future integrations.
Build webhook handlers, auth flows (OAuth, JWT), data sync pipelines.
Make integrations testable, observable, and resilient from day one. Monitoring and self-healing is critical.
Think about how to "eat" external providers when appropriate.
3. Safe Deployment & Monitoring
Set up monitoring/tracing for every feature you ship (know what breaks and where)
Create deployment automation as manual deployment pain increases.
Build internal tooling to make deployments safe, routine, and low-friction.
Know when to ask for help setting up observability, then automate it for next time
Our stack: Python/FastAPI, Next.js 14+, Supabase, Docker, GitHub Actions, and infrastructure as code patterns.
You Are
Must-haves:
4+ years professional software engineering (full-stack)
Proven ability to ship features end-to-end (Next.js + Python/FastAPI preferred)
Experience and excitement towards AI Agents (coding agents, LLM APIs)
Experience with monorepos, deployment automation, CI/CD, Docker.
Strong API, webhook, and authentication pattern knowledge (OAuth, JWT)
Balance pragmatism and perfection - ship fast, know what's imperfect, fix systematically.
**AI/LLM proficiency is required**: You are a heavy user of AI coding agents (Claude, Cursor, GitHub Copilot, or similar) and LLMs in your daily workflow. AI-assisted development is not optional - it will be expected and enforced.
Ownership mindset:
You own features from first commit to production monitoring.
You automate when manual work becomes painful, not before.
You ask for help setting up observability when needed, then automate it.
You identify where things need monitoring and either set it up or escalate appropriately.
We test for:
Can you ship a feature AND identify where it needs monitoring?
When you encounter friction (deploys, testing, integration), do you automate or accept it?
Can you collaborate with founders on technical decisions while still moving fast? xiphteb
Do you think in systems - how does this feature connect to everything else?
Nice to Have:
