You own your work.
We do not hand you tickets without context. You carry a problem from discovery through production signals—and you are trusted to say no when quality is at risk.
Careers
Build software that institutions depend on.
At 2Logics we believe software engineering is a craft. We build platforms that governments, banks, hospitals, manufacturers, and enterprises depend on every day. We are looking for people who care about quality long after launch.
Why engineers join
Why engineers choose 2Logics.
You write documentation.
Decision records, runbooks, and clear READMEs are part of the craft. Future you—and the next engineer—should not need archaeology.
You participate in architecture.
Architecture is not a closed room. Senior and mid-level engineers argue trade-offs, write ADRs, and defend maintainability in reviews.
You review code.
Reviews are mentoring, not gatekeeping theatre. We look for clarity, tests where they pay, and kindness with high standards.
You mentor others.
Growth is reciprocal. Teaching sharpens your own thinking; we make space for pairing, shadows, and deliberate feedback.
You ship thoughtfully.
Speed without operability is vanity. We prefer vertical slices that are monitored, accessible, and reversible.
You solve meaningful problems.
Our platforms serve governments, hospitals, banks, and enterprises. The work is hard because the stakes are real.
How we build software
Engineers participate at every stage.
Idea. Engineers help pressure-test whether the problem is real and measurable before we invent software.
Engineering principles
Not values posters—working agreements.
In practice
Architecture before implementation.
We refuse to start a government case system without identity, audit, and retention sketched as first-class concerns.
Current missions
Work organised around outcomes—not job titles alone.
Why it matters
Citizen services only work when identity, auditability, and peak load are treated as product requirements.
Who benefits
Challenges
Open on this mission: Senior Full-Stack Engineer
Open roles
Quality over quantity.
AI Engineer
Applied Intelligence · Lagos · Hybrid · Full-time
Ship grounded assistants and document intelligence with evaluation, guardrails, and human accountability.
Mission · Enterprise AI
Experience · 3+ years building production ML/LLM systems
Technology · Python · RAG · Evaluation · TypeScript
Success · Answers cite sources; refusals are deliberate; golden sets catch regressions before users do.
Cloud Engineer
Platform & Reliability · Lagos · Hybrid · Full-time
Build reproducible environments, safe release trains, and observability that transfers to client teams.
Mission · Cloud Modernisation
Experience · 4+ years cloud and delivery engineering
Technology · AWS · Azure · Docker · Terraform · Observability
Success · Environments are IaC-defined; cutovers are waved with rollback; dashboards answer the questions operators actually ask.
Product Designer
Design & Experience · Lagos · Hybrid · Full-time
Shape executive-grade and operator-grade experiences with rigorous systems thinking—accessibility as a launch gate.
Mission · Healthcare Platforms
Experience · 4+ years product design for complex systems
Technology · Figma · Design systems · Prototyping · WCAG
Success · Flows are clear under stress; components are reusable; accessibility findings are resolved before release; engineers receive crisp specs.
Senior Full-Stack Engineer
Platform Engineering · Lagos · Hybrid · Full-time
Own end-to-end delivery of enterprise web platforms—from domain modelling to operability—with a bias for clarity over cleverness.
Mission · Digital Government
Experience · 5+ years shipping production web platforms
Technology · TypeScript · Next.js · Node.js · PostgreSQL
Success · You ship vertical slices with tests, docs, and monitoring; architecture decisions are written down; teammates can extend your work without archaeology.
Life at 2Logics
Studio moments—not stock smiles.
Architecture sessions
Trade-offs on the board before code.
Pair programming
Two minds, one vertical slice.
Design reviews
Operators first, decoration never.
Whiteboard planning
Sketches beat slide decks.
Hack days
Space to try ideas without production risk.
Conference speaking
Share what we learn in public.
Knowledge sharing
Internal talks and written notes.
Community events
Mentorship beyond our walls.
Photography placeholders for real studio captures—replace via CMS media when available.
How we grow
Growth through ownership—not titles alone.
- 01
Joining
Onboarding with a real vertical slice—not a week of slides.
- 02
Mentorship
A named mentor and structured review feedback.
- 03
Ownership
A service or domain you can speak for in production.
- 04
Architecture Reviews
You present trade-offs and defend decisions in writing.
- 05
Leading Features
You coordinate design, QA, and release for a slice.
- 06
Leading Projects
You hold outcomes across a programme phase.
- 07
Technical Leadership
You raise the bar for others through standards and mentoring.
- 08
Principal Engineering
You set multi-year technical direction with humility and evidence.
Engineering toolkit
Tools we choose for reasons.
Frontend
Next.js / React
Typed UI with strong accessibility and performance budgets.
Design systems
Consistency for operators under stress.
Backend
Node / TypeScript
Shared language across the stack reduces handoff loss.
PostgreSQL
Transactional integrity for money, cases, and clinical state.
Cloud
AWS · Azure
Institutional hosting and identity preferences decide the cloud.
IaC
Environments must be reproducible and reviewable.
AI
RAG · evaluation
Grounded answers beat fluent improvisation.
Data
Pipelines · warehouses
Executive decisions need trusted, timely truth.
Security
Threat models · RBAC
Controls belong in design, not after launch.
Testing
Automated suites
Protect the paths that must never regress.
DevOps
CI/CD · containers
Safe, frequent release trains with rollback.
Monitoring
Metrics · traces · logs
Operability is part of the product.
Documentation
ADRs · runbooks
Systems must survive team change.
Hiring process
Transparent by design.
- 01
Application
CV, links, and a short note on work you are proud of. We read carefully; we do not farm volume.
- 02
Initial Conversation
A human conversation about craft, motivations, and how we work—no trick questions.
- 03
Technical Discussion
Architecture and trade-offs on systems like yours. We care how you think.
- 04
Practical Exercise
Only where appropriate—time-boxed, respectful of your evenings, reviewed with feedback.
- 05
Team Conversation
Meet people you would build with. Culture fit means shared standards, not sameness.
- 06
Offer
Clear scope, expectations, and growth path. Questions welcome.
Application
Apply with intent.
We read every application. Tell us about systems you are proud of—not only tools you have touched. Prefer email? Write to hello@2logics.ng.
Engineering community
Open Source
We contribute where it strengthens the platforms we run—and credit the commons we depend on.
Technical Writing
Insights is our public engineering notebook for architects and leaders.
Mentorship
Structured pairing and career conversations inside the studio.
University Talks
We speak with students about craft, not only tools.
Conferences
Occasional talks on architecture, accessibility, and delivery.
Research
Evaluation of AI and performance patterns before we recommend them to clients.
Internal Learning
Reading groups, postmortems, and deliberate practice.
Innovation Projects
Time-boxed experiments that must earn a path to production.
FAQ
Most roles are hybrid Lagos-based with flexibility for deep work. Fully remote is considered for exceptional fit and timezone alignment.
Come build software that still matters ten years from now.
We're not looking for people who simply write code. We're looking for engineers who care about systems, people, and the long-term success of every platform they build.