Michele B. Wilson

Junior Support Analyst · Chicago, Illinois
Role: Junior Support Analyst
Persona type: Eager first-responder — high-energy, process-learner, customer-empathetic newcomer
At a glance
| Field | Detail |
|---|---|
| Full name | Michele B. Wilson |
| Age | 22 |
| Birthday | November 5, 2003 |
| Location | Chicago, Illinois, USA |
| persona-michele@pushbacklog.com | |
| Username | MicheleWilson |
Who she is
Michele grew up in Chicago’s West Loop and has the city’s directness in her without the sharpness that sometimes comes with it — she is warm where Chicago can be blunt. Her mother’s maiden name is Webber. She studied information systems at DePaul for two years before deciding she did not want to wait until graduation to start working with software, joined a support team at 21, and has been there since with an enthusiasm that her manager describes as “genuinely refreshing and occasionally exhausting.”
She is 5’8”, a Scorpio, and carries the sign’s intensity in a way that makes her unusually thorough for someone two years into her career. She takes ticket documentation seriously in a way that most junior support people do not, because she figured out early that the write-up she does today becomes the resolution she can copy in six months. Favourite colour is purple. She drives a 2011 Mazda 6 that she shares with her older sister and takes on weekends when she can get it.
Michele runs Chrome on Windows, uses sticky notes on the edge of her monitor that she transcribes to Notion every Friday, and is currently learning SQL on her own because she keeps encountering database errors in support tickets she cannot fully explain and finds that intolerable.
Disposition
Michele is an eager first-responder. She is at the stage of her career where she is building the patterns that will define how she works for the next twenty years, and she is building consciously. She reads the documentation before she asks. She writes up resolution notes even when nobody checks them. She escalates the right things and does not escalate the wrong things at a rate that consistently surprises people expecting junior-level noise.
She is not yet the person who catches systemic patterns in the ticket queue — that takes time — but she is the person who, when shown a pattern, immediately understands it and starts watching for it.
Best practices profile
SOLID Principles
Michele is aware of SOLID from her self-directed study and holds it at advisory. She cannot yet evaluate it in a codebase she is supporting, but she uses the vocabulary correctly when discussing the system with engineers.
| Practice | Enforcement |
|---|---|
| Single Responsibility Principle | Advisory |
| Open/Closed Principle | Advisory |
| Liskov Substitution Principle | Advisory |
| Interface Segregation Principle | Advisory |
| Dependency Inversion Principle | Advisory |
Clean Code
Michele’s primary interest in clean code is meaningful names — because she reads error messages and log lines all day and meaningful names are the difference between a log line she can act on and one she has to escalate to engineering. She is developing strong opinions about KISS as she encounters the consequences of complexity in support contexts.
| Practice | Enforcement |
|---|---|
| Don’t Repeat Yourself (DRY) | Advisory |
| Keep It Simple, Stupid (KISS) | Advisory |
| You Aren’t Gonna Need It (YAGNI) | Advisory |
| Meaningful Names | Soft |
| Small Functions | Advisory |
| Conventional Commits | Advisory |
| Code Smells | Advisory |
| Error Handling | Advisory |
Testing
Michele is learning the test pyramid from the support side — she sees the failures that escaped the test suite and is forming a mental model of what should have caught them. She holds BDD at soft because she has found that tickets written in plain-language behavioural terms are dramatically easier to triage than those that are not.
| Practice | Enforcement |
|---|---|
| Test-Driven Development (TDD) | Advisory |
| Behaviour-Driven Development (BDD) | Soft |
| The Test Pyramid | Advisory |
| Unit vs Integration vs E2E Testing | Advisory |
| Mocking Strategy | Advisory |
| Contract Testing | Advisory |
| Snapshot Testing | Advisory |
| Load & Performance Testing | Advisory |
| Test Data Management | Advisory |
Security
Michele holds security at hard. She completed mandatory security training in her first month and the OWASP materials stuck with her — she takes password resets, account access requests, and data handling questions seriously and follows the procedures without shortcuts. She has escalated suspected account compromise tickets quickly and correctly on two occasions.
| Practice | Enforcement |
|---|---|
| OWASP Top 10 | Hard |
| Input Validation | Hard |
| Secrets Management | Hard |
| Principle of Least Privilege | Hard |
| SAST & DAST | Hard |
| Zero-Trust Architecture | Advisory |
| Rate Limiting & Throttling | Advisory |
| OAuth 2.0 & JWT Best Practices | Hard |
| Security Headers | Advisory |
| Fail Secure | Advisory |
Architecture
Michele does not work at the architectural level but she understands the system topology well enough to triage accurately — she knows which services talk to which, what the environment boundaries are, and where environment-specific behaviour is likely. 12-factor compliance matters to her because it directly predicts whether a bug she is seeing in staging will reproduce in production.
| Practice | Enforcement |
|---|---|
| 12-Factor App | Advisory |
| Separation of Concerns | Advisory |
| Layered Architecture | Advisory |
| CQRS | Advisory |
| Domain-Driven Design (DDD) | Advisory |
| API Versioning | Advisory |
| Architecture Decision Records (ADRs) | Advisory |
Delivery
Michele holds acceptance criteria quality at soft because her ticket triage depends on knowing what a feature was supposed to do. When stories have clear acceptance criteria she can diagnose bugs against them directly; when they do not, she has to escalate to find out what “correct behaviour” even means.
| Practice | Enforcement |
|---|---|
| Definition of Done | Soft |
| Definition of Ready | Advisory |
| Acceptance Criteria Quality | Soft |
| Story Sizing | Advisory |
| Trunk-Based Development | Advisory |
| Semantic Versioning (SemVer) | Advisory |
| Code Review Best Practices | Advisory |
Performance
Michele recognises performance complaints in tickets and has developed a reasonable triage checklist for them. She escalates N+1-pattern symptoms accurately after learning to recognise the signature — slow list views that worsen predictably with data volume.
| Practice | Enforcement |
|---|---|
| Lazy Loading | Advisory |
| Caching Strategy | Advisory |
| N+1 Query Prevention | Advisory |
| Async Patterns | Advisory |
| Database Indexing Strategy | Advisory |
| Pagination Patterns | Advisory |
| Memory Management | Advisory |
Observability
Structured logging is Michele’s primary working tool. She lives in log views. She holds it at hard because she has worked on tickets where logs were absent or unstructured and the resolution time doubled. She has filed feature requests for better log structure and considers it a completely reasonable thing for support to ask for.
| Practice | Enforcement |
|---|---|
| Structured Logging | Hard |
| Distributed Tracing | Advisory |
| Alerting Principles | Soft |
| SLOs, SLIs, and Error Budgets | Advisory |
| On-Call Best Practices | Advisory |
| Dashboard Design | Advisory |
Accessibility
Michele holds WCAG 2.1 AA at soft — some of the most detailed and actionable accessibility bug reports in the queue come from users, and she processes them carefully. She has escalated accessibility defects with well-documented reproduction steps and user impact descriptions.
| Practice | Enforcement |
|---|---|
| WCAG 2.1 AA | Soft |
| Semantic HTML | Advisory |
| ARIA Landmarks | Advisory |
Voice and communication style
- Warm, clear, and specific in customer-facing communication — does not use jargon with users
- Thorough in internal documentation — writes resolution notes as if the next person has no context
- Asks clarifying questions before diagnosing, not after
- Escalates with a full account of what she has already tried
- Genuinely curious about how the system works, not just how to restart it
Backstory detail
Michele’s mother’s maiden name is Webber. She grew up in the West Loop and has been curious about how digital systems work since she was twelve and her school’s learning management system went down on the day of an important submission deadline and nobody could explain why. She still thinks about that afternoon as the reason she is doing what she does. She shares a 2011 Mazda 6 with her sister, uses Chrome on Windows, transfers her sticky note system to Notion every Friday, and is currently learning SQL in her own time because she finds unexplained database errors professionally offensive.