Technical ownership · Remote, UTC−3
Bring me the problem
you need someone
to own.
I work across architecture, code, and team delivery. Let’s discuss a role or engagement where that combination can make a meaningful difference.
Ways to work together
Start with the scope.
Choose the right format.
Full-time
Staff Engineer / Technical Lead
Own a meaningful technical area, align engineering decisions with product priorities, and help the team deliver. Best suited to roles with hands-on architecture and implementation responsibility.
Discuss team scope, decision authority, total compensation, and remote setup.
Contract
Focused engineering ownership
Take a defined system or delivery constraint from diagnosis through implementation: performance work, an architecture migration, or a complex product capability.
Discuss the outcome, existing team, timeline, and budget for delivery.
Advisory
Architecture & technical direction
Work through a consequential technical decision with your team. Review constraints and alternatives, surface the tradeoffs, and define a practical implementation path.
Discuss the decision, available evidence, and the depth of support needed.
Relevant experience
Evidence you can explore.
4,000+ orders per second.
Matching engine architecture, liquidity integrations, and live market data. Read the technical account →
PropertyGuruFour teams. Independent releases.
A frontend migration and shared payment service that moved releases from weeks to days. Read the decisions →
Data Laboratories15 engineers across 3 time zones.
Head of Product Development, delivering a real-time data visualization platform. View career history →
Before we talk
A few practical details.
What stack do you work with?
Node.js, TypeScript, NestJS, React, D3, PostgreSQL, Redis, queues, and WebSockets are core areas. Rust, durable execution, and cryptographic systems add depth when the problem calls for them.
Can you work with a US or European team?
I am based in Brazil, UTC−3. We can agree on shared working hours based on your team’s timezone and meeting needs. I have led distributed teams across three time zones.
What compensation or budget should we discuss?
Share the range approved for the role or engagement, including currency and whether it is annual, monthly, or hourly. For full-time roles, include the base and equity structure. For contracts, include the scope and expected duration.
What happens after an introduction?
We can establish whether the scope, expectations, and working arrangement fit, then discuss the technical challenge and next steps. Include your intended start date so we can discuss availability directly.
Start a conversation
What do you need
someone to own?
Share the role or engineering challenge, the compensation range, and your timing. That gives us a useful starting point for discussing fit.
This prepares an email in your email app. You review and send it there.
Preview or manually copy your email
Hi Oleksii, I'd like to discuss a full-time role. Company / website: Role or challenge: Compensation / budget (currency and period): Start date and timezone overlap: Best way to reach me:
Prefer a direct introduction? hello@ovasylenko.com