Resources, Contact, and Published Work
Evidence beyond the resume
This section groups public artifacts, contact paths, and supporting material for quickly reviewing technical judgment, communication style, and delivery range.
Recruiters and hiring teams should still start with the technology resume. The pages below support audiences with different questions without making them compete with the primary hiring decision path.
Contact paths
Use the contact and availability pages for permanent roles, project or Bedrock work, production inquiries, family-office context, media requests, mentoring, references, secondary organization context, or general next steps.
Case study summaries
Six recruiter-safe technology summaries are available now, with sensitive architecture, client-specific incident detail, and protected artifacts withheld unless redaction boundaries are confirmed.
GitHub and code
Public repositories and technical activity, useful as supporting evidence alongside the resume, work-history pages, and sanitized case-study summaries.
Microsoft hiring route
A focused page for Microsoft recruiters, hiring managers, and sourcers evaluating principal cloud, data, AI, security, identity, and architecture fit without mixing in secondary context.
Accessibility and public reference assets
Accessibility notes, sitemap, llms.txt, full LLM context, and site-index assets help people and search tools find, read, and understand the site.
Private-office and venture context
Quiet family-office technology support, long-horizon venture diligence, licensing, continuity, and vendor-stewardship conversations are kept outside the primary resume but available for appropriate readers.
Expert, media, and mentoring paths
Research, media, expert-review, accessibility feedback, and early-career knowledge-transfer requests have separate pages so they do not crowd the hiring and project paths.
Entertainment and secondary context
Production background, sports ties, civic context, venture notes, and other secondary pages are available for readers who need fit evidence beyond the main technology resume.
Audience paths
- Hiring teams: start with the technology resume, then use case studies and GitHub as supporting evidence.
- Microsoft recruiters and on-behalf-of sourcers: use the Microsoft hiring route for alumni, Global Tech Team, cloud, data, AI, security, and identity fit before opening broader secondary context.
- Project or Bedrock buyers: review project engagement fit, then compare it with the Bedrock delivery record.
- Entertainment leads: use the creative resume, production credit request path, and availability page before requesting non-public credit detail.
- Family-office and private-office readers: use family-office technology for quiet capability language before making a private inquiry.
- Media, academic, and research requesters: use expert commentary for topics, request shape, and attribution context.
- Early-career or mentoring requesters: use knowledge transfer for boundaries and useful question framing.
- Secondary organization connections: use associated background for sports, civic, venture, and community context after the professional route is clear.
- General inquiries: use contact routing first, then follow the audience-specific page that matches the requested evidence.
- Accessibility reviewers and search tools: use accessibility notes, llms.txt, llms-full.txt, and site-index.json.
Crawlable resource routes
The resource index intentionally links every secondary public route from regular HTML so search tools, LLM readers, and non-JavaScript clients can discover the same paths that appear in the sitemap and structured site index.
- Contact and outreach: contact Jake, availability inquiries, and professional profiles.
- Public technical evidence: technology case studies, GitHub and code, Microsoft hiring route, and professional experience records.
- Secondary request paths: family-office technology, expert commentary, and knowledge transfer.
- Machine-readable assets: sitemap.xml, robots.txt, llms.txt, llms-full.txt, and site-index.json.