Skip to content
CV Rocket
Get started
How it worksThe enginePricingBlogContactSign in

Open nowPosted 7 hours ago

Staff Backend Engineer (FDE)

Workable (global search)107,835 open roles

Where
Argentina
Work mode
Remote
Get the CV for this job

From $25 per CV, paid once. No subscription.

Your applicationOpen nowStaff Backend Engineer (FDE)Workable (global search) · Argentina

  1. YouYes, apply to this one.

  2. CV RocketCV written for this posting.

  3. 25 readersRecruiter, hiring manager, skeptic. Round after round.

  4. CV RocketApplied on Workable (global search)'s own form.

The reply lands in your private mailbox

3×more interviews than doing it yourself with ChatGPT.

The clock on this job

Early applications get read.

8.3% of postings close within 7 days. Measured by our own scanner across the market. Workable (global search) postings stay open a median of 4 days.

Share of postings closed within
  1. 1.9%1 day
  2. 4.0%3 days
  3. 8.3%7 days
  4. 15.3%14 days
  5. 34.2%30 days
This job: posted 7 hours ago

Workable (global search) median: 4 days open

The posting

Engineering, Platform

Full-time

About Meeru AI

Meeru AI is building an AI-native platform that transforms how finance and accounting teams operate. We connect to enterprise financial systems, including ERPs, CRMs, billing platforms, and HRIS, and apply machine learning to turn fragmented operational data into grounded, auditable intelligence for CFOs, controllers, and FP&A leaders.

We deploy on customer terms: SaaS multi-tenant, SaaS single-tenant, and on-premises, across AWS, Azure, and GCP. Our customers are Fortune 500 finance teams who require data isolation, auditability, and compliance.

The Role

The Staff Backend Engineer owns the application and API services layer: the services through which everything the platform computes actually reaches a person.

Multi-tenant APIs, authentication and authorization, and the review and approval workflows where a controller accepts a result, challenges it, or sends it back. The computation layer produces the numbers. This layer is where a finance team sees them, interrogates them, approves them, and acts on them.

That means your services carry the same correctness and auditability requirements as the computation beneath them, plus the access control and tenancy guarantees that let a Fortune 500 finance organization trust the platform with their close cycle.

Every action taken through your services is part of an audit trail that sits next to externally reported financials. Who approved what, when, on the basis of which underlying result, and what changed afterward. That is not logging you add later. It is a product requirement, and it shapes how the services are designed from the first commit.

This is hands-on and high-ownership. You own major services end to end, set backend patterns alongside the Senior Staff engineers, and partner with data, AI, and product on the contracts between layers.

Key Responsibilities

1. Own the multi-tenant APIs through which the platform's results are consumed. Design the service contracts between the application layer and the computation, data, and AI layers, and own the versioning discipline that lets those contracts evolve without breaking consumers who cannot all move at once.

2. Build the review, approval, and exception-handling workflows finance teams operate in. This is where the product either earns trust or loses it. A controller who cannot see why a number is what it is will not approve it, and will not use the platform twice.

3. Build and maintain multi-tenant isolation at the service layer. Own authentication, authorization, and role-based access across the application surface. Cross-tenant leakage should be impossible by construction rather than prevented by convention.

4. Build the audit trail. Who saw what, who approved what, on the basis of which result. Guarantee that every user-facing figure links back to its computation and its source, and support the enterprise security and compliance reviews Fortune 500 finance customers run before they buy.

5. Build for a multi-cloud-ready, multi-tenant-ready, customer-hosted deployment model. Services that run inside a customer's environment with strong isolation and no data egress.

6. Own performance, reliability, and cost of the services you build, including observability and operational health. You should be able to answer why a request is slow rather than guessing.

7. Set backend patterns, review designs, and mentor mid and senior engineers. Partner with data, AI, and product on cross-layer service design.

A note on accountability: this role owns the application and API services, tenancy and access control, and the audit trail. It does not own the core computation layer, the data foundation, the AI layer, or product prioritization.

