Principal Backend Engineer, Performance, Database

Job not on LinkedIn

🔥 12 hours ago

🇵🇰 Pakistan – Remote

⏰ Full Time

🔴 Lead

🔙 Backend Engineer

👻 Ghost score 11%

What it means: how likely this posting is sitting open without active hiring.How to read it: 60% or higher means we think this is a ghost. Lower scores are less of a worry.How we score it: age, reposts, open roles vs team size, how fast jobs close, and whether pay is listed.Fine print: an estimate from public data, not a judgment of the company. Real jobs can score high, so treat it as a hint, not a fact.

Apply Now

Find Similar Remote Jobs

Set Up Email Alert For New Jobs

📊 Check your resume score for this job

Improve your chances of getting an interview by checking your resume score before you apply.

Upload Resume

iClosed

WebsiteLinkedInAll Job Openings

51 - 200 employees

Founded 2022

💼 Consulting

📣 Marketing

☁️ SaaS

Consulting • Marketing • SaaS

iClosed is a SaaS scheduling and lead-capture platform designed for high-ticket sales teams. It captures leads before showing booking availability, qualifies and disqualifies prospects, conditionally routes invites to the right closers, automates SMS/email follow-ups, and tracks calls and conversions by channel. iClosed integrates with CRMs, ad platforms (Meta/Hyros), and thousands of apps, and adds features like credit-score enrichment to ensure only buyers reach calendars and improve close rates.

📋 Description

• Own the performance and scalability of backend systems and the underlying data layer • Design request flows, synchronous versus asynchronous work, state placement, dependency behavior, and scalable service boundaries • Diagnose latency and performance issues using traces, execution plans, metrics, and evidence • Establish instrumentation, review standards, and regression gates to prevent customer-visible problems • Design strategies for read scaling, write scaling, read/write separation, background processing, real-time updates, traffic spikes, high availability, reliability, search, data growth, safe changes, and API efficiency • Review feature-team architecture proposals • Write design documents and decision records for other engineers to build from • Select and optimize relational, document, key-value, and in-memory data stores based on workload and access patterns • Diagnose execution plans, index costs, lock contention, connection pooling, replica lag, partitioning, document aggregation, shard keys, hot partitions, cache behavior, and dual-write issues • Diagnose latency across the full request path, including ORM-generated traffic, synchronous and ETL latency, and third-party integrations • Own data-layer capacity planning and cost per request alongside latency • Introduce design and query reviews for hot paths and data-layer changes • Define standards for migrations, index justification, and work that must not run synchronously • Instrument data access in application traces • Contribute CI regression gates and production-realistic load testing • Investigate performance for the largest customer accounts and per-tenant behavior • Join the escalation on-call rota once established

🎯 Requirements

• 5+ years building and operating production backend systems • 3+ years with performance and scale as a named part of the job • Experience owning performance for a multi-tenant SaaS product under real load • Evidence of designing systems, including rejected alternatives, accepted tradeoffs, and lessons learned • Specific track record diagnosing a performance problem, identifying its cause, implementing a fix, and measuring results • Ability to reason about caching, replicas, indexes, invalidation, staleness, sharding, partitioning, batching, queue buffering, replica routing, CQRS, queues, workers, orchestration, idempotency, dead letters, WebSockets, SSE, long polling, load balancing, autoscaling, headroom, load shedding, replication, failover, degraded operation, timeouts, backoff, circuit breakers, dedicated search indexes, archival, retention, canary deployments, feature flags, online migrations, logs, metrics, traces, and alerts • Ability to write design documents that teams can implement and executives can follow • Deep experience in at least two of relational, document, key-value, and in-memory stores, with working competence across the others • Relational database expertise including execution plans, composite and partial indexes, index write cost, locking, isolation levels, connection pooling, and replica lag • Document database expertise including embedding versus referencing, shard-key selection, aggregation performance, and working-set sizing • Key-value database expertise including access-pattern modelling, partition keys, hot-partition avoidance, secondary indexes, and capacity cost • Cache expertise including caching patterns, eviction, TTL, and cold-cache or cache-loss behavior • Understanding of consistency boundaries and recognizing when a query problem is an application-design problem • Production ownership in multiple backend languages • Understanding of ORM and ODM query generation • Experience with concurrency, connection and resource management under load • Experience with queue design, including handling consumers that fall behind • Experience using APM and tracing tools for diagnosis • Production experience on a major public cloud, including managed data-service cost behavior • Ability to instrument code for future diagnosis

🏖️ Benefits

• Full-time, permanent employment • Remote work arrangement • High autonomy and significant technical influence • Opportunity to shape backend architecture and performance standards • Potential future leadership opportunity if the function grows and the candidate wants to lead it