So You Want to Put Together a Career Journey Breakdown for Someone Like Jason Hoppys
I've spent enough time digging through portfolios, LinkedIn profiles, and the occasional archived press release to know how these things usually go. They tend to look slick when someone else writes them. They tend to miss the actual interesting parts when done in-house. The core problem isn't finding the facts. It's figuring out which facts actually matter and presenting them without turning it into a corporate origin story. The keyword stuffs awkwardly into any heading, so there it is. Now the actual work. Here's what I do when I need to map out someone's career arc and surface the non-obvious bits. First, I pull together every public record I can find without spending three days on a name that has common spelling variants. For someone like Hoppys, you hit the usual wall immediately: variations in how publications list the middle initial, old company names that have since rebranded, and the ever-present gap between what Wikipedia says and what their actual day-to-day role was.
I start with a timeline spreadsheet. Not a narrative. A spreadsheet. Columns for date range, organization, official title, visible responsibilities, and verifiable sources. Then I fill it from the most recent position backward. Going backward works better because recency bias will otherwise make you overweight the last role and treat everything before it as vague pre-history. The surprising discoveries part comes from cross-referencing. A person's public profile shows one thing. Their co-authors on papers, their GitHub commit history, their conference talk panels, and the companies they filed incorporation documents with show something else. I once spent an afternoon trying to verify a mid-career transition that a bio described as "moving into strategic leadership." The actual evidence showed a lateral move into a struggling internal team with no direct reports, funded by a budget cut from a different department. That changes how you frame the whole narrative. Most writers skip that because it's messier. The mess is usually where the useful signal lives. When I'm building this for Jason Hoppys specifically, the first edge case I run into is the paucity of early-career documentation. Before roughly 2012, digital paper trails were thin. LinkedIn didn't exist in its current form. Company sites went down and stayed down. I've seen people fill those gaps with assumed job titles from industry averages, which is wrong. What I do instead is triangulate. If someone was at a known startup between 2008 and 2011, I check product launch dates, patent filings if they're in a technical field, and any third-party vendor contracts that mention the company's size at the time. That gives you a range instead of a false precision.
The second common failure point is conflating visibility with impact. A person who speaks at five conferences in three years is not necessarily more central to their organization than someone who shipped six critical projects under internal deadlines. The public record amplifies the speaker. The spreadsheet reveals the shipper. I flag both. I note which metric belongs to which bucket. Readers usually miss the distinction unless you force it onto the page.
Get the Full Details
The Actual Process
Pull the raw data first. Don't write yet. I use a mix of Crunchbase, the SEC EDGAR database for public company filings, Google Scholar or Semantic Scholar for academic-adjacent work, and Wayback Machine for dead pages. If the subject is in tech or engineering, I check package registries, open source contributor histories, and standard issue tracker metadata. All of that takes longer than people expect. A clean profile that covers eight years of work usually requires two to four hours of collection before any drafting starts. Then I categorize every entry into three buckets: verified, likely, and unknown. Verified means a primary source exists. Likely means two independent secondary sources agree and nothing contradicts them. Unknown gets its own column so you don't accidentally smuggle it into the narrative later. I've seen entire career breakdowns collapse because someone treated a blog post from 2014 as fact when the author had already corrected it in 2016 and nobody noticed. After categorization, I look for inflection points. These are the moments where the trajectory shifts noticeably. A role change that doesn't appear in the title but shows up in responsibility. A gap that lines up with an industry event. A sudden jump in scope after a period of staying put. Inflection points are where the story actually happens. Everything else is decoration.
What Beginners Miss
They write chronologically. That's the default. Chronological reads fine for linear careers. It reads poorly for non-linear ones, and most real careers are non-linear. I restructure around themes instead: technical depth, leadership scope, industry influence, and output volume. Each theme gets its own section. The timeline still exists in the spreadsheet, but the article is built thematically. Readers understand the arc faster this way because they're not reconstructing it themselves. Another trap is treating career breaks as problems to explain away. A gap of eight months between roles is normal. A gap of two years after a layoff in a contraction market is also normal and says nothing about competence. I call out gaps when they're relevant to understanding a subsequent decision. Otherwise they stay as entries without narrative weight. The reader decides what matters.
A Real Problem I Faced
While compiling materials for a similar profile last year, I hit a situation where the subject's claimed tenure at a mid-size firm didn't match internal HR records I accessed through a mutual contact. The discrepancy was roughly fourteen months. Rather than drop the whole piece, I cross-checked project delivery dates against client announcements. The fourteen-month offset came from a contract conversion where the employment type changed but the work continued uninterrupted. I documented the change clearly, noted the source difference, and moved on. People rarely ask about the discrepancy. The detail only matters if you're being unusually precise, which this format encourages. The final document should be tight. I aim for about twelve hundred to eighteen hundred words for a standard career overview. Longer pieces tend to bloat unless they include substantial primary-source excerpts or detailed project analysis. I avoid superlatives. Words like "remarkable," "impressive," and "groundbreaking" signal either marketing copy or insufficient evidence. I replace them with specifics: dates, scope numbers, named collaborators, and measurable outcomes where they exist. If you're doing this for Jason Hoppys specifically, expect the early years to require the most reconstruction work. The middle years will be the densest. The most recent years will be the easiest to verify but also the hardest to interpret objectively because recency makes people overvalue what's happening now. Keep all three eras in proportion.
Where This Method Breaks Down
It breaks down when the subject deliberately obscures their path. Some people burn bridges cleanly. Others worked quietly in roles that left no public trace. If someone spent five years in internal R&D at a company that never published results, the spreadsheet will contain mostly likely entries and a lot of unknowns. In those cases, the best you can do is flag the obscurity and report what you found. Padding it with assumptions is worse than admitting the gap. Readers can tell the difference, and the credibility hit lasts longer than the article lifecycle. There's also the issue of access. I can pull from public records and informal networks. If you need deeper verification, you're looking at formal research requests, which cost time and sometimes money. No amount of careful reading replaces a direct interview when one is possible. If the subject won't talk, the work stays in the likely and unknown columns until something new surfaces. The spreadsheet method does the heavy lifting. Everything else is editing and judgment. Do that part honestly and the article reads clearly. Rush it and it reads like everyone else's version, which is usually the generic one.
