Availability Inquiries

Make the first message useful

For recruiting, consulting, production, private-office, expert-commentary, or mentoring inquiries, include enough context to determine fit quickly.

Jake is open to full-time, contract, fractional, and selective advisory engagements. Remote or hybrid work is preferred; travel up to 50% is workable. Relocation can be considered with assistance. International opportunities are appropriate when the organization is U.S.-based or U.S.-headquartered.

Permanent technology roles remain the highest-priority conversation for hiring teams. Project, production, family-office, media, and mentoring requests are welcome when they include clear context, but they should not replace the resume-first starting point for recruiters.

Helpful details to include

• Role type or project type.
• Expected timeline and urgency.
• Remote, hybrid, travel, venue, or on-site requirements.
• Technical environment, production environment, or stakeholder context.
• Whether the need is full-time, contract, fractional, advisory, or project-based.
• Whether the conversation involves private-office technology, expert contribution, media context, or mentoring.
• Whether non-public supporting facts are needed, such as production credits, references, family-office context, client architecture, or deeper case-study evidence.
• Any confidentiality constraints that affect what can be discussed before an NDA.

Audience-specific first messages

• Permanent roles: subject “Permanent technology role inquiry”; include title, level, reporting line, compensation range if available, remote / hybrid / relocation expectations, and interview process.
• Microsoft roles: subject “Microsoft principal role inquiry”; include the Microsoft team or hiring lane, role family, level, reporting line, compensation range if available, Redmond hybrid / remote expectations, travel needs, and whether the evaluation is direct Microsoft recruiting or on-behalf-of sourcing.
• Project or Bedrock: subject “Project or Bedrock engagement inquiry”; include the problem, desired output, technical environment, stakeholders, urgency, and whether the work is advisory, fractional, implementation, or recovery.
• Entertainment: subject “Entertainment production inquiry”; include production type, dates, venue or tour expectations, role needed, and whether the request is technical direction, stage management, venue technology, lighting, sound, or systems consulting.
• Family office: subject “Family-office technology inquiry”; include confidentiality expectations, decision timeline, participants, and whether the need is operational support, diligence, licensing, continuity, vendor stewardship, or advisory review.
• Media or expert context: subject “Expert commentary or media inquiry”; include topic, publication or institution, deadline, desired format, attribution requirements, and background / quote / interview expectations.
• Mentoring: subject “Mentoring or knowledge-transfer question”; include the specific decision or topic, what you have already tried or read, and the kind of answer that would help.
• General inquiries: subject “General professional inquiry”; include the audience, requested next step, deadline if any, and which public page prompted the message.
• Secondary organization context: subject “Associated background inquiry”; include the organization or shared context, the professional reason for asking, and whether the answer can stay shareable.

Entertainment resume request path

Entertainment and venue leads should request the separate production resume or cleared credit packet by naming the production type, dates, venue, role, expected responsibilities, travel or on-site needs, and whether individual credits, references, or equipment / systems detail are required. Public pages stay high-level until the purpose and audience for deeper credits are clear.

Regions and engagement shape

• Primary markets: Los Angeles metro, Detroit / Metro Detroit, and fully remote work.
• Secondary markets: other U.S. regions with relocation assistance.
• Microsoft-specific fit: full-time roles are preferred; Redmond hybrid, remote or hybrid, and travel-heavy roles are workable when the scope fits principal cloud, data, AI, security, identity, or architecture work.
• Compensation discussions should reflect senior/principal-level scope, depth of experience, and project or fractional structures when applicable.