Jessica Carter
Profile
Jessica Carter, J.D. — I build reliable systems, solve ugly problems, and communicate clearly with both technical teams and business stakeholders. My background spans advanced technical support, infrastructure and operations, and legal/organizational leadership.
Solutions Engineer · Sales Engineer · Technical Account Manager · Customer Success Engineering · Implementation / Onboarding · Technical Program Management
- Customer-facing technical execution: translating complex systems into outcomes, fast.
- Systems troubleshooting: storage/virtualization/networking stacks, incident-style problem solving, and crisp root-cause writeups.
- Cross-functional leadership: aligning priorities, clarifying decisions, and shipping improvements without drama.
- Operational discipline: documentation, process design, and building automation that actually runs.
- Synology: advanced support across storage, virtualization, and networking in high-stakes customer environments.
- Founder, law firm: built and ran a practice with real-world accountability: client outcomes, business ops, and team development.
- Long-running technical services work: hands-on troubleshooting + consulting for small-business environments.
J.D., Thomas R. Kline School of Law at Drexel University · B.A. Philosophy (minor: Classics), Central Washington University
Email: Jess@JessCarter.me · LinkedIn: jesscartertech
How I work
I’m a systems-level thinker with a bias toward shipping. I like clear specs, explicit tradeoffs, and reliability over vibes.
- Structured execution: I break big ambiguous problems into phases, deliver working slices, and keep documentation current.
- Adversarial stress-testing: I ask “how will this fail?” early — then build guardrails and rollback paths.
- Cross-domain translation: I can talk to engineers, operators, and leadership without losing the plot.
- Human-in-the-loop when it matters: automation is only good if it degrades gracefully.
Prose selections
Within a few hours, I had a response from a potential client seeking a divorce. We scheduled a meeting for the next day while I would be at work. I was genuinely surprised with the speed and efficacy of this ad campaign, and already had another two meetings in the pipeline by the time I went to bed. Friday morning came, and I took the train to work, just as I usually did. I putzed around the office for a bit, getting some medical records sorted and chatting with my friends as usual. My potential client arrived with a partner and we proceeded to the conference room to chat.
I had so many fun experiences in that car. Driving to Wenatchee to visit my biological father without directions, figuring that all the highways said either “East” or “West” and that I could figure out how to get there (this was before smartphones and GPS, and I wound up getting lost in a blizzard). Or those times I was going 45mph down Bombing Range Road (like everyone does) and got pulled over by the same rookie cop six times because I was the dork driving the shitbox. Or telling that same pig to give me a damn ticket already and quit wasting my time when he pulled me over a seventh time (he did give me a ticket, then never bothered me again).
Tom Kha is a Thai soup, comparable in some ways to an American chicken noodle soup, but without the noodles. Savory, sweet, and wholesome, it evokes the feeling of sitting by a warm hearth in the dead of winter. Its richness and complexity contrasts with the zing of fresh lime and chopped coriander. The fire of the peppers, the coolness of the Galangal, everything about the dish invites comparison and comfort. And this, I decided, would be the dish I decided to learn to cook first. Because now that I would be cooking for myself, I wanted to make good on my Freshman vow to never be famished again.