Senior Software Engineer at Hire Fellows

Hire Fellows; Manama; On-site; BHD 30,000 - 45,000; Full time

Job summary

Hire Fellows seeks a senior software engineer to own subsystems that power a multi-tenant platform. You will design, deliver, operate in production, and drive reliability metrics while mentoring junior engineers to take ownership of their work.

You will work on distributed systems with a focus on TypeScript (Node.js) and Python, operate in cloud environments with Kubernetes, and uphold security-conscious design as you scale the platform for many customers.

Qualifications

• Six or more years of professional software engineering experience, with at least two in a senior or lead capacity on a production system.
• Experience designing and operating systems at scale with measurable metrics (throughput, latency, availability).
• Strong TypeScript on Node.js and Python, with good judgment on when to use each.
• Cloud and Kubernetes fluency; production services on Kubernetes.
• Production ownership: incident response, post-incident reviews, and follow-through.

Responsibilities

• Own one or more subsystems that keep the platform running under load, including design, delivery, production operation, and reliability metrics.
• Mentor associate engineers toward ownership and high engineering standards.
• Drive architectural ownership and be able to defend choices in a high-bar, fast-paced environment.

Job description

The platform runs automated analysis and gives our operations teams the tools to reach and act on decisions.

The platform serves many customers from a single deployment, so every pipeline stage has to hold up under strict tenant isolation, bursty traffic, third-party rate limits, and partial failure. The engineering problems are, first and foremost, distributed systems problems. The team is small and senior in outlook. Engineers ship to production, own what they ship, and work directly with the operations teams who use the product every day. We hire for engineering quality above everything else. You will own one or more of the subsystems that make the platform work under load. Ownership means the design, the delivery, the production operation, and the reliability numbers. We need someone who has already done this elsewhere: you designed a system that many people depended on, watched it break at scale, and rebuilt the parts that broke. You can hold a room of engineers to a high bar without slowing them down, and you will be expected to mentor associate engineers toward ownership of their own.

Role Requirements

• Six or more years of professional software engineering, including at least two in a senior or lead capacity on a production system.
• You designed and operated a system at scale. Be ready to give the numbers: throughput, data volume, tenants or users, latency percentiles, availability. Be ready to tell us what broke, what it cost, and what you changed.
• Distributed systems depth: queues and streams, workflow engines, retries and idempotency, consistency trade‑offs, partial failure, backpressure, observability.
• Strong TypeScript on Node.js and strong Python, with the judgment to know which to use where, and comfort reading and fixing code in either.
• Cloud and Kubernetes fluency. You have run services on Kubernetes in production.
• Production ownership. You have defined service‑level objectives, led incident response, run blameless post‑incident reviews, and driven the follow‑through.
• A proven record of excellence, evidenced by several of: promotions ahead of the typical cadence; ownership of a system critical to your employer's business; public work such as talks, papers, patents, or open‑source projects with real users; a reputation among former colleagues we can verify by reference; a measurable outcome you drove, such as an order‑of‑ magnitude cost, latency, or reliability improvement.
• A security mindset. You have shipped systems where the threat model mattered, treat tenant isolation as a security boundary rather than a configuration, and design for the case where the input is hostile.

Built and operated multi‑tenant platforms where isolation of data and credentials was a hard requirement. Deep experience with a durable‑execution or workflow engine, or with a streaming platform, at scale. Integrated with security tooling APIs and know their rate limits and quirks by heart. Graph databases, and familiarity with open security data standards for events and threat intelligence. Hands‑on experience defending production systems, as an engineer or in an operations role. Productionized machine‑learning or language‑model components with a proper evaluation discipline.

Useful, not required: this is a software engineering role. This is a hands‑on senior engineering role, not a management position, with architectural ownership and mentoring responsibilities.