Software Engineer, Backend - Core/API & Process Automation
Jobgether
—
Jul 19, 2026
—
Jul 22, 2026
What this job asks for AI summary
A backend engineering role focused on building and maintaining distributed workflow and process automation systems at enterprise scale. Day-to-day work spans event-sourced workflow engines, API design, CQRS and event-driven patterns, performance optimization, and observability. The role suits a backend engineer with at least two years of experience who is comfortable working asynchronously in a remote team and wants meaningful ownership over complex, scalable systems.
Mid level · 2+ years · Remote · Full-time
“or” means any one of them counts — you don't need all of them.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Roughly 62,000 people nationally plausibly meet what this posting asks for (software developers). range 18,200–93,000
Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.
Rare in this occupation — lead with these, and say what you built with them.
What the occupation pays Median $138,970 (middle half $107,524–$175,762).
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (5)
Although the posting states 'based in United States', the Benefits section explicitly states 'Fully remote work environment with flexibility to work from anywhere in India', indicating the actual target location is India. The US-based flag has been set to false accordingly.
The title carries no seniority level word; the title states no level. The 2+ years requirement and scope of work (contributing to, not leading, distributed systems) support a Mid-level classification.
BPMN and workflow automation experience are explicitly called 'an asset' (preferred). Elasticsearch/OpenSearch and PostgreSQL are explicitly 'preferred'. JVM and observability are explicitly 'a plus' or 'an advantage'.
Event-driven architecture, distributed systems, CQRS, event sourcing, and REST API design are all stated in the Requirements section as core expectations and are marked as required. However, the JD uses interest-based framing ('experience or strong interest') for some of these — they are still listed under Requirements and treated as hard gates.
No compensation figures are provided; only a 'competitive compensation package based on location, experience, and qualifications' is mentioned.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.