Brighty App under the microscope: team, medical history, hiring.

01Executive summary for the founder

If you read only one section — read this. Seven observations, each backed by the data below.

1. Brighty is a "spin-out" of neobank engineers. The founder-CTO and 3 of the 5 lead engineers came out of the same large neobank. The product was built by engineers from day one — the company is engineering by DNA.
2. This isn't a standalone startup — it's a node in a network of connected ventures. The team's prior employers cluster tightly on two founder structures — one crypto ecosystem and one founder's holding. 6+ people from the first, 5+ from the second. The team was assembled "from within".
3. The company added functions in textbook order. Engineering and product (2020) → legal (2021) → compliance, HR, marketing, support (2022) → finance and sales (2023). Classic maturation of a regulated fintech.
4. Right now, all the hiring energy has gone into control and regulation. 15 of 68 postings are compliance/AML, 8 finance, 4 information security. This is a company under regulatory pressure, building its "immune system".
5. Several key roles won't close. MLRO was reposted 6 times, AML officer 5, CISO 4, chief accountant 3. That's the marker of a supply-constrained market — exactly where we help.
6. Two "CEO" records are a structural nuance, not an error. One CEO since 2021 (from the founder's ecosystem), a second since 2025 with a "portfolio / local managing" profile. This looks like a licensing requirement: a dedicated director for the Baltic legal entity.
7. Two gaps on the surface: no growth and no data. The current headcount has no Growth / performance-marketing owner and not a single data analyst — for a consumer app, that's immediately visible. The Data Analyst role was opened twice and then closed.

02History: the company's story from the data

Six years on a single page. All reconstructed from the team's career histories and the hiring trail — we never opened a single internal system.

Brighty was founded in 2020 in Baar (Zug). On the same domain and registration there's an earlier entity under a former name — the traces show up in the data as a "dormant" second company page.

2020 — the engineering core

The founding cohort — 7 people, 6 of them engineers and product. Co-founder and CTO + 5 developers + a designer. Three of the engineers came from the same large neobank, another two from major banks. The company was born as an engineering team, not a marketing one.

2021 — legal

The first non-engineering hire — a lawyer. Logical: you can't build a crypto-fiat product in Switzerland without a legal frame.

2022 — operational maturity

Four functions at once: compliance/risk, HR, marketing communications, support. The year the product became a company: people who serve users and the regulator appeared.

2023 → 2026 — commercialization and control

Finance and sales (2023), then continuous hiring of control functions. 16 postings in 2024, 15 in 2025, already 13 in the first half of 2026 — the company is hiring actively and steadily.

03Where the team was assembled from — two bloodlines

The strongest observation of the history: the team's prior employers cluster on two founder structures. These aren't random hires off the market — it's a transfer of people from connected ventures.

04Current condition: the whole team, by name

45 people, grouped by function. For each — role, country, year joined, and one prior employer as an origin marker. This is what the company looks like from the inside, per our data.

05Structural diagnosis: what the analysis reveals

Three structural observations that only become visible once the team is laid out name by name.

06What the organism is trying to build: the hiring read

68 postings across the whole history — that's an X-ray of priorities. The signal is unambiguous: Brighty is building a regulatory-control perimeter.

Distribution by level: 21 entry-level + 15 mid-senior + 9 executive + 5 director. A "barbell": lots of junior operational roles at the bottom and a heavy executive layer at the top — the company is scaling operations and building out the top of its control functions at the same time.

★Track 2: sourcing people for their open roles

We turned the same base the other way around: not "who works for you", but "who should you hire". For the open role and the hard-to-fill ones, we sourced candidates from the professional graph — by title, geography, and current employment. Below is the pool size; the full lists with profiles are delivered as a file.

07Conclusion: what this analysis proved