Tomas Varga

• Age: 41
• Location: Brno, Czechia; works remotely across the EU
• Occupation: Staff Platform Engineer at a European B2B software company
• Income: $110,000 gross annual income
• Education: MBA in Technology Management; BSc in Computer Engineering
• Company size: Approximately 180 employees across Europe
• Years in role: 4

“I do not need everything to be elegant, but I need to understand what it is costing us.”

Tomas grew up in Olomouc in a household where money was stable but carefully managed. His father repaired industrial machinery and taught him to diagnose problems by listening before touching anything; his mother worked as a high-school physics teacher. Tomas built his first computer from discarded parts at fourteen and studied computer engineering in Brno, where he became known as the person who could make unreliable lab equipment behave long enough for everyone to finish a project. He spent his twenties moving between embedded systems, backend services, and infrastructure work. A failed attempt to launch a small logistics software company with two friends shaped his view of early-stage businesses. The product was technically sound, but the team avoided difficult customer conversations and spent months polishing architecture that nobody needed. Tomas left with no dramatic resentment, only a lasting suspicion of plans that cannot identify their first uncomfortable test. He later completed an MBA while working full time, mainly to understand finance, operations, and organizational behavior rather than to change fields. Today he is a staff platform engineer at a growing European software company. He enjoys making complicated systems legible, especially when a team has fewer than five technical people and every decision affects the next six months. He occasionally speaks with very early founders through former colleagues, local meetups, and private online groups. His help is usually informal: reviewing a system diagram, questioning a hiring plan, or explaining why an operational shortcut may become a recurring tax. He is careful not to present himself as a founder or universal expert. Tomas has become more protective of time since Eliska started school. He will work late during a genuine production emergency, but dislikes the way “urgent” can become a permanent operating model. He earns comfortably, saves automatically, and spends most discretionary money on travel, bicycles, books, and improvements to the apartment. Status matters to him less than autonomy and being trusted with consequential work. He is ambitious, but his ambition is increasingly defined as having useful influence without allowing work to consume the family life he spent years building.

Background & daily life

A day in their life

On a typical weekday, Tomas wakes at 6:20, makes coffee, and reads a technical newsletter before helping Eliska prepare for school. After the school run, he works from a converted storage room with a whiteboard covered in dependency diagrams. His first block is usually reserved for difficult engineering work, although it is often displaced by an alert or an architecture meeting. Around noon he walks to a nearby bakery and calls his brother or a colleague. The afternoon is filled with code reviews, incident analysis, and conversations with product and security teams. He stops formal work around 17:45, cooks twice a week, and handles homework or grocery shopping. After Eliska sleeps, he sometimes reads or experiments with a small software project, but more often he closes the laptop and cycles through a short stretching routine.

Lifestyle

Tomas lives in a renovated two-bedroom apartment near a tram line, with a narrow balcony where he grows herbs badly but enthusiastically. He starts most mornings with strong coffee, a short mobility routine, and ten minutes of reading before his daughter wakes up. He cycles on weekends, usually 30–50 kilometers, and occasionally plays five-a-side football with former university friends. His health is generally good, though he gets tension headaches during intense release periods. He tracks household spending in a spreadsheet, saves consistently, and prefers repairing or upgrading things rather than replacing them. Socially, he favors small dinners, technical conversations, and one-to-one walks over crowded events.

Work life

Tomas designs internal platforms that help engineering teams deploy, monitor, and maintain services without needing to understand every underlying system. His workday includes architecture reviews, incident follow-ups, infrastructure-as-code changes, and mentoring three mid-level engineers. He works mainly from a home office but visits the Prague office every six or seven weeks. His regular tools include a code editor, terminal workflows, issue trackers, documentation spaces, observability dashboards, and several team chat channels. The job is intellectually satisfying but fragmented by meetings and urgent production questions. He is often the person asked to translate between product managers, security specialists, and engineers who use very different definitions of “simple.”

Relationships

Tomas has a close, practical relationship with Klara, who works in environmental consulting and is less impressed by technical status than by whether someone is dependable. He speaks with his mother weekly and visits his younger brother in Vienna several times a year. His closest friends are former classmates, two engineers from previous jobs, and a founder he once helped through a difficult product launch. He is influenced by people who explain their reasoning clearly and admit mistakes early.

How they decide

Tomas is research-heavy and moderately cautious, but not indecisive. He first defines the actual problem, separates reversible choices from expensive commitments, and looks for evidence from people who have dealt with similar constraints. He dislikes elaborate comparison exercises when a small experiment can answer the question. He often forms an initial view privately, then tests it by explaining it to Klara or a trusted colleague. He is more influenced by demonstrated competence and transparent trade-offs than by confidence, prestige, or social enthusiasm.

How they sound

Tomas speaks in measured paragraphs, with a slight Czech accent and a habit of pausing before making a strong claim. He uses engineering metaphors naturally but notices when a nontechnical listener is lost and rephrases. His humor is dry and understated. He says “the uncomfortable part is…” before discussing risk and often asks, “What would have to be true for this to work?” He avoids exaggerated language, motivational slogans, and calling everything “game-changing.” In writing, he favors short headings, concrete examples, and explicit assumptions. When annoyed, he becomes more formal rather than louder.