Senior Software Engineer

The Opportunity

We are hiring Software Engineers with 3–4 years of experience who are ready to take meaningful ownership of backend systems and work with minimal supervision.

This role is designed for engineers who have moved beyond writing features under guidance and are now ready to own them end-to-end — from design to production. You will be expected to make sound technical decisions, debug complex production issues independently, and contribute to how our systems scale and stay reliable.

If you care about how software behaves under load, how data stays consistent under failure, and how systems recover gracefully — this role is for you.

You will work closely with product managers, designers, and other engineers to build systems that are scalable, maintainable, and production-ready. Your daily work will involve:

• Ensuring Data Integration with Third-Party CRMs: Design and own solutions that integrate customer data seamlessly and reliably with various CRM systems.

• Enhancing Event and Fundraising Management Tools: Drive improvements to our event and fundraising tools, with a focus on reliability and scale.

• Owning Payment and Communication Systems: Take end-to-end ownership of systems that handle payments and user communications, including resilience and failure handling.

• Maintaining and Improving System Uptime: Lead reliability efforts in your areas of ownership, proactively identifying and resolving issues before they impact customers.

Responsibilities

• Own Features End-to-End: Design, build, and maintain features independently — from requirements to production — with minimal supervision.

• Drive System Reliability: Proactively identify performance bottlenecks, reliability risks, and scalability gaps and address them systematically.

• Debug Production Issues Independently: Investigate and resolve complex production issues using logs, metrics, and structured debugging approaches.

• Code Review and Quality: Conduct and participate in code reviews, raise the quality bar, and help define good engineering practices within the team.

• Collaborate Cross-Functionally: Work closely with product managers, designers, and other engineers to deliver high-quality software that meets user needs.

• Contribute to Architecture: Participate actively in design discussions, propose solutions to technical problems, and think through trade-offs clearly.

• Continuous Improvement: Stay current with engineering best practices and apply that knowledge to improve the systems you own.

Requirements

Must-Have

• 3–4 years of full-time software engineering experience

• Hands-on experience with backend development in Java, Python or Go

• Experience with frontend development using React or similar frameworks

• Strong understanding of HTTP, REST APIs, and client–server architecture

• Experience designing data models and writing complex SQL queries

• Proven ability to build and own distributed systems or microservices in production

• Experience designing APIs and backend systems for scale

• Ability to debug and resolve complex production issues independently

• Hands-on experience with performance tuning — query optimisation, caching strategies, and async processing

• Experience using Git, writing tests, and participating in code reviews

• Comfortable working with minimal supervision and taking ownership of outcomes

Good-to-Have

• Experience with Redis or similar in-memory data stores for rate limiting, caching, or queuing

• Familiarity with observability tools — metrics, distributed tracing, alerting (e.g. Datadog, Sentry, Prometheus)

• Exposure to database sharding, partitioning, or replication

• Experience with background job systems, message queues, or event-driven architecture (e.g. Celery, RabbitMQ, SQS)

• Prior experience in a SaaS product environment

• Curiosity about how systems fail at scale and how to design around those failure modes

What Does Your 1st Year Look Like at Almabase?

First 3 Months

• Ramps up quickly on the codebase, systems, and architecture

• Delivers well-scoped features independently with minimal hand-holding

• Identifies gaps or risks in existing systems and raises them proactively

• Establishes credibility through reliable, high-quality output

3–6 Months

• Owns complete features or workflows end-to-end, from design to production

• Debugs production issues independently using logs, metrics, and systematic reasoning

• Improves reliability and performance in areas they own

• Contributes meaningfully to technical design discussions

6–12 Months

• Drives architecture and design decisions for their domain with confidence

• Leads incident reviews and contributes to post-mortem culture

• Reduces technical debt and improves maintainability across their areas

• Acts as a technical reference point for junior engineers on their team