Skip to main content
redennInformatics
All open roles

Data / Automation Engineer

  • Patiala, India · Hybrid
  • 2 – 4 years
  • Full-time
  • Python
  • SQL
  • n8n
  • REST APIs & webhooks
  • PostgreSQL
  • ETL
Apply for this role

You will build the plumbing that keeps Redenn's systems talking to each other: leads moving from client websites into the Pro Lifeset CRM, ranking and analytics data landing in reports clients actually read, and workflow automations that retire jobs someone is currently doing by hand. Part of it is client integration work and a lot of it is our own product.

Why this role

Automation here is not a ticket queue you drain, it is you finding the manual process, killing it, and watching the hours come back to people sitting in the same room as you.

A normal week

  1. You trace a lead that never reached the CRM, find the webhook that failed silently, and add the retry and alert that stops it recurring.
  2. You build a scheduled workflow that pulls Search Console and GA4 data into a client reporting table.
  3. You sit with the SEO or sales team, watch them do something manually, and automate the boring eighty percent of it.
  4. You clean and reconcile CRM data before it feeds an AI feature, because the model is only as good as what it reads.

What you’ll do

  • Build and maintain data pipelines and scheduled jobs into Postgres.
  • Integrate third party APIs: CRM, Google, payments, email and client systems.
  • Design workflow automations in n8n or equivalent, with real error handling and alerting.
  • Own CRM data quality: deduplication, validation, migrations and backfills.
  • Instrument integrations so a break is spotted by us and not reported by the client.

What we’re looking for

  • 2 to 4 years building integrations, pipelines or backend automation.
  • Strong SQL, plus Python or Node for the glue between systems.
  • Real experience with REST APIs, webhooks, auth flows, rate limits and retries.
  • Hands-on with a workflow tool such as n8n, Make or Zapier, or a good reason you built it yourself instead.
  • You think about failure modes before you think about the happy path.

Nice to have (not required)

  • Experience with Supabase or Postgres in production, though a MySQL background transfers cleanly.
  • You have worked with Google Search Console, Analytics or Ads APIs; if not, those docs are readable and we will give you the time.
  • Some familiarity with LLM APIs, since more of our automations now have a model somewhere in the middle.

Sound like you?

Send your CV and a short note. A real person reads every application — expect a reply within a few business days.

Apply for this role