Reppls
Senior Software Engineer (Core Platform)
Join to apply for the
Senior Software Engineer (Core Platform)
role at
Reppls
Hiring for a client of Recrucial — a long-term Legal tech & fintech SaaS transformation project.
Our client is building a next‑generation multi‑tenant data & automation platform that powers mission‑critical workflows for legal and financial services. They have a validated R&D prototype and are now entering the product‑building phase. You will join the core engineering team responsible for turning the prototype into a scalable, performant platform used globally.
The Mission You will help transform a working R&D prototype into a production‑ready, multi‑tenant SaaS platform. As part of the Core Platform team, you will own the foundational components — the Core API, billing/metering logic, developer tooling, and the runtime that powers distributed data‑collection jobs.
Your work directly enables Delivery Teams to build new data‑automation modules 10× faster.
What You Will Build (Ownership) Core API & Runtime
Evolve the Job API and execution flow.
Design how scraper artifacts are packaged, versioned, deployed and executed across the Edge environment (Cloudflare Workers / R2).
Contribute to the long‑term runtime evolution as some components move from Python to Java for performance.
Business Logic Layer
Implement the core “boring but critical” logic of a SaaS platform:
Tenant isolation
Developer Experience Tooling
Build internal tools that developers depend on every day:
CLI tools
Management UI
Automation helpers - If internal tooling slows people down, this team owns the fix.
Collaborate with the Principal Architect on platform‑wide technical decisions.
Participate in major migrations (e.g., Python → Java for specific workloads).
Shape standards for API design, schema migrations, service boundaries, and long‑term maintainability.
Who We Are Looking For A Senior Engineer with Strong Engineering Judgment
Deep experience in backend development (Python preferred; Java or TypeScript exposure is a plus).
Ability to design reliable distributed workflows, think in terms of retries, idempotency, and state.
Someone who builds systems that survive versioning, migration, and growth.
A System Thinker
You don’t just write endpoints — you think about the lifecycle of an API, how customers depend on it, and how it evolves without breaking them.
You understand database migrations, schema versioning, and multi‑tenant constraints.
Autonomy & End‑to‑End Ownership Give this person a one‑line requirement such as: “We need to charge tenants per successful scrape.” They can design it, validate it, implement it, test it, and bring it to production.
Core
Python (FastAPI)
Platform
Docker
Nice to have
Java (for future high‑performance modules)
Experience with multi‑tenant SaaS architectures
Understanding of retry strategies, distributed systems, and API versioning
Interview Process
Resilient Coding (Practical)
What to expect:
You will work through a real‑world coding task: building a client that interacts with an unreliable third‑party service. This round evaluates your ability to design resilient logic — retries, backoff strategies, error handling, and state management. This is not an algorithmic round.
How to prepare:
Review async/await in Python
Understand retry patterns (exponential backoff, jitter)
Recommended reading: “Designing Data‑Intensive Applications”
System Design (Platform‑Level)
What to expect:
You will be asked to design a subsystem of the platform — for example, a multi‑tenant metering mechanism or a distributed job‑execution layer. The focus is on trade‑offs, modeling, and scaling, not drawing boxes.
How to prepare:
Review system design fundamentals (e.g., ByteByteGo–style content)
Pay attention to multi‑tenant systems, quotas, and billing
Refresh database modeling and lifecycle planning
Methodologies & Architecture
What to expect:
A conversational deep‑dive into your architectural decision‑making.
Topics often include:
Refactoring large systems & evolutionary architecture
Handling technical debt in a pragmatic, long‑term way
How to prepare:
Think of examples where you refactored significant parts of a codebase
Review Clean Architecture, DDD concepts, and migration strategies
What This Role Is Not
Not a “feature factory” environment
Not a place for algorithmic interviews
Not a role where architecture is dictated from above — you shape it
Why This Project Is Exciting
You’re building the foundation of a brand‑new SaaS platform, not maintaining legacy code.
You will work with a Principal Architect who drives innovation and deeply understands the Edge‑compute landscape.
You influence architecture, tooling, and developer experience across the entire engineering organization.
You join at the stage where your decisions truly shape the product’s future.
Seniority level Mid‑Senior level
Employment type Full‑time
Job function Software Development
#J-18808-Ljbffr
Senior Software Engineer (Core Platform)
role at
Reppls
Hiring for a client of Recrucial — a long-term Legal tech & fintech SaaS transformation project.
Our client is building a next‑generation multi‑tenant data & automation platform that powers mission‑critical workflows for legal and financial services. They have a validated R&D prototype and are now entering the product‑building phase. You will join the core engineering team responsible for turning the prototype into a scalable, performant platform used globally.
The Mission You will help transform a working R&D prototype into a production‑ready, multi‑tenant SaaS platform. As part of the Core Platform team, you will own the foundational components — the Core API, billing/metering logic, developer tooling, and the runtime that powers distributed data‑collection jobs.
Your work directly enables Delivery Teams to build new data‑automation modules 10× faster.
What You Will Build (Ownership) Core API & Runtime
Evolve the Job API and execution flow.
Design how scraper artifacts are packaged, versioned, deployed and executed across the Edge environment (Cloudflare Workers / R2).
Contribute to the long‑term runtime evolution as some components move from Python to Java for performance.
Business Logic Layer
Implement the core “boring but critical” logic of a SaaS platform:
Tenant isolation
Developer Experience Tooling
Build internal tools that developers depend on every day:
CLI tools
Management UI
Automation helpers - If internal tooling slows people down, this team owns the fix.
Collaborate with the Principal Architect on platform‑wide technical decisions.
Participate in major migrations (e.g., Python → Java for specific workloads).
Shape standards for API design, schema migrations, service boundaries, and long‑term maintainability.
Who We Are Looking For A Senior Engineer with Strong Engineering Judgment
Deep experience in backend development (Python preferred; Java or TypeScript exposure is a plus).
Ability to design reliable distributed workflows, think in terms of retries, idempotency, and state.
Someone who builds systems that survive versioning, migration, and growth.
A System Thinker
You don’t just write endpoints — you think about the lifecycle of an API, how customers depend on it, and how it evolves without breaking them.
You understand database migrations, schema versioning, and multi‑tenant constraints.
Autonomy & End‑to‑End Ownership Give this person a one‑line requirement such as: “We need to charge tenants per successful scrape.” They can design it, validate it, implement it, test it, and bring it to production.
Core
Python (FastAPI)
Platform
Docker
Nice to have
Java (for future high‑performance modules)
Experience with multi‑tenant SaaS architectures
Understanding of retry strategies, distributed systems, and API versioning
Interview Process
Resilient Coding (Practical)
What to expect:
You will work through a real‑world coding task: building a client that interacts with an unreliable third‑party service. This round evaluates your ability to design resilient logic — retries, backoff strategies, error handling, and state management. This is not an algorithmic round.
How to prepare:
Review async/await in Python
Understand retry patterns (exponential backoff, jitter)
Recommended reading: “Designing Data‑Intensive Applications”
System Design (Platform‑Level)
What to expect:
You will be asked to design a subsystem of the platform — for example, a multi‑tenant metering mechanism or a distributed job‑execution layer. The focus is on trade‑offs, modeling, and scaling, not drawing boxes.
How to prepare:
Review system design fundamentals (e.g., ByteByteGo–style content)
Pay attention to multi‑tenant systems, quotas, and billing
Refresh database modeling and lifecycle planning
Methodologies & Architecture
What to expect:
A conversational deep‑dive into your architectural decision‑making.
Topics often include:
Refactoring large systems & evolutionary architecture
Handling technical debt in a pragmatic, long‑term way
How to prepare:
Think of examples where you refactored significant parts of a codebase
Review Clean Architecture, DDD concepts, and migration strategies
What This Role Is Not
Not a “feature factory” environment
Not a place for algorithmic interviews
Not a role where architecture is dictated from above — you shape it
Why This Project Is Exciting
You’re building the foundation of a brand‑new SaaS platform, not maintaining legacy code.
You will work with a Principal Architect who drives innovation and deeply understands the Edge‑compute landscape.
You influence architecture, tooling, and developer experience across the entire engineering organization.
You join at the stage where your decisions truly shape the product’s future.
Seniority level Mid‑Senior level
Employment type Full‑time
Job function Software Development
#J-18808-Ljbffr