Senior Backend Engineer
About the role
- Design the core EAV data model & schema-as-code platformthat powers every customer's instance, balancing extreme flexibility with transactional integrity.
- Build a Git-style version-control + migration enginecapable of rolling forward/back complex schema and data changes on live production tenants in enterprise settings.
- Engineer AI-assisted toolingthat uses foundation models to propose, validate, and apply new customer schemas and workflow definitions.
- Scale our white-labeled data warehouse(BigQuery/Snowflake-like) for high-volume, low-latency analytics and automation workloads.
- Create Terraform-like declarative APIs & SDKsso ops teams can treat business processes as code while you ensure security, tenancy, and performance.
- Deliver end-to-end observability & searchacross supply-chain, finance, and ops data—surfacing business logic in plain language through AI-native search.
- Build Enterprise guard railsinto a composable system to proactively detect anomalous behavior or risky emergent patterns
- Mentor and shape engineering culture, partnering with product and design to turn unsexy back‑office pain into elegant, resilient systems loved by operators.
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.
