This is a Persona.bio — a short guide to how someone likes to work. What's this?
Build mine →Jordan Patel
Persona at /p/jordan-patel-developer view as markdown
How do you handle disagreement?
Collaboration
I will push back hard on ideas, then commit once the call is made. Debate does not bother me. Hidden disagreement does. If I get unusually quiet, it usually means I think we are arguing from different facts.
When you disagree with a teammate on a decision, how do you typically engage? For example: - I'll push back in the meeting and argue it out - I prefer to raise concerns in writing afterward - I'll disagree and commit once the call is made - I tend to go quiet and need to be asked directly - I like a decision-maker named so debate doesn't drag
When are your peak deep-work hours?
Work Preferences
My best deep-work window is roughly 9:30am to noon. If a meeting lands there, I can do it, but you are trading away the part of the day when I can hold a whole system in my head.
Most people have one or two hours of the day when they do their sharpest thinking. When are yours, and what should teammates avoid scheduling during that window?
What are your core areas of domain expertise?
Skills
Backend systems, debugging ugly production issues, API design, and making a messy codebase legible again. I am also the person people bring weird caching bugs to.
What subject areas do you know deeply enough that teammates could bring questions to you? This can be technical (distributed systems, React, Postgres internals), domain (healthcare billing, ad auctions, logistics), or functional (hiring, incident response, design systems).
What kind of review is most helpful to you?
Collaboration
The most helpful review is honest about risk and clear about severity. Tell me what blocks approval, what is a preference, and what can be a follow-up. I would rather get one sharp comment than twenty vague ones.
Think code review, design review, writing review, or any kind of work review. What makes feedback useful instead of frustrating? For example: - Catch every detail, even small things - Focus on big-picture risks, not nits - Leave async comments first, then talk live if needed - I prefer a quick walkthrough together - Tell me what is blocking approval versus what is optional
When you say something is done, what do you usually mean?
Collaboration
Done means tested, reviewed, observable, and documented enough that the next person is not reverse-engineering my intent from commit messages.
"Done" can mean very different things to different people. What do you usually include before you feel comfortable calling work complete? For example: tested, documented, reviewed, communicated, polished, or shipped with follow-up work clearly tracked.
If you had to describe your work personality in a few plain-language traits, what would they be?
Personal Traits
Analytical, steady, dry sense of humor, and usually the least panicked person in the incident channel.
Without worrying about official test language, what traits best describe how you tend to show up at work? For example: highly organized, very curious, calm under pressure, skeptical, warm, fast-moving, detail-oriented, novelty-seeking, or consensus-driven.
What is the most effective way to convince you to change your mind?
Working Styles
Show me concrete evidence. A failing example, a trace, a prototype, or a cleaner mental model will change my mind faster than confidence ever will.
When someone disagrees with you, what kind of approach or evidence is most likely to win you over? For example: "Show me the data," or "Give me a working prototype," or "Write out the logic in a doc so I can read it."
Are you a verbal or written processor?
Working Styles
I am mostly a written processor. If the problem is messy, give me a doc or a whiteboard I can turn into a doc. Talking helps, but only after I have had a chance to structure the problem.
If you're stuck on a hard problem, do you need to talk it out on a whiteboard/call, or write it out in a quiet document?
Like this? Build yours in 5 minutes.
Free, no credit card. Sign in with Google, answer a few starter questions, share your link.