wagey.ggwagey.ggv1.0-68eec7a-3-May
Browse Tech JobsCompaniesFeaturesPricingFAQs
Log InGet Started Free
Jobs/Staff Engineer Role/OakNorth - Lead Engineer
OakNorth

OakNorth - Lead Engineer

Bengaluru or Gurugram+ Equity1mo ago
In OfficeStaffAPACStaff EngineerSupport EngineerPostgreSQLMySQLReactTypeScriptpytest

Upload My Resume

Drop here or click to browse Ā· Tap to choose Ā· PDF, DOCX, DOC, RTF, TXT

Apply in One Click
Apply in One Click

Requirements

• We expect you to work in these ways, as well as encouraging and enabling these practices from others: • Collaborate šŸ’¬ - We work in cross-functional, mission driven, autonomous squads that gel over time. We pair program to work better through shared experience and knowledge. • Focus on outcomes over outputs āœ… - Solving a problem for users that translates to business results is our goal. Measurements focused on that goal help us to understand if we are succeeding. • Practice continuous improvement šŸ’” - We optimise for feedback now, rather than presume what might be needed in the future and introduce complexity before it will be used. This means we learn faster. We share learnings in blame-free formats, so that we do not repeat things that have failed, but still have confidence to innovate. • Seek to understand our users šŸ‘‚ - We constantly seek understanding from data and conversations to better serve our users' needs, taking an active part in research to hear from them directly and regularly. • Embrace and enable continuous deployment šŸ¤– - Seamless delivery of changes into an environment - without manual intervention - is essential for us to ensure that we are highly productive; consider resiliency; and practice security by design. • Test outside-in, test first 🚦 - TDD keeps us confident in moving fast, and deploying regularly. We want to solve user problems, and so we test with that mindset - writing scenarios first, then considering our solution; coupling tests to behaviour, rather than implementation. • We embrace differences and know that when we can be ourselves at work, we are happier, more motivated, and creative. We want to be able to bring our whole selves to work, have our own perspectives and know that we belong. As such, through your behaviours at work, we expect you to reflect and actively sustain a healthy engineering environment that looks like this: • A wide range of voices heard to the benefit of all • Teams that are clearly happy, engaged, and laugh together • Perceivable safety to have an opinion or ask a question • No egos - people listen to and learn from others at all levels, with strong opinions held loosely

Responsibilities

• Partner closely with Product and Delivery to: • Shape roadmaps, Highlight risks early • Make sensible trade-offs between scope, risk, and timelines • Take ownership during incidents and tricky production problems, coordinating technical response and follow-ups, not just writing the fix • We're pragmatic about our technology choices. These are some of the things we use at the moment: • šŸ—„ļø PostgreSQL, BigQuery, MySQL • šŸŽØ TypeScript, React, styled-components • šŸ”§ Jest, React Testing Library, Cypress, pytest • šŸš€ ECS Fargate, Docker, Terraform, GitHub Actions

Benefits

• Equity. We want people to have a stake in the business so that all our interests are aligned. • Health Insurance for employee and dependents. • Wellbeing and social events • Support causes that matter to you – Volunteering time off

Get Started Free

No credit card. Takes 10 seconds.

PrivacyĀ·TermsĀ·Ā·ContactĀ·FAQĀ·Wagey on X