Wilson Bittencourt is in direct contact with the company and can answer any questions you may have. Email
I'm looking for a sharp, methodical problem-solver to dive into our core iPaaS application. The primary mission is:
- Diagnose and fix a critical, intermittent failure in our Facebook Graph API integration.
- Design and implement a logging system to expose integration failures to the frontend.
- Conduct a detailed review of our architecture and security to ensure it's robust and scalable for future connectors.
This is a complex challenge perfect for an engineer who loves connecting the dots between services, logs, and architecture to build reliable, observable systems.
Tech Stack:
Backend: FastAPI, Python
Frontend: React, TypeScript
Infrastructure & Data: AWS (EC2, RDS, S3, Lambda, etc.), PostgreSQL
Key Responsibilities:
- Investigate why our service, which fetches new leads from Meta forms via webhooks in real-time, fails intermittently.
- Analyze the entire data pipeline: from webhook reception, through our FastAPI service, to the database and any subsequent processing.
- Identify if any possible point of failure in the current connector - which could be in error handling, rate limiting, authentication token renewal, data parsing, database locking, or AWS infrastructure.
- Implement a robust, fault-tolerant solution to achieve as close to 100% reliability as possible.
- We have a real time report dashboard that show number of data processed, successful sync and speed of transfer. We need more comprehensive logging capture, store, and display integration execution logs, specifically focusing on unsuccessful operations (failed API pulls, rejected webhook pushes, authentication errors, etc.).
-This includes:
Backend: Structuring and storing logs in a queryable format (e.g., in PostgreSQL or a dedicated logging table).
API: Creating secure API endpoints to expose these logs to the frontend, filtered by connector, account, status, and time range.
Frontend Integration: Collaborating with our React/TypeScript frontend to display these logs in a user-friendly interface (a simple initial UI is acceptable; focus is on the data pipeline).
- Review the current application architecture for scalability, reliability, and security best practices, with a focus on the new logging system.
- Assess the codebase for its ability to serve as a platform for building additional, future connectors.
- Focus on data privacy and governance: ensure the architecture has proper data isolation, encryption, and access controls, especially for logs that may contain sensitive information.
- Provide a clear list of actionable recommendations for improvement.
- Document the current and proposed future-state architecture.
- Document the root cause of the Facebook issue and its solution (if any).
- Document the design and data flow of the new logging system.
- Create runbooks for troubleshooting. Your documentation should be so clear that a junior developer can understand and maintain the system.
Who You Are (Ideal Profile):
- A senior software engineer with 5+ years of experience, especially in backend and integration development.
- A master debugger with a proven track record of solving elusive, intermittent technical problems.
- Extensive experience with Python (FastAPI) and AWS ecosystems.
- Experience building observability features like application logging, monitoring, and status reporting.
- Deep knowledge of REST APIs, Webhooks, and OAuth flows. Experience with Facebook Graph API is a massive plus.
- Understanding of PostgreSQL and database performance.
- A security-minded individual who thinks about data privacy and access controls by default.
-Able to integrate MCP or AI in the existing app
- You believe that "code isn't done until it's documented."
- Good communication skills in English.
Project Details:
Expected Duration: 2-4 weeks (part-time, to be refined based on your assessment).
Level: Senior, Expert.
Location: Remote.