Mohammad Kaleem

Automation Engineer & Backend Developer

IDL Bridge • Full-time

May 2023 - Mar 2025 • 1 yr 10 mos

1. The Architect (System Design) Before you write a single line of Python, you have to map out how data moves. You decide: How will the scraper talk to the database? How do we trigger a GoHighLevel (GHL) workflow without breaking the API limits? The Goal: Designing a system that is "scalable"—meaning it works just as well for 10,000 trucks as it does for 10. 2. The Builder (Development & Integration) This is the core "Backend" work. You are building the "engine" under the hood of the car. Writing Robust Scrapers: You don’t just "pull data"; you handle errors, bypass anti-bot detections (like Cloudflare), and manage login sessions. API Management: You build the bridges (Webhooks or REST APIs) that allow different software—like a Load Board and a CRM—to talk to each other. Data Transformation: You take "messy" data from a website and turn it into "clean" JSON or CSV data that a business can actually use. 3. The Firefighter (Maintenance & Optimization) In automation, things break because external websites change. Debugging: When a Load Board updates its website layout, your scraper might break. An engineer’s job is to identify the "break" and fix it immediately. Optimization: You make the code faster. If a script takes 5 minutes to run, an engineer finds a way to make it take 30 seconds using multi-threading or better logic. 4. The Translator (Business Logic) This is what you're doing in your meeting right now! You take a business problem ("I'm losing time entering data") and translate it into a technical solution ("I will build a headless browser automation with a POST request to your CRM"). Think of it this way: A "Coder" follows instructions. An "Engineer" understands the business goal and builds the most efficient tool to reach it.