software development

software development

Hourly rate: members only

Availability: members only

Willingness to travel: At home

Professional status: Freelancer

Last updated: Apr 14, 2026

Total work experience: 4 year(s)

Language skills: English,

Personal summary

I build software systems—mostly backend, data, and machine learning work—where the goal is simple: make things actually work in real conditions. Over the past few years I’ve been building projects end-to-end, usually starting from an idea or problem and turning it into a working system. That includes designing the backend, working with databases, building APIs, handling data pipelines, and fixing issues when things break in edge cases or under real usage. Most of my experience comes from hands-on work rather than formal environments. I’m used to figuring things out as I go, breaking problems down, and building something stable even when the requirements aren’t fully clear at the start. I work a lot with backend systems and data-heavy applications. I care about whether a system holds up, not just whether it runs once. That means thinking about structure, failure points, and how the pieces connect—not just writing isolated functions. I also work with machine learning in a practical way. I’ve built projects that involve cleaning data, creating features, training models, testing results, and plugging those models back into real applications. For me, ML only matters if it can actually be used inside a working system. I use AI tools as part of my workflow to move faster when building and debugging, but everything still gets checked, fixed, and shaped by me. I don’t treat it as outsourcing thinking—it’s just a tool to speed up the build process. I can work alone or with a team. If I’m working solo, I can take a project from idea to finished system. If I’m in a team, I can plug into an existing codebase, follow structure, and contribute without slowing things down. I’m flexible with how I work as long as the goal is clear. When I build things, I focus on a few things: it actually works when real data hits it it doesn’t break the moment something unexpected happens it’s structured enough to change later without rewriting everything it’s not fragile or overcomplicated I’ve learned that most problems in software aren’t about writing code—they’re about making sure the system doesn’t fall apart when reality doesn’t match assumptions. Right now I’m focused on backend systems, data-driven applications, and machine learning that can actually be deployed and used. Not just experiments, but things that run and stay running. If you work with me, you’re getting someone who takes ownership of the technical side. I don’t just “complete tasks”—I build the thing, test it properly, fix what breaks, and stay with it until it’s solid.

Certificates

dev ops mastery

2025 Canada

google advanced data analytics

2025 Canada

Language skills

English

Fluent knowledge