We're reimagining mortgages through blockchain - tokenizing real estate debt to make mortgage investing more transparent, accessible, and liquid. Early-stage, profitable, and moving fast.
THE ROLE:
Build smart contracts in Solidity that power mortgage tokenization, develop Python services/APIs connecting blockchain to the real world, and own features end-to-end. You'll wear multiple hats - one minute writing a Solidity payment contract, next debugging a Python API, then optimizing Celery tasks. Small team = big impact.
LOOKING FOR:
- 10+ years building products with serious Solidity + Python chops
- Experience developing EVM-compatible smart contracts
- Expert with Django, DRF, Celery
- Strong distributed systems & async programming experience
- Deep understanding of blockchain fundamentals, DeFi, token standards (ERC-20, ERC-721, ERC-1155)
- Bonus: financial services, mortgages, or asset-backed tokens
WHY JOIN:
- Own big pieces of the stack from day one
- Competitive pay + meaningful equity
- Shape the future of real estate finance
- Small, passionate team
LOCATION: Miami, FL - onsite required (South Florida candidates welcome)
Apply: talent@liquidfi.io with resume + note about your Solidity/Python experience
I got the error that this email talent@liquidfi.io doesn't exist.
"We're writing to let you know that the group you tried to contact (talent) may not exist, or you may not have permission to post messages to the group. A few more details on why you weren't able to post..."
It leaves close to no room for prioritization because the prioritization is predefined via the policy. We've had bugs on edge cases - the odds of an end user hitting them was very small (but not zero). Either the product owner (or whatever you want to call them) gets to prioritize the backlog, or its someone else - in this case it sounds like the engineering team.
In the world we have more than just bugs. We also have features, and refactoring and whatnot. Prioritization should be done across all tasks, so a bug could be "medium" but the team might not even work on bugs this week unless they are a show stopper.
Isn't this policy overruling the judgement of the team/product lead and focuses too much "only" on the bugs?
Really good article. We had been debating moving from a monolith to services in a distributed environment a while back, and I recommended real baby steps - lets not do full blown services but first break up some of the components so everything isn't deployed together. Guess what? Zombie tasks - albeit not that many, but tracking them down is a bear.
We're reimagining mortgages through blockchain - tokenizing real estate debt to make mortgage investing more transparent, accessible, and liquid. Early-stage, profitable, and moving fast.
THE ROLE: Build smart contracts in Solidity that power mortgage tokenization, develop Python services/APIs connecting blockchain to the real world, and own features end-to-end. You'll wear multiple hats - one minute writing a Solidity payment contract, next debugging a Python API, then optimizing Celery tasks. Small team = big impact.
STACK: - Smart contracts: Solidity, OpenZeppelin, Hardhat/Foundry - Backend: Python (Django, DRF), Celery, RabbitMQ, PostgreSQL - Infrastructure: AWS, Docker, EVM-compatible chains - Integrations: Web3.py
LOOKING FOR: - 10+ years building products with serious Solidity + Python chops - Experience developing EVM-compatible smart contracts - Expert with Django, DRF, Celery - Strong distributed systems & async programming experience - Deep understanding of blockchain fundamentals, DeFi, token standards (ERC-20, ERC-721, ERC-1155) - Bonus: financial services, mortgages, or asset-backed tokens
WHY JOIN: - Own big pieces of the stack from day one - Competitive pay + meaningful equity - Shape the future of real estate finance - Small, passionate team
LOCATION: Miami, FL - onsite required (South Florida candidates welcome)
Apply: talent@liquidfi.io with resume + note about your Solidity/Python experience