9x Dev jobs
3 Jobs Found
<h3>About the Role</h3><p>9x Dev is seeking a <strong>Senior Backend Engineer</strong> to join its team in Saudi Arabia. This full-time role involves designing and implementing backend architectures for client engagements, often navigating complex constraints such as regulatory requirements, existing data systems, or operational limitations. The position requires 5-10 years of experience.</p><h3>Key Responsibilities</h3><ul><li>Own the backend architecture for client engagements, including schema design, service boundaries, and integration strategies.</li><li>Engage with client architects to discuss and define technical solutions.</li><li>Define data models and service edges, documenting reasoning for clarity and future reference.</li><li>Develop critical components where correctness is paramount and establish patterns for other system parts.</li><li>Plan and execute migrations from legacy systems, ensuring continuous operation during transitions.</li><li>Establish operational baselines, covering observability, backups, and incident response protocols.</li><li>Review designs and code, ensuring adherence to best practices and pushing back on unnecessary complexity.</li></ul><h3>Required Experience and Traits</h3><ul><li>5-10 years of experience in backend engineering.</li><li>Ability to remain calm and meticulous during incidents.</li><li>A long-term perspective in building solutions, focusing on sustainability beyond initial delivery.</li><li>A natural inclination to explain reasoning and mentor colleagues through code reviews and discussions.</li></ul><h3>Preferred Qualifications</h3><ul><li>Experience with regulated industries such as finance or healthcare.</li><li>Prior work on multi-tenant products requiring stringent data isolation.</li><li>Familiarity with event sourcing or CQRS, coupled with the judgment to apply these patterns appropriately.</li></ul><h3>Work Environment and Culture</h3><p>This role supports remote work across the MENA region, with flexible hours structured around team collaboration. The company emphasizes shipping products quickly, often within weeks, and operates with small teams of four to eight individuals who manage products from initial client contact to handover. Engineers have direct client contact from day one. A budget is provided for personal setup, tools, and licenses, along with a learning budget and dedicated time for professional development. The company promotes a culture where time off is encouraged and taken, with a focus on engagement outcomes rather than time tracking.</p>
<h3>About the Role</h3><p>9x Dev is seeking a <strong>Senior Frontend Engineer</strong> to lead the frontend development for client products. This full-time position in Saudi Arabia involves designing and implementing complex B2B interfaces, such as trading screens and freight boards, where precision and reliability are critical. The role requires 5-10 years of experience.</p><h3>Key Responsibilities</h3><ul><li>Define the frontend architecture, component library, and coding standards for client products, primarily using TypeScript, React, and *****</li><li>Develop challenging components such as virtualized tables, live charts, and complex forms, establishing patterns for team implementation.</li><li>Implement practices to enhance code quality, including daily reviews, robust typing, and effective testing.</li><li>Engage directly with clients, participating in demos, explaining technical trade-offs, and adapting solutions based on feedback.</li><li>Ensure proper project handover through comprehensive documentation and walkthroughs, enabling client teams to manage independently.</li></ul><h3>Required Skills and Experience</h3><ul><li>Proven experience in frontend architecture and development, with a focus on TypeScript, React, and *****</li><li>Ability to work autonomously and take ownership of project outcomes.</li><li>Strong collaborative skills, with a focus on mentoring and improving team capabilities.</li><li>Effective communication skills to articulate problems and propose solutions clearly.</li></ul><h3>Preferred Qualifications</h3><ul><li>Experience with real-time data technologies such as websockets and streaming updates.</li><li>Prior experience in building and maintaining design systems across multiple products.</li><li>Background in domains where accuracy is critical, such as finance, logistics, or healthcare.</li></ul><h3>Work Environment and Culture</h3><p>This role offers remote work across the MENA region, with flexible hours structured around team collaboration. Projects typically ship within weeks, allowing engineers to see the impact of their work quickly. Teams are small, consisting of four to eight individuals who manage a product from initial client engagement through to handover. The company provides a budget for equipment, tools, and professional development, including dedicated time for learning. Engineers engage directly with clients from the project's inception, participating in key decision-making processes. The company emphasizes results over time tracking, offering flexible time off.</p>
<p><strong>About the role</strong></p><p>Our clients tend to arrive holding a hard constraint: a regulator, a ledger that must balance, a dispatch board that can't blink during a shift, or twenty years of data in a system everyone is afraid of. You'd design around those, then prove it works.</p><p>You own the backend architecture of an engagement: schema, service boundaries, integration strategy, and the operational story that comes with them. You also own the conversation with the client's architects, who will arrive with opinions and sometimes with a diagram.</p><p>Engagements run six to eighteen months, which is long enough for shortcuts to find their way back to you.</p><p>Agents draft, refactor and explain code all day here. That makes your judgment worth more, not less: what to trust, what to test, and which generated abstraction to delete before it spreads.</p><p><br></p><p><strong>What you'll do</strong></p><ul><li><strong>Draw the boundaries.</strong> Data model and service edges, written down with the reasoning, so the next person isn't left guessing.</li><li><strong>Build where correctness matters.</strong> You take the parts that must not be wrong, and set the patterns for everything else.</li><li><strong>Plan the escape from legacy.</strong> Migrations that keep both worlds running until the client is ready to switch.</li><li><strong>Set the operational baseline.</strong> Observability, backups, runbooks, and a clear answer to what happens at 3am.</li><li><strong>Hold the line on complexity.</strong> Review designs and code, and push back on the clever thing that won't pay for itself.</li></ul><p><br></p><p><strong>What we look for</strong></p><ul><li><strong>Five Years of Backend Depth:</strong> TypeScript, Go, Python or similar, in production, with the scars to match.</li><li><strong>Node and TypeScript Depth:</strong> framework choices you can defend, and comfort in the runtime when the behavior gets strange.</li><li><strong>Postgres Under Load:</strong> locking, pooling, partitioning, and a migration plan for the table nobody is allowed to take offline.</li><li><strong>API Design That Lasts:</strong> versioning, pagination, idempotency keys, and contracts that survive the second consumer.</li><li><strong>Event-Driven Where It Earns It:</strong> queues, outbox patterns, and exactly-once wishes met with at-least-once reality.</li><li><strong>Security and Audit Trails:</strong> authentication, authorization, secrets, personal data handling, and logs an auditor can follow.</li><li><strong>Observability Built In:</strong> structured logs, traces and metrics, so whoever is on call is reading rather than guessing.</li><li><strong>Schema Whisperer:</strong> design, query performance, transactions, and the failure modes of each at 2am.</li><li><strong>Production Owner:</strong> you have carried a pager, learned something unpleasant, and redesigned because of it.</li><li><strong>Boundary Defender:</strong> you integrate with systems you don't control and keep their surprises on their side of the wall.</li><li><strong>Straight About Trade-Offs:</strong> you can size work and say plainly what you're giving up to hit a date.</li><li><strong>Architect Translator:</strong> you explain a design to people who will never read the code, and they leave understanding it.</li><li><strong>Fluent English, Written and Spoken:</strong> most of our work happens in a written thread or on a call, and both have to be clear. Arabic is a genuine advantage across the region.</li><li><strong>AI With Judgment:</strong> agents make you faster, and you still spot the plausible nonsense they sometimes produce.</li></ul><p><br></p><p><strong>Personal traits</strong></p><ul><li><strong>Calm in incidents:</strong> you get slower and more careful when it matters, not faster and louder.</li><li><strong>Long-game thinker:</strong> you build for month nine, not demo day.</li><li><strong>Teacher by default:</strong> the review comment explains why, not just what.</li></ul><p><br></p><p><strong>Nice to have</strong></p><ul><li>Regulated work: finance, healthcare, or anything with an auditor attached.</li><li>Multi-tenant products where data isolation had to be airtight.</li><li>Event sourcing or CQRS, plus the judgment to know when they're overkill.</li></ul><p><br></p><p><strong>Why you'd like it here</strong></p><ul><li><strong>Remote across MENA.</strong> Work from wherever you are in the region, with hours built around your team's overlap rather than someone's attendance spreadsheet.</li><li><strong>Work that ships.</strong> Products go live in weeks, not quarters. When someone asks what you have been building, you can open it on your phone and show them.</li><li><strong>Small teams, no ticket queue.</strong> Four to eight people carry a product from the first client call to handover. Nobody hands you a spec and disappears.</li><li><strong>Kit and tools you choose.</strong> A budget for your setup, and for the editor, licenses and services that make you fast. No three-week procurement saga.</li><li><strong>A learning budget with time attached.</strong> Money for the course or the conference, plus room in the week to use it. The second half is the part most places skip.</li><li><strong>Client contact from day one.</strong> You sit in the room where the decisions get made. Plenty of engineers wait a decade for that seat.</li><li><strong>Time off people take, and no timesheets.</strong> We measure engagements, not humans in fifteen-minute increments. Book the holiday, go, come back.</li></ul>