Contact — Written first

Start with writing.

To keep the first step focused on technical alignment rather than scheduling overhead, I start with a structured email. If your team has a challenging data, statistical, or machine learning problem, send enough context for me to assess whether I can help.

The fastest way

Send an email

No contact forms, no chat widgets. A real email is enough, and I reply directly, usually within one business day.

Email

Availability

Booking Q4 2026 — Selectively

Based in

Taiwan — Working Globally

In the first email

Five things that help me reply quickly.

  1. 01

    The situation, briefly

    Two or three sentences on what's happening. Context matters more than polish.

  2. 02

    The decision on the table

    What are you trying to decide, and by when? This is often the most useful line in the email.

  3. 03

    Constraints & evidence

    Data state, infrastructure reality, team size, timeline, and a budget range. Pragmatic constraints lead to pragmatic solutions.

  4. 04

    Who you are

    Your role, the company, and the stage of the business. A link to your product or website is sufficient.

  5. 05

    How you found me

    Referral, article, search, or introduction. It helps me understand the context for a potential collaboration.

Common questions

Before you write.

What happens after I send my email?
I will review your message and reply within one business day. If there is potential alignment, we will begin with a structured email exchange to clarify the technical details, constraints, and scope of your problem. If the fit still looks strong, we can discuss a Paid Test Run — a small, bounded piece of real work that lets both sides evaluate the collaboration on actual code, data, or systems.
What if there's no alignment?
I will let you know directly and, if possible, recommend alternative specialists or open-source resources. Being transparent about fit saves us both time.
Do you sign NDAs?
Yes, I am happy to sign a standard mutual NDA before we discuss any proprietary data or systems.
What if my budget is smaller than your typical engagement?
Let me know anyway. If the problem is technically interesting but the scale doesn't fit my typical model, I am glad to make introductions to senior independent practitioners in my network.
How do we handle time zone differences?
I operate from Taiwan and collaborate regularly with teams in North America and Europe. Because my workflow is async-first — built around structured written updates, GitHub issues, and detailed technical documentation — time zone differences rarely cause friction.
How do you integrate with our existing engineering team?
I work as an independent, high-leverage contributor rather than an embedded employee. I do not join daily stand-ups or internal rituals unrelated to the technical work. Instead, I interface directly with your technical lead or CTO through async Slack threads, code reviews, and technical memos, delivering clean software abstractions your team can maintain.
What do your final deliverables look like?
I deliver production-ready code repositories, rigorous evaluation pipelines, and a comprehensive architectural memo. I do not deliver high-level slide decks or unmaintainable proof-of-concept scripts. Everything is built to be readable, thoroughly documented, and ready for your team to run.
Who owns the intellectual property?
You do. Once invoices for a completed phase are settled, all custom code, model architectures, weights, and documentation developed specifically for your project belong entirely to your organization.

Otherwise

If this isn't the right fit, I'm glad to point you toward someone who is.

Just let me know in the first line of your email.