Supercharge Your Career as a Senior Backend Engineer — Temporal & Python at Technoidentity!
Technoidentity — Durable Product Engineering®
Are you ready to solve people challenges that fuel business growth? At Technoidentity, we’re a Data+AI product engineering company building cutting-edge solutions in the FinTech domain for over 15 years—and we’re expanding globally. It’s the perfect time to join our team of tech innovators and leave your mark!
Role: Senior Backend Engineer — Temporal & Python
Experience: 8+ Years
About the role
You''ll build durable, long-running backend systems on Temporal for our Tier-1 clients — the kind of transaction-critical workflows that must survive failure, retries, deploys, and scale without losing state or correctness. This is a hands-on IC role for engineers who care about reliability as a first-class property, not an afterthought. Some engineers in this role will be staffed on high-bar client engagements where they''ll be evaluated against the client''s own senior engineering standards, so we hire people who can hold that line.
What you''ll do
- Design and implement Temporal workflows, activities, and workers in Python — modeling long-running, stateful processes (orchestration, sagas, human-in-the-loop, exception handling) as durable code.
- Own correctness under failure: idempotency, retries, timeouts, signals, queries, versioning, and safe deploys of in-flight workflows.
- Build and operate production Python backend services — APIs, async I/O, data access, integration with queues and datastores.
- Debug distributed-systems problems: race conditions, partial failures, non-determinism, replay mismatches.
- Write high-quality, well-tested, well-typed code and raise the bar in code review.
- Collaborate directly with client engineering teams and defend design decisions in technical discussions.
Must-have qualifications
- 5+ years building production backend systems, with strong recent Python (3.10+): async/await, typing, packaging, testing discipline.
- Solid CS fundamentals — data structures, algorithms, complexity — strong enough to pass a rigorous coding interview loop.
- Demonstrated distributed systems experience: concurrency, consistency, idempotency, message queues, at-least-once semantics, failure modes.
- System design ability: can design a scalable, fault-tolerant service end to end and reason about trade-offs out loud.
- Production ownership: has run services in prod, handled on-call/incidents, and cares about observability (logs, metrics, tracing).
- Strong written and verbal communication; can work in ambiguity and move fast without breaking correctness.
- Legally authorized to work in the US.
Temporal-specific (strongly preferred; we''ll also train the right person)
- Hands-on with Temporal (or equivalents like Cadence, AWS Step Functions, durable workflow engines).
- Understands the durable-execution model: determinism constraints, activity vs. workflow boundaries, signals/queries, durable timers, workflow versioning, worker scaling.
- Bonus: Temporal certification, contributions, or having run Temporal at scale in prod.
What makes a candidate stand out
- Clean, testable, idiomatic code and a high personal quality bar — reviewers rarely need to ask twice.
- Can decompose a vague, open-ended problem into a correct, incremental plan and explain reasoning clearly.
- Comfortable with performance work, profiling, and reasoning about systems under load.
- Genuine curiosity and fast learning — picks up unfamiliar codebases, tools, and domains quickly.
- Track record of shipping reliable systems in fast-moving, high-stakes environments.
Nice to have
- Cloud (AWS/Google Cloud Platform), containers/Kubernetes, CI/CD.
- Datastores at scale (Postgres, Redis, Kafka, etc.).
- Experience being embedded with or vendored into a demanding client engineering org.