the anti job boardactive 4mo ago
Daniel Adeniran

Daniel Adeniran

Backend Engineer @ Oneport365

Lagos, Nigeria2 yearsremote onlyready to start

Summary

Daniel Adeniran is an experienced backend engineer with a strong focus on designing and implementing reliable server-side systems. He has a proven track record in API development, database design, and integrating third-party services, leveraging AI tools to enhance development efficiency.

Looking for

Software EngineerBackend EngineerFull Stack Engineer

Skills

JavaScriptTypescriptPythonPhpGolangC#RustHTMLCSSReactNodeGinMuxFastAPISpring BootExpress jsTailwindBootstrapReact NativeFlutterRxJsBun.jsNextjsMySQLMongoDBPostgreSQLSQLAlchemySequelizePostmanCeleryPytestRabbitMQDockerGITGitHubAlembicAWSGCPDocusaurusMarkdownGraphQl

Preferences

Open to

Remote

#backendengineer#2years#softwaredevelopment#apidevelopment#databasedesign#cloudcomputing#fullstackdevelopment

The story

What Daniel is looking for

My ideal day-to-day is very backend-focused and problem-driven. I enjoy working on systems where I’m designing APIs, thinking through data models, and solving performance or scalability challenges. The kind of work that really makes me lose track of time is when I’m debugging or optimizing something non-trivial — like tracking down a bottleneck in a service, improving a slow database query, or designing a clean flow for handling asynchronous processes. I also enjoy integrating third-party systems and making sure everything works reliably end-to-end.

Why Daniel is exploring

my previous role ended due to restructuring, so I’ve been intentional about finding a role where I can contribute more meaningfully, especially on the backend, and continue growing in building scalable, production-grade systems.

What won't fit on a resume

One thing that doesn’t really fit cleanly on my resume is how deeply I got involved in building out Propay 365 at OnePort. It started as an internal tool to replace a very Excel-heavy financial workflow, but I found myself going beyond just implementing assigned tasks. I got particularly interested in how fragile some of the financial flows were — especially around data consistency and approvals. For example, during the Quotes validation process, I noticed inconsistencies in imported data that could silently affect downstream financial records. Nobody explicitly asked for it, but I dug into the import pipeline, identified the edge cases, and fixed the validation logic to ensure consistency across systems. I also led the backend development of the invoices module end-to-end. That involved designing the lifecycle states, enforcing invoice-to-PO validation rules, and integrating with QuickBooks so invoices could automatically become Bills for proper accounting reconciliation. Another area I explored was system reliability. I introduced Redis-backed queues and event-driven communication between services to decouple processes and make the system more resilient, especially for operations like notifications and cross-service updates.

The Anti Job Board

Skip the application black hole. Get warm intros to founders hiring now.

Create your profile