Senior Software Engineer

Level: Senior software engineer with 5–10 years of experience building and shipping production web applications, ideally in a full-stack role.

Required skills: Rails, TypeScript, React, Next.js, SQL, automated testing with tools such as RSpec, Vitest, and Playwright, AI coding tools, API design, authentication, authorization, caching, background processing, and strong cross-functional communication.

Familiar tasks: Owning large initiatives end to end, designing and delivering maintainable production-ready features, collaborating with product and design teams, writing tests across the stack, and working with CI/CD, cloud infrastructure, observability, or fintech systems.

How would you design and implement a large full-stack feature from requirements through production release?

I would clarify requirements and success metrics, design the API and data model, break the work into incremental deliverables, and implement the Rails and Next.js components with automated tests. I would use code review, CI/CD, observability, and a controlled rollout to validate the feature in production.

How would you structure a Rails application to keep domain logic maintainable as the product grows?

I would keep controllers thin, use well-defined domain services or command objects for complex workflows, and enforce clear boundaries between persistence, business rules, and integrations. I would also document important invariants and cover them with focused unit and integration tests.

How would you design a GraphQL API for financial advisor and client data?

I would model the schema around clear domain concepts, enforce authorization at the resolver or service layer, and use pagination, filtering, and explicit field selection to control query cost. I would address N+1 queries with batching, define consistent error behavior, and avoid exposing sensitive fields by default.

How do you implement authentication and authorization in a multi-tenant wealth management platform?

Authentication verifies identity using secure sessions or tokens, while authorization determines access based on tenant, user role, ownership, and resource-level policies. I would centralize policy checks, apply defense in depth at the API and database boundaries, and test cross-tenant access scenarios explicitly.

How would you use background jobs for long-running financial data integrations?

I would make jobs idempotent, retryable, and observable, with explicit handling for transient versus permanent failures. I would use queues and status tracking so users receive accurate progress information, while protecting external services through rate limits and exponential backoff.

What caching strategies would you consider for a React and Rails application?

I would cache data that is expensive to compute and safe to reuse, using HTTP, application-level, or query-result caching depending on the access pattern. For financial data, I would define strict expiration and invalidation rules to prevent stale or unauthorized information from being displayed.

What is your approach to testing a feature across RSpec, Vitest, and Playwright?

I use unit tests for business logic, integration tests for APIs and persistence, and end-to-end tests for critical user workflows. Tests are written as part of implementation, with deterministic fixtures, meaningful assertions, and enough coverage to protect behavior without making the suite unnecessarily brittle.

How do you review and validate code generated by Claude Code or Cursor?

I treat AI-generated code exactly like code written by a developer: I verify its assumptions, security implications, edge cases, and consistency with existing architecture. I run the relevant tests, add missing tests, inspect database and API changes, and keep only code I can fully explain and maintain.

How would you design a secure financial data integration with an external provider?

I would isolate credentials in a secrets manager, use encrypted transport and storage, validate provider responses, and minimize the data retained and exposed. The integration should support idempotency, audit logging, retries, reconciliation, and clear monitoring for failures or unexpected data changes.

What would you monitor in production for a critical advisor-facing application?

I would monitor latency, error rates, throughput, background-job health, database performance, cache behavior, and key business workflows using tools such as Datadog. I would add structured logs, traces, actionable alerts, and dashboards that help distinguish infrastructure issues from application or integration failures.

Savvy Wealth is a fast-growing, AI-native wealth management company reinventing how independent financial advisors serve their clients. As a Senior Software Engineer, you’ll own large initiatives end to end, collaborate across product and design, and ship reliable, production-ready features. Work remotely across Latin America using Ruby on Rails, TypeScript, React, Next.js, SQL, GraphQL, RSpec, Vitest, Playwright, and AI coding tools. Savvy offers a competitive salary and equity package, unlimited PTO, comprehensive benefits, and the chance to build high-impact fintech products at a Series C company with $200M raised.