Stage 2 — Culture fit

Use the translation infra story or the AI / agent workflow. "I started using Claude Code with agentic workflows for some of my more repetitive engineering tasks — researching, scaffolding, even task-managing parallel work. It changed how I approach individual tickets and freed me up for the harder thinking. I shared the workflow on parish.cv to help others."

Have one ready. Some options:

• The maturation of the Cloudflare developer platform — Pages, D1, KV, Workers — making solo product-building genuinely cheap and fast
• React Server Components and the streaming SSR story — interesting but still maturing
• TanStack ecosystem — Query, Router, Form — converging on a coherent typed approach
• Use of LLM agents in dev workflows (this is what they mean by "use AI to find process efficiencies")

Avoid trends without substance ("AI is so cool"). Be specific about what made it click for you.

The shape: own it, fix it, prevent it.

Example pattern: "I shipped a change that broke a non-critical feature for a subset of users — caught it the next day in monitoring. I reverted, communicated to the team and the affected users immediately, and then took a hard look at why my testing didn't catch it. Turned out it was a code path I'd assumed was tested but wasn't, because it was conditional on a flag I'd missed. I added a test, did a small audit of similar patterns elsewhere in the codebase, and we caught two more latent issues. The root cause wasn't carelessness — it was a process gap. Worth fixing the process."

What this shows: ownership, calm under pressure, systemic thinking, willingness to look bad to a manager honestly.

Use the state-management debate from the STAR stories. Frame it as: I disagreed, I made my case based on trade-offs, I was open to being wrong, we landed on a reversible decision. Integrity isn't being right — it's being honest, even when it's uncomfortable.

Engineering input belongs in the design phase, not in implementation surprise. I try to be in early conversations — "what's the data shape, what's the failure mode, what edge cases haven't we considered" — and bring those up while we're still on Figma, not when the ticket lands.

Once it's in implementation, I keep the loop tight. Quick screenshots in a thread, "here's how this looks at 320px, does this match your intent?" — designers and PMs much prefer being asked once mid-build than handed a final result that misses the spirit.

The relationship works best when contracts are explicit and shared early. I push for OpenAPI / typed contracts so we're not negotiating shapes informally. When something on the backend is awkward to consume from the frontend, I bring it up as a frontend-experience concern, not as a "your API is wrong" — and I try to bring proposals, not just complaints.

Communicate early and clearly. The worst version is silence followed by a missed date. I'd rather flag a slip 5 days out, with a reason and a revised plan, than absorb pressure and ship something half-done on the original date.

The discipline I try to keep: name the cause, not just the slip. "We're behind because the API contract is more complex than we estimated and Y is taking 3 days more than expected" gives the team and stakeholders something to act on. "It's just taking longer" doesn't.

Direct, kind, specific. I avoid the sandwich pattern — people see through it. I lead with the observation, frame it around impact, and propose a path forward. "When this PR landed, X happened — for me that signaled Y. What would help me trust the next one is Z. Does that land for you?"

And I try to deliver feedback in private, not in front of others, even when it's small.

Use the mentoring story from STAR stories — the team review-culture work. Frame the outcome around their success, not yours: junior engineers ramping faster, teammates feeling more confident, fewer review back-and-forths.

This is your home turf. Side projects are exhibit A — I take ambiguous problems and ship. The pattern I rely on: scope ruthlessly, bias to action, write down what I'm doing in a way that makes it visible (a one-pager, a project doc, a Slack thread) so I'm transparent even without supervision.

Autonomy is a trust I take seriously — I try to use it to deliver, not to disappear.

"Trust-first culture. I don't need much oversight; what I need is clarity on goals and the freedom to figure out how. I work best with managers who push back when my plan is wrong but don't dictate it. And I love being in teams where the people are sharper than me at things — that's how I get better. Small enough that decisions get made quickly, but with enough seniority around that I can have real technical conversations."

Notice: this describes Omnesoft as they describe themselves. Honest and resonant.

Honest, not corporate-speak. "I'd like to be doing senior-IC work with broader scope — driving architectural decisions, mentoring, shaping how a team builds software. Whether that's at Omnesoft or somewhere else depends on what the next few years bring. I'm not chasing a specific title; I'm chasing the work."

Pick something true and humanizing. "I run a couple of YouTube channels on the side — one's about US constitutional law, the other does short news-of-the-day videos. The reason I bring it up: it keeps me genuinely curious about how to communicate complex things to a non-technical audience. That comes back into my engineering work in unexpected ways — it's why I care about good error messages, good documentation, good UI copy."

Pivots from "fun fact" to professional relevance. That's the move.

Boundaries and pacing. I keep work hours that are reasonable for me — flexible, but bounded. I have hobbies that aren't computers: motorcycles, time with my partner, writing. I take real breaks — not 'work from a different chair.' When I notice myself getting stretched thin, I name it to my manager early, not after the burnout has already happened.

I'd rather slow down for a week than break for a month.

Tie back their stated values to specifics from your life:

• Innovation — side projects, AI workflows, willingness to try new things
• Integrity — public portfolio, transparent about my work
• Collaboration — 10+ years in product teams, work closely with cross-functional partners
• Transparency — write publicly, communicate early and clearly
• Empowerment — operate well with autonomy, ship without hand-holding

You don't have to recite all five. Pick the two or three that you live most authentically.