Job Description
What You’ll Own
- You’ll lead a team of 5–10 backend engineers, with scope to grow. This isn’t a reporting role — you’ll be deeply involved in technical direction, hiring, and making the team measurably better every quarter.
- Team leadership: Run a tight, high-trust engineering squad. Set the bar for code quality, system reliability, and engineering culture. Make your team better at their craft, not just faster at shipping.
- Technical direction: Own architecture decisions across your domain — APIs, service design, data flows, and third-party integrations. Hands-on enough to review designs and challenge tradeoffs, not just sign off on them.
- Hiring and growth: Scale the team deliberately. Own the full hiring funnel for your squad — sourcing, bar-raising, onboarding. Develop senior engineers into tech leads.
- Reliability and observability: Drive SLA discipline. Own uptime, on-call health, incident response quality, and RCA process for your domain. We care about this a lot — it’s part of our engineering culture, not an afterthought.
- Cross-functional collaboration: Partner with Product, Risk, Compliance, and external partners. Translate business constraints (and there are real ones in fintech) into clean technical solutions.
- Process and velocity: We’re adding structure without losing startup speed. Help us build the right amount of process—enough to ship reliably, not so much that we slow down. Since we don’t have a dedicated QA team, you and the team are responsible for shipping quality changes to production, and regression suites will play a critical role in ensuring stability.
- AI-first SDLC culture: Leverage AI to transform our software development lifecycle, building an AI-first engineering culture that boosts team productivity, innovation, and code quality.
The Real Challenge
This isn’t a simple CRUD product domain. You’re dealing with:
- Multi-vendor orchestration: The same user journeys run across multiple external partners with different APIs, SLAs, and failure modes. Keeping this reliable and debuggable is genuinely hard.
- Regulated complexity: Compliance-mandated flows, deduplication, and third-party verification checks aren’t optional. Your systems need to be both correct and auditable under regulatory scrutiny.
- Stateful, complex workflows: Core flows involve many states, retry logic, and idempotency requirements. Making these resilient and testable — while the product team wants to add new flows — is an ongoing engineering challenge.
Are you interested in this position?
Apply by clicking on the “Apply Now” button below!
#GraphicDesignJobsOnline
#WebDesignRemoteJobs
#FreelanceGraphicDesigner
#WorkFromHomeDesignJobs
#OnlineWebDesignWork
#RemoteDesignOpportunities
#HireGraphicDesigners
#DigitalDesignCareers
# Dynamicbrand guru