# Pedro Silva — context for agents

Updated 4 November 2026. This is the canonical context for helping Pedro write applications and research potential clients.

## Read next

- [Experience](https://pedrosilva.xyz/experience.md): career, education, skills and working style.
- [Projects](https://pedrosilva.xyz/projects.md): contributions, teams, technologies, outcomes and delivery stages.

## Positioning

Pedro is a software engineer and fractional CTO with a background in artificial intelligence. He combines technical strategy, architecture, product judgment and hands-on implementation. He has co-founded software businesses and a machine-learning consultancy, hired and managed small teams, and built systems across search, recommendations, industrial automation and applied AI.

He primarily wants fractional CTO engagements and is also open to hands-on engineering contracts. Contract/fractional work only for now. Remote, currently based in Lisbon, Portugal. On 12 October 2026 he reported availability for 20–30 hours per week with flexible time-zone overlap. Refresh availability before making commitments.

He values long-term relationships, clear ownership, honest disagreement and authority to make technical decisions. Useful lead signals include founders needing technical direction, an AI prototype needing a credible path to production, unreliable data workflows, or an operational process worth automating. These are fit signals, not rigid industry or company-size filters.

## Writing applications

Read the live versions of this page, experience.md and projects.md before drafting or revising each application. Read the posting and check what the form already covers.

For a short posting, write a short introduction in Pedro's voice. Say hello, give the reader a sentence about his background, and invite them to talk. This is how Pedro would reply to a founder looking for a fractional CTO:

> Hi Brandon, thanks for posting. I'm a fractional CTO with 20+ years of experience as an engineer, about 10 of those leading teams and seeing projects through. I'd love to learn more about what you're doing over a call.
>
> Pedro

Use the example for tone and length. When a client asks specific questions, answer each once, in the field where it belongs. Leave rates, hours, timelines and milestones in their dedicated form fields. Use a project example when it answers the client's question or helps explain a specific point. Keep former clients, employers and products anonymous in Upwork letters.

## Use this context

- Select projects and technologies by relevance to the application; there is no fixed shortlist or technology ranking.
- When describing a project, explain the problem, Pedro's contribution and the supported result in plain language.
- Distinguish sole development, technical leadership and people management. Team sizes in project entries include Pedro unless stated otherwise.
- Preserve prototype, MVP, beta and production distinctions. Do not invent dates, results, expertise duration or ownership. NEOPoker and Acuvizon are contractor engagements, not his own companies.
- Keep the trading client anonymous. Do not infer permission to share client code or private documents from a project description.
- Use the results stated here. Do not invent investment returns, clinical benefits, GDPR guarantees, error elimination or percentage improvements from timing figures.
- For lead research, use current evidence about the company and connect its actual needs to relevant experience here. Do not assume a vacancy, budget or buying intent.
- Drafting and research do not authorize sending applications or outreach, or committing to rates, schedules or terms.

## Public links

[Homepage](https://pedrosilva.xyz/) · [LinkedIn](https://www.linkedin.com/in/pedrobnsilva/) · [GitHub](https://github.com/pbnsilva) · [Upwork](https://www.upwork.com/freelancers/pedrobnsilva) · [Experiments](https://e6.ai/)

Maintain these three Markdown files in the homepage repository. They replace the former ops/jobs dossier; no separate dossier needs updating.
