Tech Lead — Platform Engineering

Tech Lead — Platform Engineering

Location: Hyderabad (Work from Office) | Type: Full-time, 5 days a week | Experience: 8–10 years

About Bluecopa

At Bluecopa, we are building a finance operations platform for high-growth companies. We help finance teams automate their work, analyse their data, and make decisions faster.

We are a small, product-focused team working on hard data and platform problems. If you like building backend systems that stay reliable at scale and leading a team that ships well, we would like to talk to you.

About the Role

As Tech Lead for Platform Engineering, you will lead the team that builds and runs the backend services and workflows at the core of Bluecopa's platform. This is a hands-on role: you will write code, review designs, make the architecture calls for your area, and guide a team of backend engineers working across Java and Python.

Your success will be measured on three things: how reliably your team's services run in production, how predictably the team delivers against product goals, and how quickly recurring customer needs turn into platform capabilities instead of one-off fixes.

What You Will Do

Platform Architecture and Development

• Own the technical design and architecture for your team's services and modules, and make sure they hold up as the platform grows.
• Design, build, and maintain scalable backend services using Java (Spring Boot) and Python (Flask, Pandas, PyArrow).
• Build reliable, long-running workflows using Temporal and Argo Workflows, so that multi-step jobs finish correctly, recover from failures, and can be traced when something goes wrong.
• Set clear standards for code quality, testing, and documentation, and hold the team to them through design and code reviews.
• Troubleshoot and fix complex production issues across distributed services, and drive them to root cause rather than patching symptoms.
• Work with the SRE and DevOps teams on releases and deployments, making sure your team's services are release-ready, well-instrumented, and easy to operate.
• Keep CI/CD and engineering hygiene strong within the team, so shipping stays fast and safe.

Team Leadership

• Lead, mentor, and grow a team of backend engineers through one-on-ones, direct feedback, code reviews, and pairing.
• Break product goals down into clear, well-sequenced technical workstreams, and assign work based on team strengths, growth goals, and delivery priorities.
• Make timely technical and prioritization decisions, including when the information is incomplete, and explain your reasoning clearly.
• Own the trade-offs between speed, scope, and long-term maintainability, and make sure the team understands why a call was made.
• Unblock the team: resolve dependencies, escalate early, and remove friction before it slows delivery.
• Build a culture of ownership, collaboration, and accountability, and reduce ramp-up time for new engineers through documentation and pairing.

Working Across Teams

• Partner with product managers to shape scope, estimate effort, and set timelines the team can actually meet.
• Turn product requirements into technical specifications the team can execute against without guesswork.
• Work directly with the customer implementation team to understand deployment-specific needs, and turn recurring requests into platform capabilities rather than repeated one-off work.
• Investigate issues raised by implementation teams and fix them at the root, so the same problem does not come back.
• Keep the team aligned on common product goals and aware of how their work connects to them.
• Work with SRE, DevOps, QA, and UI teams to deliver features end to end.
• Communicate progress, risks, and technical constraints to stakeholders at the right level of detail, and represent your team in roadmap and architecture discussions.

What We Are Looking For

Required Qualifications

• Bachelor's degree in Computer Science, Information Technology, or a related field.
• 8–10 years of software development experience, including experience leading or mentoring engineers.
• Strong hands-on skills in either Java or Python, with working proficiency in the other.
• Production experience with Spring Boot (if Java is primary) or Flask (if Python is primary).
• Hands-on experience with Pandas and PyArrow for data processing.
• Hands-on experience with a workflow orchestration engine such as Temporal or Argo Workflows.
• Working knowledge of Kubernetes — enough to design services that deploy cleanly and to work well with SRE.
• Strong grasp of microservices architecture and RESTful API design, along with a good understanding of the web technology stack.
• Familiarity with Docker, Git, and sensible branching strategies.
• Track record of making sound technical decisions and defending them with clear reasoning.
• History of delivering complex projects with a team — systems you can point to that shipped and ran well.

Nice to Have

• Experience with Ibis for portable dataframe expressions across backends.
• Experience with OpenTelemetry for distributed tracing and metrics.
• Working knowledge of a major cloud platform (AWS, GCP, or Azure).
• Experience with both SQL and NoSQL databases.
• Familiarity with agile methods and running agile ceremonies.
• Experience working with customer-facing or implementation teams.
• Experience hiring and interviewing engineers.
• Time spent in a SaaS or product engineering environment.

What Success Looks Like

• In 90 days: You know the platform's services and their weak points, you have set up a regular design-review cadence, and you have shipped or unblocked at least one significant piece of work with the team.
• In 6 months: The team delivers against a clear, well-sequenced plan, production issues are traced to root cause instead of patched, and recurring implementation-team requests are turning into platform capabilities.
• In 12 months: Your area of the platform runs reliably with few surprises, the team works to standards you have set, and engineers you have grown make good decisions without needing you in every one.