Lead Software Developer

Lead Software Developer - ALNC

Valsoft Corporation · Beirut, Lebanon (Hybrid) · Full-time · Posted 2026-11-05

Workplace: hybrid

Department: Research & Development

Description

Aspire Software is looking for a Lead Software Developer to join our team in Lebanon.

Here is a little window into our company: Aspire Software operates and manages wholly owned software companies, providing mission-critical solutions across multiple verticals. By implementing industry best practices, Aspire delivers a time sensitive integration process, and the operation of a decentralized model has allowed it to become a hub for creating rapid growth by reinvesting in its portfolio.

The opportunity

We are rebuilding a proven government software product from the ground up as an AI-native, agentic platform, and we need the technical leader who will own it end to end.

We already have what most GovTech startups spend years chasing: paying government customers, deep domain knowledge, and a product that agencies rely on every day. What we don't have yet is a platform built for how software will work for the next decade. Government has been underserved by technology for a long time. Caseworkers, administrators and the public they serve still fight slow, form-driven systems built in another era. We think agents that can read, reason, act and hand off to humans can change that, and we want to be the ones who prove it.

You won't be maintaining legacy code. You will design the new platform, ship it to real customers, and then build the team that carries it forward. We're backed by an established software group, so you get startup ownership with the stability and runway of an established operator.

About the Job:

You are the Software Engineering Lead and the first technical hire on the new platform: architect, lead builder, and eventually manager of a small team. This role changes shape over time. In the first phase you are hands-on, writing a large share of the code yourself with a few contractors or partners alongside you. Once the platform is live with customers, you move into leading a small product engineering team of roughly [3–6] people, while staying close to the code and the architecture.

You report directly to the General Manager of the business and work closely with the people who know our customers best. You own:

• Architecture: the technical vision and design of an AI-native, agentic platform built on current-generation models, tooling and infrastructure.
• Delivery: shipping the rebuilt product to existing government customers and migrating them off the legacy system without disruption.
• Trust and compliance: security, privacy, accessibility and audit requirements that government buyers demand, designed in from day one.
• Team: hiring, setting the engineering culture, and growing the people who join after you.
• Build vs. buy: deciding where to use frontier models, open-source tools and partners, and where we need to own the stack.

Your first 6 months

• By month 4, customers start moving onto the new platform. By month 6, the migration is well under way and you are leading the team that runs it.
• Months 0–2: Build. Spend the first weeks with customers and the current product, then build the core platform: data layer, agent orchestration, evaluation and guardrails, key integrations and the security baseline. End month 2 with a working product running real workflows.
• Months 2–4: Refine with customers. Put the platform in front of design-partner customers, watch how frontline users work with it, and ship improvements weekly. Bring reliability, security and compliance up to production standard.
• Month 4 onward: Migrate and scale. Move existing customers onto the new platform in planned waves, without disrupting their operations. Put in place monitoring, incident response and release discipline. Hire and onboard the core team, and set the 12–24 month roadmap.

What success looks like: customers do the same work in a fraction of the time, adoption grows without being pushed, and the platform passes the security and procurement reviews government buyers require.

Requirements

You are a builder first, with the ambition to rewrite how an entire industry works and the discipline to ship it.

• You've built, shipped and scaled real products. What you've shipped matters more than years of experience: at least one product you built and scaled with real customers, as a founder, founding engineer, engineering lead or CTO, ideally with some time leading other engineers.

• You're fluent in the new way of building. AI coding agents, rapid prototyping and model-driven tooling are how you work every day, so a small team ships what used to take a large one. You've also shipped LLM-powered features in production: agents and tool use, retrieval, evaluation, guardrails, and managing cost and latency. You know where models fail and how to design around it.

• You're strong across the stack. Comfortable owning backend, data, cloud infrastructure and enough frontend to ship. You pick modern tools on merit, not habit.
• You take security seriously. You understand authentication, data protection, audit logging and least-privilege design, and you see compliance as a product feature rather than a blocker.
• You move fast without breaking trust. You ship weekly, but you know the difference between a prototype and software an agency depends on.
• You want to lead. You're ready to hire, mentor and set the culture of a small team, even if you haven't managed one before.
• You think like an operator and communicate clearly. You tie technical choices to budget, customer outcomes and revenue. You can explain a technical trade-off to a government director, a customer's IT team, or our leadership in plain language.

Nice to have

• None of these are required; any of them will help you move faster.
• Experience building for or inside government (for example an agency IT or CIO role), healthcare, insurance or other regulated buyers.
• Familiarity with public-sector security frameworks such as [SOC 2, FedRAMP, GovRAMP (formerly StateRAMP), or Canadian equivalents].
• A track record of migrating customers from a legacy system to a new platform.
• Time in a multi-business software group or serial acquirer, reusing platforms and practices across companies.
• Experience leading engineering across regions and time zones.
• Open-source contributions, published work, or side projects in AI agents.
• [French / bilingual English–French, if relevant to customers or location].

What we offer

• Real ownership. A blank-page platform build with existing customers waiting for it, and the authority to make the big technical calls.
• Meaningful upside. Competitive base salary of [salary range] plus [equity / long-term incentive / profit share].
• Stability with startup speed. The runway and customer base of an established company, without the bureaucracy.
• Impact you can see. Your work changes how public services are delivered to real people.

Apply

Apply at Valsoft Corporation

---

Powered by Workable