Ruby On Rails Backend Engineer

About the job

We're looking for an engineer who loves building reliable backend systems and is comfortable working close to production.

You write clean Rails code, understand data modeling and performance, and you can reason about operational reality: deployments, monitoring, scaling, and safe change management. You don't need to be a full-time infra engineer — but you do need to be someone who can jump into logs, dashboards, CI/CD, and production issues without fear.

Who we´re looking for

We're looking for an engineer who is comfortable owning production infrastructure for enterprise bank customers — and who treats security, reliability and compliance as core product requirements.

You are deeply hands-on in AWS and containerized environments, but you also think in threat models, controls and audit trails. You've operated systems that must pass formal due diligence (banks, fintech, payments, healthcare, or similar), and you can translate that reality into pragmatic security decisions without slowing the business unnecessarily.

You're methodical, proactive and allergic to "security theater." You build policies and controls that actually get adopted, reduce risk measurably, and stand up in audits.

Responsibilities

Backend Engineering (Ruby on Rails)

a. Build and own backend services and APIs for our mortgage origination SaaS (banks + internal ops).

b. Design and maintain domain models, business rules, validations, and workflows that are correct and auditable.

c. Build and maintain integrations with third parties (KYC/KYB, credit bureaus, document providers, banking services, etc.).

d. Implement background processing (Sidekiq/ActiveJob), idempotency, retries, and safe job orchestration.

e. Ensure strong engineering fundamentals: testing (RSpec), code review, refactoring, documentation, and maintainable architecture.

Data, Performance, Reliability

a. Own database design and performance (Postgres): indexing, query optimization, migrations, and data integrity.

b. Improve system performance and reliability: caching strategies, rate limits, timeouts, circuit breakers, and graceful degradation.

c. Define and track backend quality metrics: latency, error rates, queue health, and system throughput.

DevOps / Production Ownership

a. Participate in and improve CI/CD pipelines, release processes, and rollback strategies.

b. Contribute to our deployment/runtime environment (AWS + containers), including configuration, secrets usage, and environment hygiene.

c. Improve observability: logging, tracing, dashboards, and actionable alerting (not noise).

d. Participate in on-call / incident response (lightweight but real), with clear post-incident RCAs and preventive follow-ups.

Security-by-default (backend scope)

a. Implement secure patterns in application code: auth, authorization, audit logs, encryption practices, secrets handling, and safe data exposure.

Requirements

Must-have

• Strong professional experience building production systems with Ruby on Rails.
• Solid understanding of API design (REST/JSON), versioning, pagination, and error semantics.
• Experience with PostgreSQL (schema design, performance, migrations, data integrity).
• Experience with background jobs (Sidekiq/ActiveJob) and distributed-systems patterns (retries, idempotency).
• Good testing discipline (e.g., RSpec) and comfort shipping in a collaborative environment.
• DevOps fundamentals: comfort with Docker, CI/CD, reading logs/metrics, and debugging production issues.
• Experience running Rails in AWS (ECS/Fargate, EKS, or similar).

Nice-to-have

• Infrastructure-as-code familiarity (Terraform is a plus).
• Experience with observability tooling (Sentry, Datadog, CloudWatch, OpenTelemetry, etc.).
• Prior work in regulated or diligence-heavy environments (fintech, banks, payments, healthcare).

Soft skills

• High ownership and accountability
• Strong written communication and documentation
• Ability to explain risk and trade-offs clearly to technical and non-technical stakeholders
• Calm, structured incident handling and strong prioritization