Personal details
Minea C.
Summary
My name is Constantin-Claudiu Minea and I am a dedicated software engineer looking to positively impact a specific product or industry that would be possible through my expertise put into practice. I have a passion for getting involved in a dynamic team, where the speed of development is equally important as efficiency and code quality.
For the past 4 years, out of 7 of experience in the field, I have been in a start-up environment, where a day is never like the one before, the ability to quickly adapt to the new scope is a must, and proactivity is not just encouraged, but highly required. This is where I feel most comfortable, as I desire technical challenges and I want to stay away from the cubical mindset where I only handle my own tech yard.
Work Experience
SeedOn is a blockchain-based (web3) solution whose focus is to tackle the web2 crowdfunding space, thus being able to conduct investment transactions through blockchain, in a transparent manner.
As part of SeedOn, we have developed two solutions: a crowdfunding platform, that allows entrepreneurs to raise funds for their start-ups with cryptocurrencies (https://invest.seedon.io) and a crypto-related solution with capabilities such as custodial wallet management, assets depositing and withdrawal, staking, vesting, swap operations, and fiat on-ramp (https://finance.seedon.io).
My responsibilities have varied from resource management, interviewing, mentoring, and keeping in touch with all team members via 1-on-1 meetings, to defining, refining, and planning the product backlog and future sprints. I have been actively involved in all development efforts in building the ecosystem, being the main decision-making person on everything related to the technical aspects of the backend architecture, while managing the whole team made of 14 software engineers.
When required, I have also taken care of the web3 smart contract developments that were deployed on the EVM infrastructure, with the latest smart contract being developed for a trading bot whose purpose was to maintain trading volume on a decentralized exchange.
A critical aspect of the application was the transaction processing mechanism that needed to be handled for 3k active platform users constantly managing their assets with swap operations, transfers & staking requests while guaranteeing at the same time financial transaction's correctness, atomicity, and consistency. At its peak, SeedOn finance managed assets worth $3m.
During my collaboration with Igentify, I have contributed to software solutions within their ecosystem to digitalize and streamline genomic workflows. Through this solution, genetic results for various analyses have been delivered automatically to patients, reducing the processing time, and thus becoming more efficient to sustain a higher patient flow. Through Igentify’s ecosystem, conventional genetics medicine procedures have increased by at least 10 times, therefore onboarding over 1000 patients at the moment of our collaboration.
Being part of Igentify’s development team, I have contributed to building software that offers a more effective way of providing genetic results to patients. During my development involvement, I have worked on various applications from the solution suite that the company is offering, which is a microservice-oriented architecture. The team was formed out of senior software engineers only, with high coding standards, and a lean & quick transition from onboarding to the productive phase.
The main responsibilities were to quickly deliver clean, flexible code, keep up with industry standards, and be highly adaptable to constant requirements changes due to re-prioritization. In Igentify, being a microservice-oriented architecture, developers had a primary and secondary microservice that they belonged to.
Belonging to a primary service, meant that developers were owners or co-owners of a specific service, thus tackling on their own the issues reported to their services, onboarding new team members, handling the knowledge transfer sessions, and being responsible for the features to be released and match the planned timeline.
Belonging to a secondary service it meant that only on demand, developers were required to assist and join forces to deliver a functionality on a specific service that might require more efforts either to match a deadline or due to the complexity of the implementation.