I turn
problems into
working products.
ANUJ CHOUDHARYWorking across software, AI, cloud and product—from understanding the problem to shipping the solution.
Work measured by
what moved.
Beyond titles and technology, the clearest signal is what shipped, who it helped, and the ownership required to make it real.
Built from the
problem up.
Products, systems, and experiments I've taken from an early idea toward implementation. Swipe or use the controls to explore.
From “we have a
problem” to production.
My advantage isn't one language or framework. It's taking ownership across the whole path to a working outcome.
Understand
Business context, users, stakeholders, and the constraints shaping the real problem.
Design
Requirements, architecture, data flows, and a product experience that makes sense.
Build
Full-stack systems, AI workflows, integrations, and prototypes that become products.
Deploy
Cloud infrastructure, delivery pipelines, observability, and production readiness.
Iterate
Stakeholder feedback, product signals, performance, and the next useful improvement.
A progression of
ownership.
Every chapter, from Canadian co-op internships and independent client work to product building, founding a company, and forward deployed engineering.
Forward Deployed Engineer
NuVista | Atlanta, Georgia, USA
Business, product, engineering, AI, cloud, and delivery.
Founder & CEO
Chaev Services | India · Remote
Product direction, architecture, engineering, and execution.
Product Builder
Anonymate | Canada
Built an anonymous student community product from concept to implementation.
Freelance Software Engineer
Freelance | Remote
Delivered focused web products for real clients and businesses.
Software Engineer
CGI | Canada
APIs, automation, systems, and dependable delivery.
Junior QA Analyst
CUMIS | Canada
Maintainable software and production work in an enterprise setting.
Full Stack Developer
Autoly | Canada
Built across the front and back end of an automotive startup product.
Test Analyst
CIBC | Canada
Built a foundation in quality, systems thinking, and detail.
“The code is rarely
the hardest part.”
Projects rarely fail because nobody could write the API. They fail because the wrong problem was solved, requirements stayed fuzzy, or engineering drifted away from the business.
I prefer to understand the context first—then make the technical decisions.
Product engineering
Full-stack systems / SaaS / Mobile / APIs / Product architecture
AI & intelligent systems
LLM applications / Conversational interfaces / AI workflows / Automation
Cloud & infrastructure
AWS / Serverless / Docker / CI/CD / Production delivery
Discovery & delivery
Technical discovery / Requirements / Stakeholders / Prototyping / Iteration
I've sat on
both sides of the table.
Building my own products changed how I approach engineering. When resources are limited and every decision matters, technology has to serve the product—not the other way around.
That experience made uncertainty, MVP trade-offs, speed versus quality, user feedback, and shipping feel like engineering concerns—not somebody else's job.





