Growth Engineer

Incode Technologies · Mexico

Apply on the company website

About Incode

Incode is a Series B unicorn ($2 B valuation) rewriting how the world proves identity. Our AI-powered platform lets leading banks, fintechs, marketplaces, and governments deliver friction-free experiences while defeating fraud and safeguarding privacy. Customers such as Citi, AirBnB, Block, Chime, Sixt, and TikTok rely on Incode to power their identity verification and security. Recently named a leader in the Gartner® Magic Quadrant™ for Identity Verification, we’re scaling fast.

The Impact You’ll Make

Growth at Incode owns the top of funnel - the pipeline that feeds every region's revenue number. This role exists to build the systems that generate it.

You'll ship AI agents, automations, and workflows across the full top-of-funnel surface: outbound, inbound, lead qualification and routing, event and conference motions, account and competitive research. The work is grounded in live Salesforce, Supabase, and Outreach data and supports revenue teams across NAM, LATAM, and EMEA. The Growth AI Office - our multi-agent GTM operating system - is where it lives, and a fleet of these agents is already in daily production use.

Today that fleet is built and maintained by a single engineer. You are the second builder.

You'll design and ship new agents, harden the ones already running, and own the integration layer that connects them to the systems revenue actually runs on. This is not an internal-tools ticket queue and it is not research. It is applied engineering where the output is measured in qualified pipeline, meetings held, and hours returned to a 24-person revenue team.

A note on the title: "Growth Engineer" means different things at different companies. Here it does not mean product-led growth or experimentation infrastructure - Incode sells to banks, fintechs, marketplaces, and governments, and there is no self-serve funnel to optimize. It means engineering applied to pipeline generation. You will write and deploy production Python and Node services, stand up MCP servers, and own your own CI/CD - not configure a no-code platform. If your strongest work is A/B test infrastructure and activation metrics, or enrichment waterfalls inside a vendor UI, this is the wrong role. If you are an engineer who chose revenue systems as your problem space, keep reading.

What You’ll Own & Drive

• Top-of-Funnel Agent Development - Design, build, and ship production LLM agents that generate and qualify pipeline: scoped skills, explicit guardrails, human-in-the-loop checkpoints, and clean multi-agent handoffs. Take agents from concept to daily use by non-technical operators across outbound, inbound, and event motions.
• MCP & Integration Infrastructure - Build and operate the Model Context Protocol servers and clients that connect agents to Salesforce, Outreach, Supabase, ZoomInfo, Notion, and Slack. Own authentication, token scoping, pagination, rate limiting, and graceful failure - including for systems with no native integration path.
• Grounding & Evaluation - Keep agent output tied to real records, not plausible-sounding invention. Build schema-aware retrieval, reconciliation checks, eval harnesses, and regression tests so a prompt change never silently degrades a production agent.
• Workflow & Decision Automation - Implement routing, scoring, and trigger logic across automation platforms (n8n, Tines-class) and custom services: webhooks, scheduled jobs, event-driven pipelines.
• Internal Tooling & Reporting - Build the web apps, dashboards, and interactive reporting that put agent output in front of BDRs and leadership in a form they'll actually use.
• Documentation & Durability - Write the runbooks, skill specifications, and architecture docs that make the agent fleet maintainable by more than one person. Enable GTM operators to extend what you build without filing a ticket.

The Qualities That Set You Apart

• Agent-Native Builder - You've shipped LLM-powered systems that real people depend on, and you know the difference between a demo and something that survives contact with messy production data.
• Integration Instinct - You default to connecting systems rather than replacing them, and you're comfortable building the middleware that vendors didn't.
• Evaluation Discipline - You treat prompts and agent skills as code: versioned, tested, measured. You can tell someone whether a change made an agent better, with evidence.
• Data Integrity First - Before you automate on top of a number, you check whether the number is trustworthy. You've been burned by a bad join and you don't intend to be again.
• GTM Fluency - You can read a pipeline report, hold a conversation about conversion rates, and design for how a seller actually behaves rather than how the org chart says they should.
• Ownership Under Ambiguity - You scope your own work from a business problem, ship something usable fast, and iterate. You operate like a founder with a unicorn's resources behind you.
• Handoff Mindset - You write so that the next person can run it. You measure success partly by how little you're needed for maintenance.

