Pro Bono / Long-Term Opportunity - SaaS Integration & Product Implementation

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 important 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 mappingSchema transformationData normalizationData validationMissing fieldsDifferent naming conventionsDifferent data formatsDifferent values/enumerationsNested or inconsistent data structuresError handling and validationThe 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 / GCPCloud RunDockerNode.jsPythonREST APIsPostgreSQL / SupabaseEnvironment variablesSecretsAuthenticationCI/CDLogging and troubleshootingYou 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 changesAPI changesData-processing changesIntegration changesDatabase changesSmall frontend changesChanges to data structuresChanges to workflowsDebugging across multiple servicesYou 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 integrationsREST APIsWebhooksData mapping and .