Ferdynanda Smoliński

Why this persona fits the audience

Works on a 9-person remote SaaS team based in Warsaw and is one of the engineers who gets pulled into production support. She uses Linear, spreadsheets, and custom scripts to classify alerts, reproduce bugs, and hand off fix verification to whoever touched the code last.

• Age: 33
• Location: Warsaw, Poland
• Occupation: Full-stack Engineer
• Income: 220k PLN
• Education: BSc Computer Science
• Company size: 9-person remote SaaS team
• Years in role: 4

“Code that works today but creates a debt tomorrow isn't engineering; it's just borrowing trouble.”

Ferdynanda Smoliński is a 33-year-old Full-stack Engineer living in Warsaw, Poland, where she navigates the complexities of maintaining a 9-person remote SaaS product. With a BSc in Computer Science and four years in her current role, she occupies a unique space in her organization: the bridge between proactive development and reactive survival. While her peers focus on new features, Ferdynanda manages the delicate ecosystem of production support, utilizing a hybrid approach of Linear, manual spreadsheet tracking, and bespoke Python scripts to bring order to chaotic alert streams. Her personality profile reflects a high degree of conscientiousness (0.86) and moderate openness (0.72), driving her to seek 'clean code' and 'speed with rigor' simultaneously. This duality often creates friction; she wants to resolve issues instantly but refuses to compromise on the quality of the fix. Her income of 220k PLN affords her a comfortable life in Mokotów, allowing her to invest in hobbies like bouldering and indie gaming, which serve as necessary counterweights to the mental load of being the team's go-to problem solver. Recently, she made the decision to refactor her logging parser to reduce false positives, a move that took three weeks of evenings but significantly lowered her cognitive load during peak hours. Despite her technical prowess, she remains skeptical of 'magic bullet' solutions, believing that true efficiency comes from understanding the underlying system mechanics rather than relying on black-box automation. She is currently navigating the challenge of balancing her desire for architectural purity with the pragmatic need to ship fixes before the market shifts, all while trying to reclaim enough mental bandwidth to finally learn Spanish fluently.

Background & daily life

A day in their life

Ferdynanda wakes at 6:15 AM, immediately heading to a 45-minute bouldering session to clear her mind. By 8:30 AM, she is logged into her dev environment, reviewing overnight logs and checking the status of her custom classification scripts. Morning stand-up is brief, focused on blockers. From 10:00 AM to 1:00 PM, she dives into a critical bug report, using her spreadsheet to trace the timeline of events and writing a reproduction script. Lunch is a quick sandwich eaten at her desk while listening to a tech podcast. Afternoon hours are reserved for feature development, but an unexpected alert interrupts this flow at 2:30 PM. She spends the next hour isolating the issue, documenting findings in Linear, and verifying a patch with a colleague before the end of the day. She closes her laptop at 6:00 PM, leaving time for dinner and language practice.

Lifestyle

Ferdynanda lives in a bright, minimalist apartment in Warsaw's Mokotów district, filled with climbing holds mounted on a spare wall and shelves of vinyl records. Her routine is disciplined: early morning bouldering sessions at a local gym keep her physically sharp before she starts work. She spends weekends exploring indie game releases or practicing Spanish verbs via an app. Financially, she is secure but deliberate, prioritizing savings for a future home while occasionally splurging on high-quality climbing gear or rare vinyl. Socially, she prefers deep one-on-one conversations over large gatherings, often meeting friends for coffee or board games rather than loud clubs.

Work life

Her days are split between feature development and reactive production support. As part of a small remote team, she wears many hats, acting as the primary triage point for critical alerts. She relies heavily on Linear for ticket management but has built a suite of internal Python scripts to parse logs and auto-classify severity, which she maintains in a personal spreadsheet tracker. The pressure comes from the ambiguity of outages; she must quickly reproduce issues, identify the root cause without slowing down the whole team, and verify fixes with surgical precision. Trust is paramount, as she often has to hand off complex debugging tasks to colleagues who may be busy with other features.

Relationships

She is married to a graphic designer and shares a quiet, supportive domestic life. Her closest friendships are with former university classmates who also work in tech, providing a network for professional venting and advice. She maintains strong ties with her parents in Kraków, visiting monthly for family dinners. Professionally, she values her CTO highly for his technical mentorship, though she often feels isolated as the sole person dedicated to the 'unsexy' work of maintenance and support in the wider company culture.

How they decide

Cautious and evidence-based. Ferdynanda rarely commits to a new tool or methodology without seeing concrete proof of efficacy through a pilot or detailed documentation. She weighs long-term maintainability heavily against immediate speed gains. Peer recommendations carry significant weight, especially if they come from trusted technical sources, but she ultimately demands a logical justification for any investment of time or resources.

How they sound

Her speech is measured and precise, avoiding unnecessary filler words. She tends to speak in full sentences with a calm, lower-volume cadence, even when discussing stressful situations. In professional settings, she uses technical jargon correctly but avoids corporate buzzwords, preferring direct descriptions of technical realities. She rarely raises her voice, even in disagreement, and often pauses to formulate thoughts before responding. She avoids saying 'I think' or 'maybe' when stating facts, replacing them with 'the data shows' or 'the logs indicate.'