When I joined as a Software Developer Intern, I knew how to build software but had never worked with Zendesk. Six months later, I had completed partner training, built a Salesforce to Zendesk connector, and moved into a full-time Zendesk Developer role. This is how I learned the platform and found my first real project.
Where I Started
At first, I did not know what a trigger was, how a macro helped an agent, or why a support team tracked SLAs. I needed to understand the work happening inside Zendesk before I could build anything useful on top of it.

Months 1 and 2 Learning the Zendesk Basics
I began with the language of support: the ticket lifecycle, triggers and automations, macros, views, and SLAs. Zendesk training modules gave me a structure. After each lesson, I opened a test account and tried the idea myself by creating tickets, applying macros, and checking when triggers fired.
It felt slow at times. But seeing those tools from an agent’s perspective gave me a mental model of the platform that made the more technical work easier to understand.
Months 3 and 4 Working Toward Certification
Next came a Zendesk partner training program, the Implementation Expert course. Its videos and quizzes covered ticket forms, business rules, omnichannel routing, reporting, and other parts of a support setup. I had to finish each module and pass its quiz before moving on.
The final task was hands-on. I received a detailed configuration brief and built my own Zendesk Suite Standard instance to match it, including ticket fields, triggers, SLAs, and roles. A reviewer checked the setup against the brief. I received the certification only after it passed that review.
That two-month course made the theory practical.
Months 5 and 6 Building My First Connector
With that foundation in place, I spent the final two months of my internship learning the Zendesk Apps Framework, or ZAF. My first real developer project was a Salesforce to Zendesk connector that synced customer and case data between the two systems.
Working with Zendesk developer tools and an external platform’s API forced me to learn how an app authenticates, requests data, and renders inside the agent workspace. It was the point where the platform stopped being a set of training exercises and became something I could build on.
The Move to a Full Time Role
At the end of those six months, I was promoted from Software Developer Intern to full-time Zendesk Developer. The Implementation Expert certification showed I could configure the platform; the Salesforce connector showed I could use those skills in a real project. Together, they formed the foundation for that next step.
What I Am Building Now
As a Zendesk Developer, I am helping build Help Center IQ. The problem behind it is familiar to support teams: customers ask the same questions repeatedly while useful Help Center articles may be missing, weak, or out of date.
Help Center IQ is designed to analyze support tickets, group repeated questions into topics, and compare them with the existing Help Center. It identifies knowledge gaps and uses ticket context to prepare draft articles for a person to review, edit, and publish.
This work has changed my view of development. I am learning how product decisions are made and how a tool can fit into an agent’s daily workflow. I am still learning, especially around the AI and data side of the product, but building something for a real support need is the part of this journey I am most proud of.
Four Lessons I Would Share With a New Developer
- Learn as an agent first. Create tickets and use macros and views before you try to extend the platform. The technical pieces make more sense when you know why a support team uses them.
- Take the hands-on work seriously. The certification task made me configure a complete instance and check it against requirements. That practice stayed with me longer than the quizzes alone.
- Build a real integration. The Salesforce connector made me work through authentication, data requests, and the agent interface. I learned more from that project than I could have from reading documentation alone.
- Say yes to a live product. Help Center IQ has shown me how developers weigh a product idea against the questions agents and customers actually have.

Where I Am Now
I started without knowing what a Zendesk trigger was. Six months of deliberate practice, a hands-on certification, and a connector project led to a full-time developer role. Today I am building on that foundation with Help Center IQ, and there is still plenty for me to learn.
If Zendesk feels overwhelming at the start, begin with one ticket and one workflow. Learn what the team needs, then build a small project that solves a real problem. That is how the path opened up for me.
Interested in a career in Zendesk development? Get in touch with our team.




