Backend Developer

Entangl is building the operating system for critical infrastructure, starting with data centers. We bring together drawings, asset data, technical documentation, procedures, telemetry, alarms, and operational knowledge so that teams can understand their facilities, identify problems, and operate them safely. We are looking for an exceptional Backend Engineer to build the systems that make this possible. This is not a role where you receive perfectly written tickets, implement isolated endpoints, and hand responsibility to someone else. You will work on difficult problems involving incomplete data, complex physical systems, customer-specific integrations, real-time information, and infrastructure where reliability matters. You will be expected to understand the underlying problem, design the right system, ship it, monitor it, and take responsibility for whether it works successfully for the customer. What You Will Build You may work on: Systems that ingest and structure engineering drawings, manuals, asset lists, procedures, and operational data.Data models representing electrical, mechanical, and controls infrastructure.Pipelines that extract, normalize, validate, and connect information from many different sources.APIs that power complex operational workflows.Real-time telemetry and alarm-processing systems.Systems that combine multiple abnormal conditions into clear, actionable issues.Integrations with building-management, electrical-power-monitoring, asset-management, and other customer systems.Search, retrieval, and AI systems grounded in customer documentation.Infrastructure for deploying Entangl across many customers and facilities.Permissioning, auditability, security, and multi-tenant data isolation.Internal tools that allow our engineers and operations teams to configure and validate customer sites quickly.Systems that support customer-specific requirements without fragmenting the core product. The challenge is not simply storing information. It is turning fragmented, inconsistent, and often incorrect data into a dependable operational system. What You Will OwnDesign and build production backend systems from initial concept through deployment.Take ownership of complete systems and customer outcomes, not just individual services.Develop clear, maintainable data models for complicated physical infrastructure.Build reliable ingestion and transformation pipelines for messy customer data.Make sound architectural decisions while avoiding unnecessary complexity.Investigate production issues deeply and resolve their underlying causes.Build monitoring, testing, observability, and failure recovery into the systems you own.Work directly with frontend, AI, controls, product, and operations teams.Speak with customers and domain experts when necessary to understand the real problem.Identify scaling, reliability, and data-quality risks before they become emergencies.Improve the speed and safety with which Entangl can onboard new facilities.Raise the engineering standard across the company.Leave every system better understood, more reliable, and easier to extend. What Success Looks Like You will not be measured by lines of code, story points, or the number of services you create. You will be measured by: Whether the systems you build work reliably in real customer environments.Whether customer data becomes more accurate, connected, and useful.Whether failures are detected before customers report them.Whether problems are resolved permanently rather than repeatedly patched.Whether new customers and facilities can be deployed faster.Whether the architecture remains understandable as the product grows.Whether other engineers can safely build on top of your work.Whether you make good decisions under ambiguity.Whether customers trust the information Entangl provides.Whether you take responsibility for the complete outcome. A system is not finished because it has been deployed. It is finished when it works reliably, handles failure intelligently, and delivers lasting value to the customer. Who You AreYou have an unusually strong sense of ownership.You are relentlessly resourceful.You can take an ambiguous problem and turn it into a working production system.You care deeply about correctness, reliability, and maintainability.You are willing to understand the domain rather than treating it as someone else’s responsibility.You investigate problems until you understand the actual cause.You do not hide behind incomplete specifications.You can distinguish between necessary engineering and unnecessary abstraction.You move quickly without being careless.You test realistic failure cases, not only the happy path.You are comfortable making decisions with incomplete information.You communicate clearly about risks, trade-offs, and uncertainty.You take responsibility when something you built fails.You care about commercial and customer outcomes, not only technical elegance.You are comfortable operating in a demanding environment with high standards. Technical Strengths You should have strong experience with several of the following: Designing and operating production backend systems.Python, TypeScript, Go, Java, Rust, or another modern backend language.Relational databases and disciplined schema design.Background jobs, queues, event-driven systems, and asynchronous processing.Cloud infrastructure and production deployments.Monitoring, logging, tracing, and incident investigation.Automated testing and production-quality validation.Security, authentication, authorization, and data isolation.Performance optimization and scaling.Working with large, inconsistent, or rapidly changing datasets. Experience with telemetry, time-series data, graph structures, industrial systems, building controls, digital twins, electrical infrastructure, document intelligence, or AI systems is valuable but not required. We care more about evidence of exceptional engineering judgment than familiarity with a specific stack. The Problems Are MessyThe data we receive from customers is rarely clean. Names may not match across systems. Drawings may be outdated. Manuals may be missing. Assets may be duplicated. Telemetry points may be incorrectly mapped. Different manufacturers may expose different information for equipment that appears similar. You should be comfortable building systems that: Make uncertainty visible rather than hiding it.Preserve traceability back to original sources.Detect conflicts and missing information.Allow data to improve over time.Fail safely when inputs are incomplete or incorrect.Separate customer-specific configuration from core product logic.Remain understandable even as complexity grows. We do not want systems that appear impressive in a demo but become fragile under real operational conditions. Engineering Judgment Great backend engineering at Entangl requires more than writing code. You should regularly ask: What does the customer need to trust this output?What happens when the input is incomplete, delayed, duplicated, or wrong?How will we debug this six months from now?Can we trace this result back to its source?Does this design make the next customer easier or harder to deploy?Are we solving the actual problem or merely moving complexity elsewhere?What are the consequences if this system fails silently?Is this abstraction genuinely useful?Can another engineer understand and safely modify this system?Is this ready for production, or does it only work in a controlled demonstration? You should be able to balance urgency, technical quality, customer needs, and long-term maintainability. You May Be a Strong Fit IfYou have built a backend system from an early stage and operated it in production.You have worked with messy or incomplete real-world data.You have owned systems where reliability and correctness were critical.You have diagnosed difficult production problems that others could not explain.You have designed systems that became easier to extend as usage increased.You have simplified an unnecessarily complicated architecture.You have worked closely with customers or domain experts.You have identified major risks before they caused visible failures.You have built internal tools that materially increased a team’s speed.Former teammates would describe you as fast, rigorous, dependable, and unusually resourceful. This Role Is Not for You IfYou only want to work from detailed tickets.You consider your responsibility complete when your code is merged.You avoid production ownership.You are unwilling to speak with users or understand the domain.You respond to recurring problems with repeated patches.You add complexity to make systems appear more sophisticated.You prefer rewriting systems over understanding why the existing system fails.You ignore data-quality issues because they are not strictly backend problems.You wait for someone else to identify what should be improved.You optimize for technical purity while ignoring customer value.You are satisfied with systems that work most of the time.You blame unclear requirements instead of helping create clarity. How We WorkWe are ambitious, direct, and highly accountable. Engineers at Entangl are expected to understand the customer, protect the company’s reputation, care about commercial outcomes, and take responsibility for the full result. We expect engineers to think independently and challenge decisions when they believe there is a better approach. Once a decision has been made, we expect full commitment and disciplined execution. We value speed, but not recklessness. We value strong architecture, but not unnecessary complexity. We value ownership, but not silent heroics that leave systems undocumented and dependent on one person. The goal is not to become indispensable because nobody else understands your work. The goal is to build systems and raise standards that make the entire company stronger.