At Chi, I stepped into the role of project manager, even though that wasn’t my official title.
I was responsible for communicating directly with clients, gathering their requirements, and translating their needs into clear, actionable plans.
I organized the team, delegated tasks, and helped align everyone on project goals.
This experience strengthened my communication skills and gave me a broader view of the product lifecycle.
ProSoft outsourced me to a company in India — a unique experience in which I represented my company while working remotely with a completely different team and culture.
I collaborated with senior engineers abroad, participated in weekly cross-border meetings, and adapted to an unfamiliar tech stack.
They were using an outdated version of Vue.js and SVN for version control — quite a shift while GitHub was the standard elsewhere.
This role challenged me to adapt quickly, bridge tech gaps, and maintain productivity under unfamiliar constraints.
I often conducted meetings with clients to extract business requirements, structure them logically, and deliver them to the pricing team in a clear format.
I conducted interviews for incoming candidates. This involved:
At the end of each interview, I gave personalized feedback, often handing candidates a list of skills or concepts they should learn next.
It wasn’t just about evaluation — it was about mentorship and growth.
Since I was building foundational architectures for various projects, I took the lead on code reviews for my team.
I enforced clean and maintainable code from the start.
Eventually, I integrated ESLint and other tools to automate many aspects of the code review process, reducing the need for manual checks.
Although I wasn’t hired for DevOps, I saw a major inefficiency in our deployment process — it was completely manual and required constant help from the backend team.
I introduced and implemented a CI/CD pipeline using GitLab.
I automated the entire process, allowing developers to deploy independently without needing server credentials.
This change saved time, improved team agility, and removed bottlenecks in the development lifecycle.
I helped draft job descriptions and KPIs for various positions including:
This helped the company clearly define role expectations and attract the right talent.
Even though I joined the ERP project in its third version, I took ownership of documenting the entire system:
I created comprehensive technical documentation, detailing architecture, features, and internal workflows.
This required a deep dive into unfamiliar codebases, understanding legacy systems, and translating that knowledge into readable documentation for current and future team members.
It wasn’t easy, but it was essential — and I’m proud of how it turned out.
A personal portfolio website is your digital resume—a place to showcase your work, skills, and achievements.
I'm a software engineer with 6 years of experience in both backend and frontend development. I specialize in building high-quality web applications with modern JavaScript frameworks.
