---
title: "Software Engineer at SignatureAPI"
company: "SignatureAPI"
position: "Software Engineer"
period: "November 2023 - September 2026"
contract: "Full-Time"
description: "I joined as the first engineer and built the platform from MVP to a production e-signature API handling thousands of requests per minute. I own the architecture, the CI/CD, the SOC 2 and HIPAA compliance work, and the AI integrations."
website: "https://signatureapi.com"
url: "https://rolandoandrade.me/career/software-engineer-signatureapi/"
author: "Rolando Andrade"
---

# Software Engineer at SignatureAPI

> I joined as the first engineer and built the platform from MVP to a production e-signature API handling thousands of requests per minute. I own the architecture, the CI/CD, the SOC 2 and HIPAA compliance work, and the AI integrations.

Period: November 2023 - September 2026. Contract: Full-Time. Company website: https://signatureapi.com

# From MVP to an award winning signature API

In 2023, electronic signature tools like DocuSign and Adobe were hard for developers to use. They were built for salespeople, not programmers. If you wanted to add signatures to your app, you had to deal with complicated documentation, confusing SDKs and high prices.

I joined SignatureAPI in November 2023 as the first engineer to change that. The product was an MVP, a first simple version. My job was to turn it into a platform developers would actually want to use. The goal was a programmer friendly API, plus connectors for automation platforms, at the most competitive price in the market.

Today the platform processes thousands of envelopes per day, over 100,000 envelopes per year, and hundreds of thousands of signed documents. An envelope is one package of documents sent out for signature. In 2024, SignatureAPI won Best API Debut at the API World Awards, alongside winners like Postman and Stack Overflow.

## Building the Playground

We launched our beta in March 2024. Developers signed up, but many left without trying the API.

I looked at the data and watched how people used the site. Developers had trouble making their first API call. They read the docs, but they got stuck before they tested anything.

I spent two weeks building an Interactive API Playground. It lets developers test the API before they write any code. They can create a document, add signers and send a test signature request just by clicking buttons.

![The Playground changed everything. It turned 'reading' into 'doing'.](https://storage.rolandoandrade.me/blog/signatureapi-birth-moment.webp)

This helped a lot. More developers started using our API, because they could see it work right away. It taught me that good documentation is more than text. It works better when people can try things for themselves.

## Signatures without code

As we grew, I noticed something. Developers loved our API, but people without technical skills at those companies wanted a simpler way to use it. They wanted to send contracts from spreadsheets without writing code.

I built a Power Automate Connector for Microsoft. Power Automate is a Microsoft tool for building workflows by clicking, not coding. Now someone in HR could set up a simple workflow like "when I add a new person to this Excel spreadsheet, automatically send them an NDA."

Teams without developers could now automate their work on their own.

## An architecture that stays up

Legal documents cannot wait for a server restart. We committed to less than 10 minutes of downtime per year. We have delivered zero downtime for multiple years.

The platform runs as five services. They are the core API, the signing ceremony, a cryptography service, a rendering service and an integrations layer. Each one deploys and scales on its own with Docker and ECS (Amazon's service for running containers). Heavy work like document rendering, email delivery and webhook dispatch runs through queues. A queue holds jobs until a worker is free. Each job uses idempotent retries, which means a job can safely run again without doing the work twice. This design sustains thousands of operations at the same time.

![Five services that deploy and scale on their own, with queues for heavy work](https://storage.rolandoandrade.me/blog/signatureapi-five-services.webp)

My daily tools at SignatureAPI include Node.js, NestJS, TypeScript, Next.js, React, Docker, Jest, S3, ECS, GitHub Actions, Clerk and Stripe.

I also rebuilt our CI/CD from scratch. CI/CD is the automatic path that tests code and ships it to production. Every merge now reaches production automatically in about 5 minutes. Staging deploys run in parallel. End to end tests are split into balanced shards, so they run side by side. Every change gets a live preview environment. Nobody pushes a button. Nothing goes down.

Performance gets the same treatment. When our worst dashboard queries passed 30 seconds, I moved the aggregations into PostgreSQL and added the right indexes. The same queries now return in under a second.

## Earning trust with evidence

Companies trust us with contracts, NDAs and medical documents. That trust has to be earned with evidence, not promises.

I co-designed our compliance strategy and then led the implementation. That meant security controls, organizational changes and enforcement across engineering. We achieved SOC 2 and HIPAA compliance. SOC 2 is a security standard for companies that handle customer data. HIPAA is the US law that protects health information. I also led our GDPR readiness, from the gap assessment to account anonymization and cascading data erasure. GDPR is the European data privacy law.

Behind the certifications there is a continuous hardening program. It includes least privilege IAM audits, which make sure every account has only the access it needs. It also includes strict HTTP security headers, cryptographically secure signing URLs, OTP lockouts, webhook signature verification and over 156 patched dependency vulnerabilities.

This work is less visible than new features. It is what makes customers trust us with their most important documents.

## Teaching AI agents to sign

Electronic signatures are an old market. AI agents are not, and they need to sign documents too.

I designed and shipped SignatureAPI's hosted MCP server. MCP (Model Context Protocol) is a standard way for AI assistants to use outside tools. With it, AI assistants can create and send envelopes directly. It handles OAuth and API key authentication, per account gating and file uploads through CloudFront and Lambda@Edge. It is also available as a Codex plugin and a Claude plugin.

I also made signing ceremonies agent aware. And I shipped an AI support agent that resolves customer tickets, using our own documentation as its knowledge base.

## More than engineering

Being the first engineer means doing more than engineering.

I presented the technical side of the product to Platanus during the accelerator's enrollment, and through the pre-seed investment that followed. I join integration calls with our largest enterprise customers.

I built a customer health dashboard that flags accounts at risk of leaving. About 70% of the customers we reached out to stayed with us, and nearly half became more active than before. I also mentored our junior engineer, who now works as a Product Manager.

## Where we are today

SignatureAPI handles rental agreements, freelance contracts and company approvals for paying customers every day. New developers find us every week.

We are making it easy for developers, and now AI agents, to add legally binding signatures to their apps. As simple as sending an email.
