What we look for when we hire at FBK

We get asked this a lot, especially by candidates who are early in their careers: what does FBK actually look for when hiring?

The honest answer is that there's no single profile. Our team includes people with backgrounds in computer science, linguistics, public administration, data science, and business — and that diversity is intentional. But there are a few things that consistently matter.

We care less about where you studied and more about how you think. The problems we work on — extracting structured data from messy procurement documents, building reliable AI systems for enterprise clients, navigating complex regulatory frameworks — don't have textbook solutions.

What we need are people who are genuinely curious, who ask good questions, and who are comfortable saying "I don't know, but I'll figure it out."

FBK is not a big company. We don't have layers of management or approval chains. That means everyone has real ownership over their work — and real accountability for the outcome.

We look for people who want that. People who take initiative, who see a problem and fix it without waiting to be asked, and who care about the quality of what they deliver.

Building enterprise software for a regulated industry means working with clients who have specific, complex needs. Being brilliant technically isn't enough if you can't explain your work, listen to feedback, and collaborate across teams.

We value people who can communicate clearly — in writing, in meetings, in code reviews. This isn't about being extroverted; it's about being thoughtful in how you share information.

We're building products that our clients depend on for critical business processes. That requires a mindset oriented toward reliability, maintainability, and long-term value — not just shipping fast.

We look for people who care about doing things right, who think about edge cases, and who understand that the best code is code someone else can read and maintain.

You don't need to know anything about public procurement when you join. But you do need to be interested in it — or at least open to becoming interested. Our best people are the ones who get genuinely engaged with the domain, who understand why what we build matters, and who can connect their technical work to real-world impact.

Our process is straightforward: an intro call with someone from the team, a technical or case-based exercise depending on the role, and a conversation with leadership. We try to be fast, respectful of your time, and transparent about where we are in the process.

If any of this resonates, take a look at our open positions.