Contact | Guy Romelle Magayano

Contact

Start with the role, system, or constraint.

Use this page for hiring conversations, client work, agency collaboration, or product team support. The best first message explains the context, timeline, and outcome you need.

Start

Choose the route that matches the role or constraint

The first note gets useful faster when the context already points to the kind of conversation you need.

Hiring team or recruiter

Use this path if you are evaluating me for a senior engineering role and want the fastest route to fit, availability, and relevant proof.

Talk about a role

Client or operator

Use this path if a live product, workflow, or platform constraint needs direct engineering help, clearer ownership, or a safer delivery path.

Discuss the project

Agency or delivery partner

Use this path if you already have strategy, design, or client ownership and need a senior engineer who can fit around the existing team.

Plan the collaboration

Existing product team

Use this path if your team needs architecture judgment, scoped implementation, or a second pair of hands on a high-pressure product surface.

Share the constraint

Context

Start with direct context

The useful first message usually includes the product surface, the delivery risk, what changed, and the outcome that would make the work worthwhile.

Brief

Helpful context to include

Most good first conversations get clearer faster when the first note is specific.

Hiring conversation

Share the role, team shape, work mode, timeline, and which parts of the site feel most relevant.

Existing system

Share the product surface, the delivery risk, who currently owns access, and what outcome would make the work worthwhile.

Agency or partner support

Share the client context, team shape, delivery responsibilities, and where senior implementation support would remove the most drag.

Embedded product support

Share the current roadmap pressure, the platform constraint, and whether the need is review, execution, or both.

Services

Typical service entry points

If the need already sounds commercial, these are the usual starting points before the scope gets refined.

Architecture Review

Starts at USD 1,500

A focused architecture review of the routes, workflows, and technical boundaries that are slowing delivery or hiding risk.

Technical Advisory

Starts at USD 2,400 / month

Recurring senior engineering judgment for teams that need sharper decisions around architecture, delivery, and product-system tradeoffs.

Delivery Sprint

Starts at USD 4,800

Hands-on implementation for the highest-leverage slice of work when the problem is clear and the team needs direct progress.

Links

Public proof before you write

If you want more context before reaching out, use these public surfaces first.

Work with me