The person behind the systems

Curious by nature.
Practical by choice.

I'm Austin, a self-taught Python developer who likes turning complicated, repetitive work into systems that feel clear and dependable.

Austin John Salvador
PYTHON · AI · AUTOMATIONPH

What drives me

I build technology to make work easier, not more complicated.

Most of my work revolves around Python, APIs, webhooks, system integrations, and workflow automation. I especially enjoy finding the messy handoffs and repetitive steps inside a process, then turning them into something easier to manage, understand, and scale.

Today, that often means thoughtfully integrating AI where it can improve speed or decision-making while keeping the overall system transparent and reliable.

Experience that shaped me

More than 100 clients taught me what production really means.

Before moving into full-time remote development, I freelanced as Austin_js. I served more than 100 clients and maintained a perfect five-star track record across a wide range of technical projects.

Those projects taught me far more than programming. They taught me to uncover requirements, troubleshoot unexpected problems, communicate clearly, and take responsibility for the systems I delivered.

I later moved into remote Python and backend development, working with teams and existing production systems across Flask applications, APIs, webhooks, background processes, internal tools, alerts, and workflow improvements.

An unconventional path

I learned by building things people needed.

My path into software was not traditional. During the pandemic, I began learning MQL4 and MQL5 to create automated trading tools with friends. That experience showed me how code could turn an idea or manual process into something that worked on its own.

I moved from trading tools into Python and Ethereum development, then expanded into backend applications, APIs, business automation, and AI-powered workflows.

I use modern AI development tools to move faster, but I believe developers still need to understand, review, debug, and own the code they produce. Tools increase leverage; judgment makes the result dependable.

Working principles

What you can
expect from me.

Good systems come from good engineering habits and a clear understanding of the people who will use them.

01

Own the outcome

I care whether the system solves the problem, not just whether the code runs.

02

Communicate clearly

I surface tradeoffs, progress, and problems early so there are fewer surprises.

03

Keep learning

I stay curious, test ideas in practice, and adapt quickly when the situation changes.

Let's make something useful

Bring the problem.
I'll bring the systems thinking.