Careers at IKECOZ
Help build useful software and a company designed to grow responsibly.
IKECOZ is building products, engineering systems, and a strong foundation for future client work. As the company grows, opportunities may become available for people who value thoughtful technology, continuous learning, and practical problem-solving.
No publicly listed vacancies
IKECOZ is currently strengthening its products, operations, and company foundation. Verified opportunities will be published on this page when they become available. Submitting a professional enquiry does not guarantee a role, interview, or response timeline.
There is no open-role application grid on this page because no verified vacancies are currently published.
Environment IKECOZ aims to build
Why people may want to work with IKECOZ.
These describe intended working habits — not guaranteed employee benefits or current team programmes.
Why work with IKECOZ
Meaningful problems
Work should connect to a real user need, business challenge, technical problem, or product objective — not busywork invented for its own sake.
Practical product ownership
IKECOZ aims to involve people in clarifying problems, shaping solutions, and improving outcomes across planning, building, and review.
Clear communication
Decisions, limitations, progress, and next steps should be explained honestly so collaborators can work with shared context.
Continuous learning
Engineering work improves through testing, feedback, documentation, and reflection — including lessons from internal products and prototypes.
Responsible engineering
Accessibility, maintainability, privacy, and security-conscious practices are part of quality, not optional extras.
Long-term thinking
IKECOZ prefers systems and habits that can grow with the company rather than shortcuts that create avoidable debt.
Team growth
How IKECOZ intends to build its team.
Recruitment and collaboration principles for a company still establishing its foundation.
Principle 1
Hire when there is meaningful, sustainable work
Roles should exist because the company has real work to support — not to create the appearance of growth.
Principle 2
Define responsibilities clearly
Future role descriptions should explain the problem to solve, expected outcomes, and how success will be assessed.
Principle 3
Communicate the company stage honestly
IKECOZ is currently strengthening its product portfolio, engineering systems, company processes, and client-service foundation. The company documents internal products and prototypes honestly while preparing for broader client and product work.
Principle 4
Assess practical ability fairly
Evaluation should focus on relevant skills, communication, and evidence of work — without asking candidates to do substantial unpaid production labour.
Principle 5
Protect applicant information
Professional enquiries should be handled carefully. Identification documents and other sensitive records should not be requested through the public website form.
Principle 6
Agree terms before work begins
Compensation, responsibilities, confidentiality, and working arrangements should be written clearly before collaboration starts.
Future opportunities
Capability areas that may become relevant as IKECOZ grows.
These cards describe possible future needs. They are not vacancies, salary offers, or application openings.
Future capability areas
- Future capability area
Frontend Engineering
Interfaces, accessibility, interaction quality, and maintainable web frontends.
- Future capability area
Backend and API Development
Server applications, integrations, data modelling, and reliable API design.
- Future capability area
Mobile Application Development
Cross-platform and native-leaning mobile product foundations such as Flutter work.
- Future capability area
Product and UI/UX Design
User flows, interface clarity, product structure, and usable design systems.
- Future capability area
Quality Assurance and Testing
Manual and automated testing, regression checks, and release confidence.
- Future capability area
DevOps and Deployment
Delivery pipelines, environments, monitoring foundations, and operational reliability.
- Future capability area
Cybersecurity-Conscious Engineering
Secure defaults, careful handling of secrets, and privacy-aware product decisions.
- Future capability area
AI Integration
Practical AI API integrations, prototyping, evaluation, and responsible configuration.
- Future capability area
Technical Writing
Documentation, case studies, developer-facing explanations, and editorial quality.
- Future capability area
Sales and Business Development
Discovery conversations, partnership outreach, and clear commercial follow-up.
- Future capability area
Customer and Product Support
Helping users and clients resolve issues with clarity and documented outcomes.
- Future capability area
Project Coordination
Scheduling, communication, milestone tracking, and delivery coordination.
Ways to collaborate
Possible ways to work with IKECOZ.
Not every arrangement is available today. Availability depends on real needs, capacity, and written agreement.
Ways to work with IKECOZ
Employment
Not currently listed.
Future full-time or part-time roles when sustainable positions exist and responsibilities are clearly defined.
Contract work
Considered when a real project need exists.
Project-based collaboration with agreed scope, deliverables, payment terms, and confidentiality.
Internships or early-career opportunities
Not available as an open programme today.
Only when IKECOZ has supervision, structure, meaningful work, and resources to support participants responsibly.
Technical collaboration
Discuss through a professional enquiry.
Specialist contributions, product partnerships, or other technical collaboration where interests and capacity align.
Business partnerships
Use the Contact form for partnership discussions.
Conversations involving products, distribution, technology, operations, or related collaboration.
Working principles
Habits that guide IKECOZ engineering and collaboration.
Drawn from company values, product delivery, Case Studies, website quality checks, and Blog editorial standards.
Working principles
Purpose before complexity
Start with the user, problem, and intended outcome before expanding architecture or tooling.
Build in clear stages
Controlled milestones make progress reviewable — as reflected in Services, Case Studies, and website quality checks.
Communicate limitations early
Honest status labels, draft protection, and evidence-first writing are part of how IKECOZ presents work publicly.
Document important decisions
Case Studies, Blog editorial standards, and typed content systems exist to keep reasoning reusable.
Test before declaring completion
Typecheck, lint, tests, and production builds are part of the website delivery standard; similar discipline applies to product work.
Protect users and sensitive information
Secrets stay server-side, privacy notices stay accurate, and public forms must not request identity documents or credentials.
What IKECOZ may value
Candidate expectations for future roles.
Requirements will depend on the role. Formal degrees are not assumed to be mandatory for every future opportunity.
Candidate expectations
- Ability to explain technical or product decisions clearly
- Willingness to learn and improve from feedback
- Honest communication about skills, limits, and availability
- Attention to quality, accessibility, and maintainability
- Practical problem-solving with portfolio or project evidence where relevant
- Respect for users, collaborators, and confidentiality
- Security and privacy awareness appropriate to the work
- Reliability in communication and agreed commitments
Proposed process
A transparent recruitment path for when roles open.
This describes an intended future process. It is not currently operating as an active hiring pipeline.
Stage 1
Role publication
Approved vacancies would be published on this Careers page with clear responsibilities and application instructions.
Stage 2
Application review
IKECOZ would review submitted information against the role requirements and current capacity.
Stage 3
Introductory conversation
A short discussion to understand motivation, experience, communication style, and fit for the company stage.
Stage 4
Skills or portfolio discussion
Review of relevant work, decisions, and practical ability — without requiring identity documents through the public form.
Stage 5
Practical assessment where necessary
Any assessment should be proportionate. Candidates should not be asked to complete substantial unpaid production work or confidential client deliverables.
Stage 6
Final discussion
Clarify responsibilities, working arrangements, compensation, and next steps.
Stage 7
Written offer or contract
Terms should be written and agreed before work begins.
Stage 8
Onboarding
Access, expectations, communication habits, and support would be set according to the agreed engagement.
Equal opportunity and respect
IKECOZ intends to consider applicants based on role requirements, demonstrated ability, potential, conduct, and lawful business needs.
Discrimination, harassment, exploitation, and disrespectful treatment are inconsistent with the company’s values.
This statement is an operational draft. Formal employment-policy wording requires Nigerian employment-law review before it is treated as a finalized legal policy.
Professional enquiry
Express interest for future opportunities
You may send a professional enquiry describing your skills, portfolio or GitHub links, preferred collaboration type, and availability. Do not submit identification documents, medical details, bank information, or other highly sensitive records through the public form.
What to include
- Area of interest and preferred collaboration type
- Relevant experience summary
- Portfolio, GitHub, or website link if available
- General availability
Do not upload CVs through this website yet, and do not send passports, national IDs, bank details, or medical information.
Context
Work and writing that show how IKECOZ operates.
Useful background for people interested in the company’s engineering approach — not employee testimonials.
Related work and articles
PraySync
Cross-platform Flutter product foundation in active development.
Creatiq
AI-assisted creative prototype exploring Node.js integrations.
PraySync Case Study
Planning, debugging, and testing lessons from the product foundation.
Creatiq Case Study
Prototype setup, environment configuration, and delivery lessons.
Technologies
How IKECOZ approaches stacks, capabilities, and engineering choices.
About IKECOZ
Company stage, values, and long-term direction.
Related Blog articles
Blog
From Personal Portfolio to Software Company Website: The Architecture Behind IKECOZ
How IKECOZ moved from a personal portfolio model to a company-first Next.js website with typed content, evidence standards, and routes for services, products, case studies, and contact.
Blog
How IKECOZ Chooses a Technology Stack
A practical framework for selecting tools at IKECOZ: start with the problem, respect constraints, prefer the smallest reliable architecture, and revisit decisions as products evolve.
FAQ
Questions about careers at IKECOZ.
Honest answers about vacancies, internships, contractors, remote work, and professional enquiries.
Frequently asked questions
Interested in the future of IKECOZ?
Explore the company’s work, follow future updates, or send a professional enquiry describing your skills and area of interest.