About

I didn’t take the traditional path into development.

I came to Salesforce through music, customer service, leadership, and a curiosity about how better systems get built.

Jeremy Shull standing outdoors in warm evening light.

How I got here

A different starting point, with useful carryover.

My degree is in Worship & Music Studies, and I spent more than a decade in customer service at Starbucks. Several of those years were as a Shift Supervisor. That work taught me how much clear communication, reliable processes, and steady problem-solving matter when people are counting on you.

I stayed involved in worship ministry and church technology along the way. Music, audio, video, and livestream systems gave me a practical place to keep learning how creative work and technical systems fit together.

Curiosity about development eventually led me to Salesforce. My path has included earning Salesforce Platform Developer I, completing Cloud Code Academy Developer Kickstart, and earning the Salesforce Administrator certification. Today I build with Apex, Lightning Web Components, Flow, integrations, and the wider Salesforce platform.

The short version

A few stops that shaped how I work.

  1. 2014

    A foundation in music and ministry

    I earned a B.S. in Worship & Music Studies: Worship Leadership and continued serving in worship ministry.

  2. More than a decade

    Customer service and leadership

    My time at Starbucks included several years as a Shift Supervisor, where clear communication and dependable processes mattered every day.

  3. Ongoing

    Church technology

    Working with church audio, video, and livestream systems kept creativity and technical problem-solving connected.

  4. Salesforce path

    From curiosity to building

    That curiosity led me to Salesforce, earning my Platform Developer I certification, completing Cloud Code Academy's Developer Kickstart, earning my Salesforce Administrator certification, and building hands-on projects with Apex, LWC, Flow, and integrations.

How I build

I want to understand the system, not just make it run.

I care about why a solution works and how its pieces fit together. That means thinking through the architecture, testing the behavior, reviewing the result, and being able to explain the decisions behind it.

01

See the whole system

I look at data, automation, integrations, and the user experience as connected parts of the same solution.

02

Test the behavior

I test the expected path and the edge cases, then revisit anything that does not behave the way I intended.

03

Review and explain

I review my work closely and make sure I can explain the choices, tradeoffs, and limits in plain language.

AI is part of that workflow. I use it to explore approaches, debug problems, and move implementation forward, but I am still responsible for understanding, reviewing, testing, and explaining what I build.

Beyond Salesforce

There is usually a guitar or a controller nearby.

Music is still a big part of my life. I play guitar, stay involved in worship ministry, and enjoy the behind-the-scenes work of church audio, video, and livestream technology.

Outside of that, I spend time on fitness and gaming. Both give me a good reset, although they bring out very different versions of my competitive side.

Location and availability

Based near Indianapolis and open to the right conversation.

I’m pursuing Salesforce Developer, Salesforce Administrator, CRM Analyst, Salesforce Business Analyst, Salesforce Support Engineer, and associate consulting opportunities.

Based in
Greater Indianapolis Area
Availability
Open to remote roles and opportunities across Greater Indianapolis and Central Indiana.
Relocation
Not seeking relocation.
Independent work
Open to freelance or consulting conversations.