At Mark Spain Real Estate, Paulo Cardoso worked as a Senior Full Stack Engineer and Technical Lead through Upstart13. He maintained the serverless integration layer joining Salesforce, Homeward, the CMS, the website and internal services, built the appointment-to-offer handoff, migrated WordPress content to Strapi, and solved fixed-egress networking for AWS Lambda.
Sales lived in Salesforce. Investor offers came through Homeward. Content lived in a CMS. The website ran on Next.js. Around them sat internal services and third-party APIs.
Every gap between those systems became either a manual step for the operations team or a place where data could quietly diverge. The work was not one standalone app. It was ownership of the seams.
Paulo maintained a central API layer in Node.js on AWS Lambda behind API Gateway, with bearer-token authentication and CloudWatch logging. It connected Salesforce, Homeward, the CMS, the website and internal services.
After a sales appointment, Salesforce data had to reach Homeward so an investor-offer application could begin. Paulo built the Node.js 18 Lambda endpoint, completed the field mapping across both systems, coordinated new fields with the Salesforce team and delivered the partner documentation.
Paulo did not build this page. Behind it, he maintained the serverless integration layer, executed the WordPress-to-Strapi migration and built the fixed-egress networking that kept partner connections unblocked.
One integration layer · five connected systemsA Lambda has no stable public address by default. The partner allowlisted by IP, so the integration needed a deliberate network path: private subnets, NAT Gateway and Elastic IP. That infrastructure detail was the difference between a correct endpoint and one the partner could actually call.
The serverless layer kept sales, marketing, content, the website and real-estate partners exchanging data through one owned seam.
The Salesforce-to-Homeward flow removed manual steps between an appointment and an offer in flight. The WordPress content and media moved to Strapi and S3 across staging and production. Fixed-egress networking gave serverless workloads the stable address the partner required.
No invented numeric outcome is claimed. The supported results are qualitative: fewer manual handoffs, a CMS the company could build on, and integrations that were no longer blocked by networking.
Headless content and SSO gave a healthcare community a faster platform for new products.
A regression model turned shutdown cost history into a projection before budget commitment.
Connecting systems across a business? See embedded engineering, software rescue, or the guide to automating a business process.
Next / Your build
Taking on new builds
Tell us what you're making. We reply within one business day, and you get a fixed price and a date in writing before any code.