Your Background

Engineering foundation

• 4+ years professional software engineering
• 1+ year building and shipping LLM-powered applications or agents to production - used daily by people who are not engineers
• Strong Python and Node.js/TypeScript in production; React sufficient to build internal UI end to end
• At least one internal application you built start to finish: data model, backend, interface, auth, deployment, and the maintenance afterward

CRM and revenue systems - required

• Hands-on experience with both Salesforce and HubSpot. We run both, and this role writes against both. We are not asking for admin certification - we are asking for working fluency: standard and custom objects, field-level behavior and validation, record ownership and sharing, REST and bulk APIs, and a clear sense of what breaks downstream when you change something upstream
• Sales engagement platform experience - Outreach, Salesloft, or Apollo: sequence and step models, prospect and mailing data structures, and API access patterns
• A realistic view of how revenue data degrades in practice: duplicates, stale ownership, unenforced picklists, half-migrated fields - and what that means for anything automated on top of it
• Bonus: enrichment and contact data providers (ZoomInfo, Clay, Lusha-class) at the API level rather than the UI level

Databases and data work

• Production experience with Postgres or Supabase: schema design, migrations, indexing, query tuning, row-level security
• SQL fluency against a warehouse - Redshift, Snowflake, or BigQuery-class - including window functions and incremental models
• You have reconciled the same metric across two systems, found the delta, and explained it to a non-technical stakeholder

Automation, end to end

• You have designed, built, deployed, monitored, and maintained automations in production - not just built them. You own the alerting and the failure modes for your own work
• Webhooks, queues, scheduled jobs, retries, idempotency, and backfills. You have debugged a job that silently stopped firing
• Automation platform experience (n8n, Tines, Zapier-class) and the judgment to know when to abandon the platform and write the service instead. We care more about the second half of that sentence
• Routing, scoring, and decision logic implemented as code with test coverage, not as a chain of conditional blocks nobody can read

AI and agents

• Hands-on with MCP - servers, clients, custom endpoints - or an equivalent tool-calling and agent framework
• Production LLM API integration (Anthropic-class): structured output, tool definitions, context management, cost and latency tradeoffs
• Prompt and skill design treated as versioned artifacts, with some method for evaluating whether a change helped

Deployment, integration, and security

• Cloud deployment ownership: AWS, containerized hosting, CI/CD (GitHub Actions); Terraform or another IaC tool a plus
• OAuth flows, token lifecycle and refresh, credential vaults, header auth, and least-privilege scope review on the integrations you build

Nice to have

• Experience supporting a multi-region revenue team (NAM, LATAM, EMEA) and the data-residency questions that come with it
• Event and conference lead-capture tooling
• Notion and Slack API work
• Experience enabling non-technical teams on AI tooling - documentation, training, internal adoption

The Work You've Done Before

Come ready to walk us through two or three things you have built. The strongest candidates we have seen have shipped work like:

• An internal application a non-technical team now uses every day, where you owned it from data model to deployment
• A two-way integration between two systems that had no native connector, including how you handled auth, rate limits, and partial failure
• An agent or automation that replaced a recurring manual process, with a before-and-after number attached to it
• A data reconciliation between a CRM and a warehouse where the two disagreed and you determined which one was right
• Something you built, documented, and handed off - that someone else now runs without you

We care more about what you shipped and what broke than about which tools were on the sticker. If your strongest work used a stack we did not list, tell us about it anyway.

Why Incode?

• Mission with Meaning - Shape how billions of people prove identity - safely, simply, and ethically.
• Rocket-Ship Growth - Join at an inflection point where your strategies will compound in value for years.
• Elite Team & Backing - Work a truly global with top engineers, designers, and investors who share your ambition to dominate a category.
• Ownership & Autonomy - Operate like a founder with the resources of a unicorn.
• Global Impact - Every program you launch will reverberate across industries and continents.

Ready to ignite the future of trust?

Lead the narrative. Empower the field. Join Incode and turn innovation into unstoppable market momentum.

More jobs at Incode Technologies · Software Engineering jobs in Mexico