Key Responsibilities
Design and Engineering
Design, develop, and maintain backend services, APIs, and data integration layers that power key product features.
Author design documents (EDDs) for services in the domain and defend them in review.
Design and optimize database schemas and queries for performance and system reliability.
Meet project goals without trading away quality, and pay down technical debt as part of delivery rather than as a separate request.
Serve as the go-to person for one or more technologies in the domain, following industry developments and explaining concretely how they would or would not apply at Tala.
Quality, Review, and Standards
Hold the domain's engineering bar in code and design reviews, including for work from other technical teams.
Write clean, maintainable code that follows established coding standards.
Contribute to the testing infrastructure to increase coverage for backend modules.
Verify AI-assisted changes to the same standard as hand-written code.
Reliability and Operations
Define alerting, SLIs, and SLOs, and advance monitoring of backend modules so availability and response times improve proactively.
Handle incidents that the runbook does not cover, fill runbook gaps found during a shift, lead the technical response for domain incidents, and write the RCA.
Troubleshoot and resolve technical issues quickly across development and production environments.
Delivery and Collaboration
Own delivery of domain roadmap work and take part in quarterly and sprint planning with a view on feasibility.
Anticipate blockers before sprint commitment, and escalate with a problem statement, an impact assessment, and proposed options.
Work with Product and business stakeholders to remove ambiguity and to understand what success means for a feature.
Work with the team lead to deliver domain solutions, and own service design and implementation end to end, including regressions you introduce.
Keep the domain's tickets accurate and its documentation complete enough that it is the first place people look.
Work across multiple time zones using asynchronous communication.
Mentorship
Act as a dedicated mentor to junior and mid-level engineers, with a clear sense of what each is working to improve.
- Technically lead and mentor a team of Backend Engineers building or extending complex modules.
- Required Skills and Experience
- Language: Fluency in English, including clear written communication, which is how most work happens across time zones.
Backend engineering: Hands-on experience designing, building, and operating applications in Java, Kotlin, and/or Scala, including a web framework such as Spring.
Track record: Has led and delivered multiple domain-significant projects, each validated in production over a meaningful period, including large scale consumer applications on cloud infrastructure (AWS, Google Cloud, or Azure) using microservices architecture.
Technical expertise: Subject-matter expert in their own domain and conversant in adjacent ones. Maintains a working mental model of the wider company architecture and where the seams are. Assesses code and design quality beyond their own area.
Solution building and system design: Designs services and their dependencies with security, maintainability, operability, and scale accounted for. Authors design documents (EDDs) and defend them in review. Designs for failure cases, not just the happy path.
API design: Expert knowledge of REST API design and development for mobile and web use.
Judgment and problem framing: Reframes poorly posed problems instead of answering them as asked. Decides with incomplete information and states the assumptions relied on. Distinguishes reversible from irreversible decisions and applies rigor accordingly. Choose the smallest solution that solves the problem.
Data stores: Strong relational database experience (MySQL, MariaDB, PostgreSQL, Oracle, or MS SQL) and strong non-relational database experience (Cassandra, Redshift, DynamoDB, or HDFS).
Testing and observability: Defines alert thresholds, SLIs, and SLOs for the domain along with the telemetry that supports them. Designs for graceful degradation. Ships new features with monitoring already in place. Co-owns Acceptance Tests coverage decisions with SDET and flags testability gaps before release.
Security and compliance: Follows Tala's security and privacy practices in line with ISO-27001 and ISO-27701, follows OWASP secure coding practices, and remediates vulnerabilities within established SLAs.
AI fluency: Knows when not to delegate to AI and decomposes domain work into agent-sized units with explicit acceptance criteria. Builds reusable context assets, prompts, and skills that others in the domain adopt. Sets the verification bar for the domain's AI-assisted work. Is accountable for AI-generated code as if it were hand-written, and never puts PII, borrower or credit data, secrets, or production credentials into a prompt or agent context.
Delivery and impact: Owns delivery of domain roadmap work and balances feature velocity against technical debt deliberately. Owns an outcome rather than a task list, knows which metrics their systems move, and watches them after release.
Ways of working: Expert proficiency in the Agile development process. Prioritizes and communicates well in a fast-paced environment. Strong drive for independent learning and work.
