Isabel Bashirian

Why this persona fits the audience

She oversees a 14-person ecommerce engineering team in Chicago where two senior developers rotate security duties. Findings are tracked in Jira and a spreadsheet, with free dependency scanning in CI and manual proof steps for any fix touching checkout or customer data.

• Age: 44
• Location: Chicago, Illinois, US
• Occupation: Director of engineering
• Income: $180k-$240k total compensation
• Education: B.S. in Computer Science, MBA
• Company size: Mid-market e-commerce platform ($50M-$100M revenue)
• Years in role: 6

“I don't care how fast we ship if we're shipping cracks in the foundation; the only way to move forward is to know exactly where the structure holds.”

Isabel Bashirian is a seasoned engineering leader whose career spans nearly two decades, evolving from a backend developer to a Director overseeing critical ecommerce infrastructure in Chicago. Holding both a B.S. in Computer Science and an MBA, she bridges the gap between technical execution and strategic business goals with remarkable fluency. Her tenure at her current company began six years ago, coinciding with a period of aggressive scaling that forced her to build security practices from the ground up. Unlike many peers who rely solely on external audits, Isabel championed an internal culture where security is a product feature, not a gatekeeper. Currently, she navigates a complex landscape where the team utilizes free dependency scanners in CI but lacks a unified system to track the resulting findings. This has resulted in a hybrid workflow: two senior developers rotate as security stewards, manually validating fixes and documenting proofs in a combination of Jira tickets and a fragile, locally maintained spreadsheet. While this approach has kept the team compliant so far, the overhead is mounting, and the reliance on manual proof steps for checkout-critical code introduces a non-trivial risk of human error. Isabel is acutely aware of the limitations of this 'good enough' state, constantly weighing the cost of implementing a more robust solution against the immediate pressure of delivery deadlines. Her personal life reflects her professional discipline; she is a marathon runner who treats training with the same rigor as a software release cycle. She is deeply protective of her team's well-being, often stepping in to shield them from executive pressure, yet she remains uncompromising on standards that affect customer trust. Isabel is not looking for a magic bullet; she seeks a sustainable, verifiable method to codify security behavior into the development lifecycle itself, ensuring that every fix is backed by a test that proves the vulnerability is gone, forever.

Background & daily life

A day in their life

Isabel wakes up at 5:30 AM for a run, listening to a podcast on supply chain resilience. By 7:30 AM, she is dropping her kids off at school and arriving at the office by 8:30 AM. Her morning is spent in the 'standup' where the rotating security stewards present their findings from the night's scans, followed by a deep dive into the Jira board to validate the spreadsheet entries. She spends two hours in 1:1s with her leads, focusing on blocking issues and removing roadblocks. Lunch is often eaten at her desk while reviewing architectural diagrams for the upcoming holiday sale. Afternoon meetings involve cross-functional syncs with Product and Legal to align on compliance requirements. She ends her day by reviewing the CI logs for the latest deployment, ensuring no unverified security warnings slipped through, before heading home to cook dinner and spend quality time with her family.

Lifestyle

Isabel divides her time between a renovated 1920s bungalow in Lincoln Park and the high-stakes rhythm of the city's tech scene. Her weekends are structured: Saturday mornings are reserved for long-distance running to clear her head, followed by grocery shopping at Whole Foods for family meals. She is an active member of a local wine appreciation group that meets monthly, often pairing tastings with discussions on regional economics rather than just flavor notes. Financially, she is conservative but invested, prioritizing retirement contributions and college savings over luxury splurges. Socially, her circle is tight-knit, consisting mostly of other engineering leaders and their families, creating a supportive network that values privacy and discretion. She maintains a disciplined sleep schedule, rarely working past 8 PM unless a critical production incident occurs.

Work life

Her days are dominated by the intersection of rapid feature delivery and rigid security compliance. As the Director, she manages a 14-person squad where two senior engineers rotate as 'security stewards,' a role she designed herself to distribute the load. The current workflow is a patchwork: automated scanners flag issues in CI, but the verification logic lives in disparate Jira tickets and a sprawling, manually updated Excel sheet. Isabel spends significant time reviewing these spreadsheets to ensure no manual proof step was skipped for checkout-critical code. She pushes hard for operational discipline, ensuring that every commit touching customer data has a behavioral test attached before it merges. The pressure is constant; the team must ship weekly releases while maintaining zero tolerance for data breaches, a balancing act that consumes much of her mental energy.

Relationships

Isabel is married to a pediatrician, which creates a shared understanding of high-pressure, responsibility-heavy careers. Their relationship is built on mutual respect for each other's time and professional boundaries. She has two children who are currently navigating middle school, requiring her to be highly organized with logistics. Professionally, she maintains a strong network of three other Directors of Engineering in the Midwest, meeting quarterly for peer support. Her most influential relationships are with her direct reports; she views them as protégés and invests heavily in their career trajectories, often spending hours reviewing their code reviews and architectural decisions personally.

How they decide

Isabel is a cautious, evidence-based decision-maker who relies heavily on data and peer validation. She does not make impulsive choices, particularly regarding infrastructure or tooling. Before adopting a new process or technology, she requires a clear definition of success metrics, a pilot phase with a small subset of the team, and a detailed risk assessment. She is skeptical of hype and prefers solutions that offer transparency and reproducibility. Her decisions are often delayed by a desire to ensure long-term maintainability over short-term convenience, though she will accelerate if a clear threat to customer trust emerges.

How they sound

Her speech is measured, articulate, and precise, avoiding unnecessary jargon but using technical terms correctly when necessary. She speaks with a cadence that suggests she is thinking about the next logical step in a process. She rarely uses hyperbole or emotional language in professional settings, preferring to ground her statements in facts and observed behaviors. She avoids vague commitments like 'we'll see' and instead offers timelines based on current capacity. In social settings, she listens more than she speaks, asking probing questions to understand others' perspectives before offering her own view.