If you enjoy taking messy real-world systems, figuring out how they fit together, and making the entire thing work reliably in production, this role is for you.

About MindpexMindpex is building an AI-powered B2B SaaS product that helps organizations understand what is happening inside their workforce and take timely action.

We are currently moving from MVP development toward real customer implementations and production deployment.

At this stage, one of our most key engineering challenges is making Mindpex work reliably with the different software systems our customers already use.

Every customer may have a different HRMS, SaaS tools, APIs, data structures, authentication methods, and workflows.

Your job is to make all of that work with Mindpex.

The RoleWe are looking for a highly capable SaaS Integration & Product Implementation Engineer who can take ownership of customer integrations from beginning to end.

You will work at the intersection of:

Customer systems → APIs/connectors → data mapping → Mindpex → production deployment → customer feedback → product iteration

This is not a role where you will simply receive isolated development tickets.

We are looking for someone who can understand the complete problem, figure out what needs to be done, execute it, communicate clearly with the team and customer, and stay with the problem until it works.

What You Will Actually Do1. Integrate customer systems with MindpexYou will:

- Understand how a customer's existing software stack works.
- Identify the APIs, webhooks, databases, exports, authentication mechanisms, and other integration points available.
- Connect external systems to Mindpex.
- Work with integration platforms such as Kombo or equivalent solutions where appropriate.
- Build custom integrations when an existing connector is insufficient.
- Troubleshoot failed or incomplete integrations.
- Make the complete data flow work reliably in production.

2. Solve the data-mapping problemThis is one of the most important parts of the role. Different customers may represent the same information differently.

For example

Customer system: employee_codeMindpex: employee_idor:

Customer system: reporting_toMindpex: manager_idYou will determine how customer data should be mapped into Mindpex's expected schema, including:

- Field mapping
- Schema transformation
- Data normalization
- Data validation
- Missing fields
- Different naming conventions
- Different data formats
- Different values/enumerations
- Nested or inconsistent data structures
- Error handling and validation

The objective is simple: Whatever valid information the customer's systems provide must reach Mindpex in a structure that Mindpex can reliably understand and process.

3. Own production implementationYou will help take integrations from development to actual customer usage.

This includes working with

- Google Cloud / GCP
- Cloud Run
- Docker
- Node.js
- Python
- REST APIs
- PostgreSQL / Supabase
- Environment variables
- Secrets
- Authentication
- CI/CD
- Logging and troubleshooting





You should be comfortable investigating problems across multiple parts of a system rather than assuming that an issue belongs to someone else. 4. Work directly with customer realityThis is an MVP-stage product.

That means customers will tell us:

"This works.""This doesn't work.""We need this.""The data we're seeing isn't correct.""This workflow doesn't make sense."You need to be comfortable taking that feedback seriously, investigating the underlying technical problem, and helping the team determine what needs to change.

Sometimes the required change may be small.

Sometimes it may require a significant change to the product or integration.

You should be comfortable with both.

5. Rapidly iterate the product when requiredYou should be technically capable of contributing to product changes when the customer implementation reveals a genuine product or engineering problem.

That may involve

- Backend changes
- API changes
- Data-processing changes
- Integration changes
- Database changes
- Small frontend changes
- Changes to data structures
- Changes to workflows
- Debugging across multiple services

You will work closely with the existing engineering team to make these changes safely and quickly. 6. Become the technical bridge between the customer and engineeringYou should be able to take a customer's problem and translate it into a technical problem.

For example

Customer: "The employee information coming into Mindpex isn't correct."You should be able to investigate:

Where did the data originate? → What did the customer system provide? → What did the connector return? → Where was it transformed? → What did Mindpex receive? → Where did the mismatch occur? → What needs to change?

And then communicate the answer clearly to both the customer and the engineering team.

What We Are Looking ForWe are specifically looking for someone who is:

Technically strongYou should have strong practical experience with:

- SaaS/API integrations
- REST APIs
- Webhooks
- Data mapping and transformation
- Node.js
- Python
- Production deployments
- Google Cloud / GCP
- Docker
- Databases
- Authentication and API credentials

A strong technical generalistYou don't need to be the world's best specialist in every technology. But you should be capable of moving across a system and understanding how the pieces fit together.

If something breaks between

Frontend → Node.js → Python → database → external API → cloud deployment you should be comfortable tracing the problem.

We Care About How You WorkTechnical ability alone isn't enough for this role.

We are looking for someone who demonstrates:





OwnershipYou don't wait for someone else to tell you every step.

ReliabilityIf you commit to something, you follow through.

DisciplineYou communicate clearly, document important decisions, and keep the team informed.

CommunicationYou can explain complicated technical problems clearly to engineers and non-engineers.

Customer orientationYou don't treat customer problems as someone else's problem. You help find the solution.

Problem-solvingWhen something doesn't work, you investigate until you understand why.

AdaptabilityYou are comfortable working in an MVP where requirements can change based on real customer feedback.

Long-term commitmentWe are looking for someone who wants to stay involved, understand the product deeply, and grow with it—not someone who wants to complete a few tasks and disappear.

Who Should ApplyThis role is particularly suitable for someone who has previously worked on:

- B2B SaaS implementations
- Enterprise software integrations
- HRMS / ERP / CRM integrations
- API integration platforms
- Middleware
- Data synchronization
- Customer onboarding/implementation
- Production SaaS deployments
- Systems where multiple independent services need to work together

If you have previously been given an unfamiliar customer system and told:

"Figure out how to connect this to our product and make it work."—you are exactly the kind of person we want to speak with.

What Would Make You Stand OutStrong candidates may have experience with:

- HRMS integrations
- Enterprise SaaS implementations
- OAuth and API authentication
- Webhooks
- Data normalization / canonical schemas
- ETL or integration pipelines
- Kombo or similar integration platforms
- PostgreSQL / Supabase
- GCP / Cloud Run
- Distributed systems
- Customer-facing technical implementation
- Taking products from MVP → pilot → production

EngagementThis opportunity is initially offered on a pro bono / volunteer basis.

We are transparent about this upfront.

We are looking for technically strong people who are genuinely interested in:

- Working on a real B2B SaaS product
- Solving real enterprise integration problems
- Working directly with customer implementations
- Understanding how an MVP evolves through real customer feedback
- Gaining hands-on experience taking a product toward enterprise production
- Taking meaningful ownership rather than working on artificial internship projects

This is intended as a long-term opportunity for the right person.

We are not looking for someone who simply wants a certificate or a short-term project to add to a resume.

What Success Looks Like

You will be successful in this role when we can give you:

"Here is the customer, here is their technology stack, and here is what Mindpex needs."

…and you can:

understand it → determine the integration approach → map the data → implement it → deploy it → test it → troubleshoot it → communicate with the customer → identify product gaps → help fix them → get the customer working successfully.

That is the job.

📌 Pro Bono / Long-Term Opportunity - SaaS Integration & Product Implementation Engineer (Bengaluru)
🏢 Mindpex
📍 Bengaluru