Flarseo
This translation is being reviewed. The Italian text remains the reference version.
We are few, and you can tell, for better and worse
Flarseo is built by a small Italian team working remotely. There are no middle layers, committees or long processes: whoever joins touches the product in the first week and sees their decisions land straight away.
Few rules, actually applied
We are not promising an extraordinary company culture. We are promising a place where decisions are quick, work is visible and nobody ends up writing slide decks to justify what they did.
- Remote work, with hours agreed rather than imposed.
- Meetings kept to a minimum: we write more than we talk.
- Whoever starts something carries it through, from decision to release.
- The product is in customers' hands every day, so releases are frequent and small.
- People make mistakes, say so and fix them. Nobody builds a case out of it.
The roles that open, when they open
There is no published hiring plan: we open a role when the work stays consistently ahead of the people we have. These are the areas where that happens.
Product engineering
The platform, the integrations and the layer that orchestrates language models. The work is in PHP, JavaScript and the infrastructure holding it together.
- People who read other people's code before rewriting it
- People comfortable with systems in production
- People who have worked with language models, or seriously want to
Content and review
Defining how the system should write, reviewing what it produces and raising the bar when it needs raising. The work is about language, not volume.
- People who write well and can say why a sentence fails
- People who check a source before citing it
- People who are not offended by reading text a machine wrote
Research and ranking
Working out why a page rises or falls, turning that into rules the system can apply by itself, and checking they hold on real customers.
- People who have delivered measurable results, not just reports
- People who know local SEO and its oddities
- People genuinely curious about visibility inside conversational assistants
Support and customer success
Talking to businesses who do not do this for a living, finding the real problem behind the question and carrying it back into the product.
- People who write clear answers without sounding like a manual
- People who can say no and explain why
- People who note what breaks and keep pushing until it is fixed
How we handle an application
We read it
A person reads it, not an automatic filter. We answer everyone, including when the answer is no: a clear no beats silence.
We talk
A conversation, not an interrogation. We tell you how things really are, awkward parts included, and we ask you to walk us through something you have made.
A paid trial piece
If it makes sense for both sides, we propose a small, concrete, paid piece of work. It lets you see how we work and lets us see you working.
Things to know before writing
- We are small: anyone looking for an established structure and a mapped out career path will not find it here.
- We have no office to show off in photographs. Work is remote and we meet when there is a real reason.
- The work is varied by necessity: whoever joins also does things that were not in the job description.
- A collaboration can start part time or per project, if that is the shape that works for both sides.
- The working language is Italian, but the product is multilingual, so being comfortable with technical English matters.
Nothing advertised right now? Write anyway. Speculative applications stay in our archive and we go back through them when something opens.
Tell us about something you have made
No cover letter needed. A piece of work you are proud of, explained in ten lines, tells us far more.
Want to understand what we are building first?
The quickest way is to look at the product at work, or to read how we describe it.