Falora.ai · Antwerp
Practical Where: Antwerp office, 4 days a week. 1 day from home. Level: Medior to senior Language: English (Dutch or French is a plus) Contract: Employee Team: Tech lead, a junior developer, a senior AI advisor, a Founding Product & GTM Lead, the founder/CEO, and you Don't tick every box? Apply anyway. If you've built and shipped real software, we want to hear from you. Why we're hiring We're a small team with a big product. We want engineers who own their work from idea to production, help the team grow, and make us faster every month. What you'll do Own features end to end. You take on top-priority features and carry full responsibility for them: discovery, build, testing, release, and the bugs after. Figure out how to build it. The goal is set; the requirements are often vague. You talk to whoever you need, ask the questions, and find the best way to deliver it. Write the spec, then let agents build. You plan before any code is written, run several agents in parallel, and review everything they produce. Test it hard. Automated tests and manual testing, locally and on dev, before you open a pull request. Ship it and stay on it. If bugs show up in your code, you make sure to fix them. Help each other grow. Coach others on what you know, and learn from them in turn. Make the team better. Found a better tool or approach? Try it, prove it, bring it to the team. How we work This part is not optional. AI-native from day one. Specs before code, agents doing the typing, you owning every line that ships. The tools keep changing. What we use today may be gone in three months. You keep learning, and you're happy to drop a tool that stops working. High pace, high ownership. Small team, high output, no one to hide behind. This is a startup, not a 9-to-5 comfort job. Who you are We hire for character first. Skills can be learned; these can't. You own it. You don't wait for a perfect ticket. When something breaks, you say “I did this, here's the fix”, not “QA missed it”. You're a team player. You share what you know, you ask when you're stuck, and you enjoy building with others more than alone. You don't take yourself too seriously. You can joke, take a joke, and say “I don't know”. You work hard. You care about finishing things properly, not just starting them. You push back, with reasons. You question our process when you think it's wrong, and you give it a real try before you judge it. You're curious. You try new tools on your own and tell the team what's worth using and what isn't. What you bring — must have A proven track record of building and shipping production software that people use Strong Python Strong system design: you model data properly in a relational database, design APIs that others can use without reading your code, and can explain the trade-offs behind a system you designed Comfortable in React and TypeScript, so you can own a feature front to back Comfortable with Google Cloud and infrastructure as code You use AI to code every day, with a routine you can explain: what you give the model, how you check its work, where it fails Nice to have Built LLM features or agents that real users touched Written specs or plans that an agent builds from Run more than one agent at a time FastAPI, PostgreSQL, LangGraph, Agno, or PydanticAI Our stack: Python, PostgreSQL with pgvector, React with TypeScript, Google Cloud, Terraform. Not for you if You want someone else to write the ticket, so you can just code it and clock out You see AI as autocomplete, or as something to avoid You'd rather work alone than grow a team You want a slow, predictable pace You'd rather stick to what you know than keep learning new tools and ways of working What we offer Real ownership: full responsibility for what you ship, and visible impact on the product A team that treats new tools and new ways of working as part of the job How to apply Send us three things. Your CV How you use AI to code (5–10 lines). Your tools, your routine, and one place where AI cost you time instead of saving it. One story (5–10 lines). Something you took from a vague idea to production. How did you design it, who did you talk to, and what went wrong along the way? [email protected] Hiring steps Conversation with one of the founding team Case Meet the team We'll get back to you within 7 days after each step.