Technical direction
Turn rough requirements into a concrete plan: what to build, how to structure it, and which decisions need to be made up front.
Clear communication and regular updates in plain English.
Turn rough requirements into a concrete plan: what to build, how to structure it, and which decisions need to be made up front.
Identify what could slow down delivery, clarify tradeoffs, and break the scope into tasks with realistic estimates.
Pair with developers, run thorough reviews, and set team conventions to keep the codebase maintainable.
Remove blockers with quick calls, take ownership of the hard parts, and keep frontend-backend integration on track.
Ongoing support billed monthly, with reserved capacity.
Flexible hours with occasional late-evening availability.
US time zones are possible with partial overlap.
Resolve open questions early on.
Keep PMs in the loop with brief updates and ticket summaries.
Jump on short calls when needed.
Step in where it's needed.
Coordinate the work and drive it to completion.