Skip to main content
Joey Z.

Work With Me

This page does one thing: help you quickly evaluate whether we are a good fit.

Collaboration Models

Role Collaboration

Join as a senior frontend/full-stack contributor for medium to long-term product building.

Case-based Delivery

Deliver a scoped module, architecture upgrade, or performance optimization initiative.

Advisory Session

Provide technical diagnosis and implementation guidance for difficult engineering problems.

Good Fit Signals

  • • You value long-term maintainability, not just quick patching.
  • • Your team needs a reliable engineer to own ambiguous, complex modules.
  • • You prefer transparent communication and documented decisions.

Collaboration Process

  1. Align context and expected outcomes
  2. Define scope, constraints, and ownership boundaries
  3. Execute in visible milestones with regular updates
  4. Review outcomes and capture reusable learnings

Default Working Agreement

  • • We start with clear outcomes and boundaries, not ambiguous execution.
  • • Cadence is usually weekly, with visible updates at key checkpoints.
  • • Documentation and decision logs are prioritized to reduce rework.

Payment Terms

40%

Upfront

40%

Mid Review

20%

Completion

FAQ

Payment terms?

40% upfront, 40% at mid-point review, 20% upon completion.

Do you only do project-based work?

No. Role collaboration and long-term engineering participation are both welcome.

What should I send before the first discussion?

A short context summary, desired outcome, timeline, and current blockers are enough to start.

Can we start with a small scope first?

Yes. A small pilot is often the fastest way to validate collaboration fit.

Next Step

If this direction fits, use the contact card below and send a short context brief.

Contact

Open to role opportunities, scoped collaboration, and engineering discussions.

  • Email******
  • WeChat******
  • Telegram******