Another great question here! To start, I think I’d reframe the notion of surface-level integration work. Sure, certain things in the world of integrations might be simple, like setting up a webhook when a form is submitted to then go to a slack channel. However, at the same time, those surface-level things are also super complex if you look a little deeper. For instance:
This automation works when we have 50 people a week, but what if I had 5000.
If I run a commercial and get a bunch of traffic to my site, will this automation break?
So, there’s definitely a lot of deep technical thought to be done in the world of integrations.
With that being said, the biggest separation factor for me is being able to understand the context of why you’re building what you are, and being able to tackle that problem creatively. Often times, you’re given an automation job where someone tells you exactly what they need, but their solution may only be one option. So, what I like to do is take a step back from the solution and say: “What problem does this form automation actually solve”. Then you also start involving things like Systems Architecture into your skillset