Requirements

Seven or more years in backend forward deployment engineering, with significant Staff-level time owning complex production services. Owning them, including what happens when they fail.

  • Demonstrated ownership of services in a multi-cloud SaaS environment, and a clear account of how you guaranteed isolation rather than assumed it.
  • An obsession with correctness and traceability. You treat "who did what, when, and on what basis" as a first-class requirement rather than an audit checkbox.
  • Strong API and service design, including versioning, contracts, and backward compatibility. You have evolved an interface other teams depended on without breaking them.
  • Practical security engineering: authentication, authorization, and tenant isolation. Not theory.
  • Python
  • FastAPI, Django, or Flask; PostgreSQL and Redis;
  • REST API design; Docker, Kubernetes, and Terraform
  • SQL against Snowflake or PostgreSQL.

Nice to Have

  • Finance, accounting, or fintech domain, or a genuine willingness to learn how financial statements are built and reconciled.
  • Multi-tenant, customer-hosted deployment at scale.
  • Supporting SOC 2 or ISO 27001 review.
  • Building auditable systems in a regulated environment.
  • Exposure to ML or LLM application patterns, enough to integrate them well.
From $25, paid onceGet the CV for this job

What happens when you press

One press. We do the rest.

  1. A CV for this posting

    Written against Workable (global search)'s own wording, from every piece of relevant proof in your profile.

  2. 25 readers review it

    Recruiter, hiring manager, skeptic and more read every draft, round after round. You get the best round.

    The review screen in CV Rocket: how each CV was read, round by round.

  3. We apply on Workable (global search)'s form

    Our application engine gets through the hardest forms there are. Where a question needs you, AI suggests the best answer. Don't want us applying from our IP addresses? Use our Chrome extension: we apply straight from your own browser.

    An application in CV Rocket: every answer filled in on the employer's form.

  4. Every reply, sorted

    Workable (global search)'s answer lands in your private mailbox, and we classify it on arrival: interview, question, rejection.

    The CV Rocket inbox: each employer reply classified as an interview, an action or a rejection.

  5. Reply with AI

    AI helps you write the email, checks it and sends it. We show you whether the recruiter read it.

  6. The interview in your calendar

    Full integration with your calendar. The invitation goes straight in.

    An interview invitation in the CV Rocket inbox, added to the candidate's calendar.
Get the CV for this job

From $25 per CV, paid once. No subscription.

Why it works

3×

more interviews than doing it yourself with ChatGPT.

ChatGPT writes a CV and never learns what happened to it. We see every reply. For each CV we know:

  • How it was written, and how the review scored it
  • When we applied, and how long after the posting went up
  • Which posting, which company, which city
  • Who got the interview, and who heard nothing

That is how we know which CVs get called.

Get the CV for this job

From $25 per CV, paid once. No subscription.

The numbers game

More applications. More interviews.

Every application goes out with its own CV, written for that posting and paid once. Send enough of them and the law of large numbers finds you the job.

Get the CV for this job
By hand5–10
With CV Rocket100
applications a day

Nearby

Live postings like this one

Same employer first, then the same role elsewhere.

Before you press

Straight answers

Get the CV for this job

From $25 per CV, paid once. No subscription.

What if my background isn't good enough?

We make the most of the background you have. The CV uses every piece of relevant proof your profile holds, and one of the 25 readers reads your whole profile and flags what the CV left out.

Do you really apply for me?

Yes, on the employer's own form, the hardest ones included. Where a question needs you, you answer it right there and AI suggests the best answer. Don't want us applying from our IP addresses? Use our Chrome extension: we apply straight from your own browser.

Is it a subscription?

No. You pay once per CV, from $25. Every application goes out with its own CV, written for that posting.

One job. One CV.
Paid once.

Pick the posting you want. We write for it, apply for you and catch the reply.

Get the CV for this job

From $25 per CV, paid once. No subscription.