Overview
Landela is an early-stage technology company building and operating digital products and services. We are hiring three Software Engineers to help turn product requirements and customer problems into reliable production software.
You will work with senior engineers and the wider team across frontend, backend, APIs, data, integrations, testing, and delivery. This is a hands-on product engineering role for someone who can take a reasonably scoped problem, understand what needs to be built, work through implementation decisions, and take responsibility for getting it into production.
Why this role matters
As Landela grows its products and customer base, we need more engineering capacity without creating a team that depends on senior engineers for every implementation decision.
These roles are important to building that capacity. You will own meaningful product work, contribute to the quality of the shared codebase, and gradually take responsibility for larger features and parts of the system as your judgement and familiarity with the products grow.
Responsibilities
- Build, test, and ship customer-facing and internal product features across frontend and backend systems.
- Take ownership of scoped features from understanding the requirement through implementation, code review, release, monitoring, and follow-up fixes or improvements.
- Build and maintain APIs, business logic, data models, database changes, and integrations with third-party services.
- Implement clear, responsive, and maintainable user interfaces using established product and engineering patterns.
- Write appropriate automated tests, review your own changes carefully, and participate constructively in code reviews.
- Investigate bugs and production issues, use logs and other available information to identify causes, and work with senior engineers when problems require deeper system knowledge.
- Contribute to technical discussions and raise implementation risks, unclear requirements, or maintainability concerns before they become larger problems.
- Work with product, operations, customer-facing colleagues, and other engineers to understand the real problem behind the work rather than treating requirements as isolated tickets.
- Improve code quality, documentation, developer workflows, and engineering practices when you identify practical opportunities to make the team more effective.
Requirements
Experience & qualifications
- At least 2 years of professional software engineering experience building applications used by real users or customers.
- Bachelor's degree in Computer Science, Software Engineering, Information Technology, Computer Engineering, or a closely related technical field.
- Good TypeScript or JavaScript experience, including practical experience building web applications with React or another modern frontend framework and working with backend APIs.
- Experience delivering complete features in a shared production codebase rather than only coursework, tutorials, or isolated coding exercises.
- Good understanding of relational databases, SQL, API development, automated testing, Git, and pull-request workflows.
- Able to debug problems systematically, read unfamiliar code, make sensible implementation decisions, and ask for input when a problem exceeds your current context or experience.
- Strong communication and follow-through, with the ability to work independently on reasonably defined problems and collaborate effectively with other engineers.
Nice to have
- Experience with Node.js, Next.js, PostgreSQL, AWS, or similar technologies used in modern web applications.
- Experience building third-party integrations, authentication, payments, fintech, travel, marketplace, or e-commerce products.
- Experience working in a startup or small product team where engineers participated in deployment and production support.
What success looks like
- You consistently take well-scoped product work from requirement to production with reliable follow-through.
- Your code is understandable, appropriately tested, and maintainable by other engineers.
- You identify blockers, unclear requirements, and technical risks early rather than allowing work to stall silently.
- You can investigate and resolve increasingly complex bugs and production issues with less assistance over time.
- You contribute useful feedback in code reviews and technical discussions rather than treating review as a one-way approval step.
- Your ownership grows from individual implementation tasks to complete features and well-defined parts of the product.
What this role is
- A hands-on product engineering role
- Broad exposure across frontend and backend systems
- Real responsibility for software that reaches production
- A role where technical ownership should increase as you demonstrate capability
How this role works
- You will usually receive a defined product problem or outcome, but not every implementation detail will be specified for you.
- Senior engineers will provide technical direction and support, but you are expected to investigate, propose solutions, and make progress independently.
- You may work across different parts of the stack depending on the product problem rather than being limited to frontend or backend tickets.
- You will participate in deployment and production support for the systems you help build, while deeper architecture and infrastructure ownership will generally sit with more senior engineers.
Working style
Landela operates with a small engineering team and minimal layers. Engineers are expected to communicate clearly, take responsibility for their work, review each other's code, document important decisions, and raise delivery or technical risks early.
This is a remote-first role anchored in Nairobi. Most engineering work can be done remotely, with occasional in-person team sessions or working meetings when useful. Strong asynchronous communication and reliable follow-through are important.
How to apply
Use the application form below and include your LinkedIn, GitHub, portfolio, or other relevant work where available. Briefly describe a production feature or project you personally built, what you were responsible for, one technical challenge you encountered, and how you solved it.
Go to application form