Staff keep retyping the same information
Forms, spreadsheets, email and business software are moving the same data around by hand. Aaryn can map the workflow and determine whether an automation or integration would actually save useful time.
PRINCIPAL ENGINEER + LONDON LEAD · LONDON, ONTARIO
Aaryn Biro is Second Coat's software engineer in London, Ontario.
Aaryn takes technical ownership when a business problem goes beyond a conventional website: repetitive workflows, disconnected systems, internal tools, backend infrastructure and custom software that needs an engineer to work out the real requirement before building anything.
ENGINEERING, WITHOUT THE HANDOFF CHAIN
The person in the first technical conversation stays responsible for the work.
Aaryn earned a Bachelor of Engineering Science in Software Engineering from Western University in 2020. His program covered software architecture and design, algorithms and data structures, object-oriented programming, databases, web technologies, testing and quality assurance, requirements engineering and project management.
Professionally, he has worked as a full-stack and software engineer with realxdata GmbH, Neurolign Technologies and Snappy, building and maintaining production web applications, backend systems, customer-facing features and internal product capabilities.
He is also Founder and Principal Engineer of PixelEnhance Labs and Xcelsior. That work reaches into AI media-processing pipelines, cloud infrastructure, billing, containerized GPU workloads, distributed scheduling, observability, security and developer tooling. The useful part for a Second Coat client is not the list of technologies. It is that Aaryn is comfortable taking an unclear technical problem, finding the real constraint and owning the solution through deployment.
THE PROBLEMS THAT FIT
Look for expensive repetition, awkward handoffs and software your staff are compensating for.
The best first engineering projects usually have a business symptom before they have a technical name.
Two systems should talk to each other
The business already owns the tools, but the handoff between them is manual or unreliable. If supported APIs or integration methods exist, Aaryn can design the connection around the real process.
The spreadsheet has become the system
A spreadsheet can be the right tool for years. When permissions, errors, duplicated versions or complicated handoffs start costing more than the simplicity is saving, an internal tool may be worth examining.
The missing tool does not exist
Some requirements are specific enough that another subscription is not the answer. Aaryn can scope a purpose-built internal application, backend service or custom workflow when the economics justify it.
A technical product needs ownership
Startups and growing businesses sometimes need backend architecture, APIs, infrastructure, payments, data systems or deployment work without hiring a large outside development team.
The problem is still badly defined
You do not need to arrive with a specification. Requirements gathering is part of the engineering work. Aaryn can sit with the people who use the process, understand what is failing and turn that into a practical technical plan.
LONDON, ONTARIO
A real local technical contact, not a city name added to a footer.
Aaryn moved to London in 2014 to attend Western and has been based in the city ever since, apart from a period working on site in Berlin. He lives centrally and can meet London clients in person when seeing the operation or talking with the people doing the work will improve the requirement.
That local presence is most useful for businesses where the problem is operational. A screen-share can show software. Being in the room can reveal the sticky note, duplicate spreadsheet, manual approval or five-minute task repeated forty times a week that nobody thought to mention.
- Downtown London
- Western + Richmond Row
- Masonville + North London
- Old East Village
- South London
- Greater London area
HOW AARYN WORKS
Understand the business first. Add technology only when it earns its place.
Aaryn is comfortable working directly with owners and non-technical teams. He gathers requirements, explains tradeoffs in plain language, makes architectural decisions, communicates progress and stays accountable for the outcome.
That matters at Second Coat because web design and engineering are related without being the same service. Scott leads the customer-facing website work. Aaryn leads engineering when the costly problem is behind the website. A project can use one side or both without forcing a client into a vague agency package.
BACKGROUND + LINKS
See the work behind the résumé.
- BESc in Software Engineering · Western University · 2020
- Production full-stack and software engineering experience
- Backend architecture, APIs, SQL, databases and cloud infrastructure
- Python, FastAPI, Ruby on Rails, JavaScript, TypeScript, React and Next.js
- Docker, Linux, Git, payments and deployment automation
- AI inference, GPU workloads and distributed-system experience
LONDON TECHNICAL PROJECT?
Start with the thing that is wasting time or refusing to work properly.
You do not need to choose a technology or write a specification first. Describe the business problem. If it belongs with Aaryn, he takes the technical conversation from there.
TALK TO SECOND COAT