Integration Engineer

Connect Every Financial System to Fiskl

We're at 80% automation today, building toward 95% autonomous accounting. We need someone obsessed with making every transaction – from every payment provider, bank, and platform – flow seamlessly into Fiskl. Zero manual entry is the goal.

The Mission

Build bulletproof integrations that capture every transaction from every source. We've nailed Stripe – now we need everything else. When a business uses Fiskl, every penny should appear instantly, ready for our AI to reconcile.

What You'll Build

• Payment Integrations: PayPal, Square, Adyen, Mollie, GoCardless, Wise, crypto wallets.
• Banking Feeds: Open Banking APIs, Plaid, TrueLayer – real-time transaction streaming.
• E-commerce Platforms: Shopify, WooCommerce, Amazon Seller, eBay.
• Accounting Migrations: One-click migration from Xero/QuickBooks.
• Data Enrichment: Transform messy transaction data for 98%+ AI matching accuracy.

Non-Negotiable: You Must Code with AI

We only hire engineers who use AI tools to ship faster. You should be using Claude/GPT-4 to parse API docs, generate boilerplate, and handle edge cases. If you code without AI, don't apply.

Technical Requirements

• 3+ years building production payment/banking integrations.
• Strong backend development skills (Java preferred, but we care more about integration expertise).
• Deep understanding of payment flows, settlement, and reconciliation.
• Experience with Open Banking/PSD2 standards.
• Event-driven architecture and distributed systems experience.
• Track record of building resilient, self-healing integrations.

Technical Environment

• Java backend services with AWS infrastructure.
• Event processing with EventBridge and Step Functions.
• Real-time streaming with Kinesis and SQS.
• Lambda for serverless webhook processing.
• Integration with AWS Bedrock for AI-powered reconciliation.

The Reality of This Role

• Parse wildly inconsistent data across 100+ providers.
• Handle multi-currency complexity and settlement timing issues.
• Build for 99.99% reliability when third-party APIs fail constantly.
• Reverse-engineer undocumented APIs when needed.
• Obsess over edge cases that affect 0.01% of transactions.

What Makes You Successful

• You're obsessed with data completeness – 99.9% isn't good enough.
• You understand that missing £0.01 is unacceptable in accounting.
• You build systems that self-heal rather than page you at 2am.
• You use AI to accelerate everything from API exploration to testing.
• You think in failure modes and edge cases.

The Opportunity

The accounting industry is a $88B market with data trapped in thousands of silos. Every business uses 5-10 different financial tools that don't talk to each other. Manual data entry costs billions in hours and errors.

This is your chance to build the connective tissue that makes autonomous accounting possible. Every integration you ship unlocks an entire market segment. A successful Shopify integration means 2 million merchants can automate overnight.

Why This Matters

You're not just moving data between systems. You're eliminating the most painful part of running a business. Every integration saves thousands of hours of manual work. Every edge case you handle prevents a business owner from panicking about missing money.

Interview Process

• Review of production integrations you've built
• Live coding session building an integration with AI assistance
• Architecture discussion on handling distributed transactions
• Deep-dive on your approach to reliability and error handling

What We Offer

• Competitive salary based on experience.
• Own the entire integration architecture.
• Process millions in real transactions daily.
• Work with our AI team to push reconciliation accuracy to 100%.
• Remote-first with quarterly team sprints.

To Apply

Show Us

• Payment or banking integrations you've built.
• How you use AI tools to accelerate integration development.
• Your approach to handling edge cases and failures.
• The worst API you've conquered.

If you think "good enough" integrations are acceptable, don't apply. If you're obsessed with capturing every transaction perfectly and making unreliable APIs bulletproof, let's talk