Working here

This is the honest pitch, not the recruiting version. It tells you what you'd actually be signing up for, rough edges included. Read it before you decide you want in.

Who thrives here

Self-directed people who care about craft. If you see something broken and your instinct is to fix it rather than file a ticket and wait, you'll feel at home. We hand you a problem and the room to solve it, and then we mostly get out of your way. That's freedom, and it's also a weight. Nobody is going to hover over you with a plan.

The people who do well here are opinionated but not precious. They write things down. They'd rather ship one good thing than ten fine ones, and they can tell the difference. They're comfortable being wrong in public and correcting course without making it a whole thing.

Who won't

People who need a lot of structure. There's no dense process to hide inside, no manager assigning your day, no meeting that tells you what you're supposed to think. If that sounds unnerving rather than freeing, this will be a hard place to work, and that's a real answer. Not everyone wants the same job.

People who need an audience won't either. The status meeting, the deck built for the sake of the deck, the performance of being busy: we don't have those, and we won't invent them for anyone. See our values for what we do instead.

What we expect

• Ownership. You own outcomes, not tasks. "It wasn't my job" isn't a sentence we say much.
• Writing. We're remote and we build in the open, so writing is as much the job as the code is. If it isn't written down somewhere others can find it, it barely happened.
• Working in public. Most of what we make is readable by anyone. That takes a little courage at first and then becomes normal.

Remote-first, and what that means

We're remote by default and async by habit. That's not a perk, it's the design: we want the best person for a thing, not the closest one, and we want a workday that bends around your life instead of the other way around. It works because we write instead of interrupt, and because "I'll get to it" is a fine answer to most messages. See how we work for the mechanics, and time off for how we think about hours.

Your first week

There's no boot camp. Week one is mostly reading and doing. You'll read the handbook, poke around the code, and pick up something small and real (a fix, a paper cut, a rough edge) and ship it. We'd rather you touch the actual work early than sit through a week of onboarding slides. Someone will be your point of contact, questions in the Discord are always fair game, and nobody expects you to have it all loaded in your head by Friday.

We're small and early

Be clear-eyed about this. We're a small company early in our story, building in the open, and that's the upside and the catch in the same breath.

The upside: there's a lot still open, and you get to shape it. Your fingerprints will be all over what Flagon becomes. There's no legacy to apologize for, no committee to convince.

The catch: some things are held together with tape. Not everything is documented. Priorities shift when we learn something. If you need a company that's already got everything figured out, we're not it yet. But if you'd rather help figure it out, that's exactly the job. Come say hi at hey@flagon.io.