> Markdown version of [/jobs/ext/4583038-senior-software-engineer-remote](https://www.wearedevelopers.com/jobs/ext/4583038-senior-software-engineer-remote). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Senior Software Engineer (Remote) - **Company:** LTD Global - **Location:** United States (Remote available) - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Query Performance, Software Bug Management, Relational Databases, Programming Tools, Python (Programming Language), PostgreSQL, MySQL, Web Services, Large Language Models, Software Coding - **Published:** November 5, 2026 - **Apply:** https://arc.dev/remote-jobs/j/redirect/pwttyz9ifr ## About the Role * Eight or more years building and operating web services, or fewer with clear evidence of senior-level ownership. * Depth in at least one dynamic language. Python preferred but definitely not required. * Experience in relational database schema design, query performance, migration, and troubleshooting. Postgres preferred but other relational databases (MySQL, * Specification and verification design. Can you state a requirement precisely enough that it can't be misread, including the non-functional parts, and then design how to prove that it works? * Systems judgment. You know what breaks at scale, what it costs, and what fails; you assume every network call will fail and every model will misbehave. * Ruthless prioritization. What's in, what's out, and what isn't worth doing at all, which it usually isn't. Going along with whatever the LLM suggests leads to bloated projects we can't afford. It also means recognizing when the lesson from a piece of work is worth more as a permanent check than the next three tickets. * Product sense. You can tell whether something is right for a customer without being told. ## Description Your job is to know the business and the systems well enough to spot when an agent has produced the wrong thing, to keep its work inside the given scope, and to improve the process so that class of error can't recur. That takes more design judgment, review discipline, and product knowledge than a conventional senior role, not less. It's the wrong job if you want to spend your days writing code by hand., * The LoopFor any piece of work, with LLM and human review as appropriate at each step: * Think it through interactively: options, trade-offs, what could go wrong, and how it links to what's coming. * Write the specification: acceptance criteria, an explicit out-of-scope list, telemetry, and the non-functional requirements: latency, query behaviour, memory, and cost. * Implement: including an acceptance script that checks the criteria are met, inclusive of emitting telemetry and omitting out-of-scope work. * Ship and observe: run the acceptance script, fix what's needed, and watch production for defects. * Learn: what guardrails were hit, what cost time, and queue the work that turns the lesson into a permanent check. * Ramp and What Success Looks LikeYou'll start on small improvements and bug fixes to build familiarity with the business, the technology, and the process, growing into feature-level work. * Mastery shows up as owning larger features, authoring specifications rather than receiving them, and improving the tooling and harness. * Signs of success after three months: * You write specifications that get built without multiple rounds of review and without serious technical or product design flaws. * You can review what a coding agent has produced, find problems, and suggest fixes without asking other team members. * You are constantly improving our development tools as a byproduct of your work. * We don't feel like we need a daily standup.