Avantos is an AI-native operating system that unifies client data and automates onboarding and servicing for financial institutions.
Company Overview Avantos AI is shaping the future of client relationship management by reimagining it through the lens of artificial intelligence. We are building the industry’s first AI-native operating system for financial services, transforming how firms onboard clients, deliver advice, and manage critical servicing workflows. Our platform consolidates fragmented data, automates complex processes, and embeds intelligent decision-making throughout every stage of the client lifecycle. Supported by Bessemer Ventures and MIT’s investment arm, our team comprises execution-focused, design-driven, product-centric founders and leaders from Wharton, MIT, top design programs, and unicorn SaaS companies. We move swiftly, tackle deep industry challenges, and build technology that empowers users to take charge of their workflows. If you thrive on client impact, innovative product design, and tackling complex problems, Avantos is the place for you. About the role Sitting at the intersection of implementation engineering and solutions engineering, we’re looking for a Workflow Engineer to turn complex business processes into reliable, production-ready workflows on our workflow platform. You’ll work directly with product, operations, compliance, and customer-facing teams to translate messy real-world requirements into forms, integrations, rules, approvals, automations, and workflow logic that runs in production. You’ll author workflows in two complementary modes: Code-based workflows. Workflow definitions live in our repository as typed code, alongside tests. Provisioning is done by an idempotent CLI that projects the code into a target environment. Git is the source of truth — review, branching, rollback, and standardization across customers all flow through the normal engineering pipeline. Visual workflow builder. A drag-and-drop designer for workflows that are simpler, exploratory, or owned by non-engineering stakeholders. Most workflows that need to ship across multiple customer environments, are regulated, or benefit from unit-tested rule wiring live in code. The visual builder is the right tool when iteration speed or non-engineer ownership matters more. What you’ll do Build and ship workflows - Translate business requirements into workflow designs: forms, API integrations, branches, loops, wait conditions, computed expressions, and nested sub-workflows. - Author workflow definitions in code for anything that needs Git-grade rigor: typed structures, tests, and code review. - Author workflows in the visual builder when iteration speed or non-engineer ownership outweighs Git-grade review. - Build forms: pick the right elements, configure validation, add visibility and required rules, and wire data flow. Integrate and operate - Configure outbound HTTP integrations and manage auth, including OAuth2, API tokens - Provision workflow definitions idempotently across environments: dev → staging → UAT → production. - Deploy across multiple customer environments, thinking carefully about what to share, what to customize, and what is worth abstracting. - Debug failing runs using logs, preview tooling, and trace-style execution visualizations. Add logic at the right layer - Use no-code condition editors for branches and form rules. - Use computed expressions for pure derivations. - Use embedded JavaScript in the form sandbox for dynamic form behavior, validation, and integrations. Test and ship - Perform your own manual tests. - Validate work in the platform’s preview and debug surfaces before shipping. - Version your work, write meaningful release notes, and stage deployments through the environment ladder. Partner with stakeholders - Work with product, ops, compliance, and customer-facing teams to translate requirements into workflows. - Push back when a process should be redesigned, and move quickly when the process is sound. - Clarify requirements quickly, explain trade-offs clearly, and get to working prototypes fast. Minimum Qualifications - Strong programming fundamentals in a statically typed language such as Go, Java, C#, Kotlin, Rust, or TypeScript. - Working knowledge of JavaScript or TypeScript. Embedded JavaScript runs inside a form renderer’s sandbox, so you’ll need to write correct async-aware, side-effect-aware JS. - Comfort with JSON Schema and structured data. Forms are JSON-Schema-driven; you’ll read it, write it, transform it, and occasionally hand-edit it. - REST / HTTP intuition: reading an OpenAPI spec, building a request, debugging a 4xx, and deciding when to retry vs. fail. - Strong testing habits. You write tests as you build, not after, and you understand the value of testing rule wiring — not just the happy path. - Engineering rigor in a code-as-config world: idempotent provisioning, version control, meaningful release notes, treating renames as breaking changes, and documenting gotchas for the next person. - Strong written and verbal communication. You’ll spend real time clarifying requirements and explaining trade-offs to non-engineers. - A bias toward shipping. Expected to ramp on - Our Go-based workflow authoring model. - Our provisioning CLI and environment model. - Platform-specific form, expression, and workflow patterns. - Multi-customer deployment patterns: what should be shared, customized, parameterized, or abstracted. Preferred Qualifications - Existing Go experience. - Experience with workflow or orchestration platforms Why this role is interesting You’ll work on workflows that are complex enough to deserve real engineering discipline: versioning, tests, code review, environment promotion, and reusable patterns. At the same time, the work stays close to real business problems. You’ll see the process, talk to the stakeholders, design the system, ship it, and debug it in production.