Software Engineer, Developer Infrastructure

New York City · Full-time · On-site · Engineering · Estimated base salary $150K–$250K, plus equity

About the company

Every business depends on accounting. Yet most software in the category was built in the early 2000s — slow, clunky, and years behind on AI. Accountants now face a growing, unsolved data problem created by complexity, volume, and fragmented systems, without the tools to address it. The problems are real, hard, and increasingly urgent. They are also solvable.

This company is building the modern platform for accounting and finance — the platform that delivers on the promise of live, rich, trustworthy data and insight companies can actually run decisions on.

The team takes on the foundational challenges required to automate ingest, transformation, matching, projection, and reporting across an end-to-end graph of financial data. By weaving together data, automation, workflows, and AI-first experiences, it gives accounting teams ownership of a continuous window into their company's finances and activity.

Product-market fit is strong, with a growing customer base that genuinely likes the product, including many of the best-known names in AI and fintech. Investors include top-tier venture firms alongside founders and executives from category-defining companies.

About the role

Platform Engineering here is engineering for engineers. Its customers are the company's own developers and, more and more, the AI agents working beside them. The mission is to make every engineer and every agent dramatically more productive through a shared platform, so anyone can move from idea to a safely deployed change without custom setup or tribal knowledge.

This role covers the developer-infrastructure side of that mission: environments, CI/CD and deployment, infrastructure-as-code, environment parity, observability, security, and internal tooling. The current state has real gaps — deploys without a staging gate, migrations that can't roll back cleanly, a production-database-clone lock that blocks deploys, Terraform drift, and two clouds where one should do. There is a roadmap to close them. This engineer will own parts of that roadmap end to end, then watch colleagues actually use what they built.

What this person might work on

1. Deployment process. Serialized, gated deploys across services; automated schema migrations with rollback; a staging-to-production promotion path engineers trust
2. Environments and parity. Local and remote dev environments that are dependable and quick to spin up; sandboxes and preview environments so reviewers verify behavior instead of only reading code
3. Agent-first development. MCP gateways, governance, cost management, and foundation model selection
4. Infrastructure-as-code. Spacelift/OpenTofu, drift remediation, migrating off DigitalOcean onto AWS, and IaC standards that are easy to follow by default
5. Repo standards and ownership. Linting, testing hierarchy, ownership manifests, idempotent onboarding, an ownership registry, and an internal developer portal
6. Observability foundations. Local tracing, logging, and metrics for every engineer; Datadog cost and hygiene; more mature incident management; status pages
7. Security and access. Unified secrets and config management, SSO in front of internal sites, IAM scoping, ECR scanning, audit logging, and vulnerability management
8. Internal AI tool hosting. A platform that lets anyone at the company ship an internal tool without re-solving auth, hosting, and observability each time

You might be a strong fit if you

1. Go deep on infrastructure — AWS, containers and ECS, networking, IaC — and stay pragmatic about it
2. Bring a product builder's instinct to developer experience: sensible defaults, tooling that teaches, and the conviction that shipping means seeing it work
3. Find problems by meeting your users — pairing with engineers, watching onboarding, reading the friction in Slack
4. Are comfortable building in-house when that's the right call, and explicit about when a third-party tool earns its place

Requirements

1. 3+ years of software engineering experience, including significant time on infrastructure, platform, or developer-productivity work
2. Confidence with AWS, IaC (Terraform, OpenTofu, or similar), CI/CD systems, and Linux and container fundamentals
3. Strong general-purpose programming skills, primarily TypeScript with Python where it fits

Nice to have

1. Experience with tools like Spacelift or Atlantis, Datadog, Firetiger, or Chronosphere, and GitHub Actions or Buildkite
2. Running incident management, defining SLAs, and keeping sites up through heavy traffic
3. Supporting non-engineer contributors, such as support engineers shipping fixes with AI tools

Stack

AWS (ECS, RDS, S3), OpenTofu/Terraform via Spacelift, GitHub Actions, Datadog, TypeScript/Node, Postgres, ClickHouse, Inngest

How the team works

This role is in-person in New York City.

Engineers learn the domain, meet their users, and exercise substantial creativity and agency over product direction. The team moves fast, operates with high integrity, and genuinely likes collaborating.

The company believes the best business is the one with the best individual contributors, and has built its culture to maximize their work. Great product and engineering are seen as the output of a desire to win, deep care for the craft, and pragmatism about shipping for overall impact. Engineers ground their work in a real understanding of the users, the domain, and the organization's goals.