Agent
Jobs
Applied
Tracker
Profile
    1. Jobs for you
    2. Job

    Job · 13741576

    BENGALURU · FULLTIME

    Senior Backend Software Engineer

    Care Adhd logo

    Care Adhd

    Bengaluru · hybrid · Posted 57d ago

    Sourced fromNaukri
    Undisclosed6–9 yrsfulltimeBengaluru

    About a minute. You'll make an account on the way through.

    agent · working

    • Read this posting0.6s
    • Found the form on Naukri · 13 questions to answer1.7s
    • Decided the answers for all of them2.2s
    • Tailor your résumé to this role
    • Waiting for you

    Section · 01

    About this role

    Senior Software Engineer
    API / Backend / Architecture
    Location: Bangalore, India
    About CareADHD
    CareADHD is a UK-based company providing ADHD diagnosis and treatment services. Our digital
    platform including a patient portal, clinician-facing applications, and AI-driven tools is how
    patients access care and how clinicians deliver it. When the platform works well, people get
    diagnosed and treated faster. When it doesn't, they wait. That's the context everything we build sits
    within.
    We are growing the engineering team in Bangalore and looking for a senior engineer who can own
    significant pieces of the platform end-to-end: understand the problem, design the approach, build it,
    ship it and support it in production.
    What you will actually be doing
    Most of your time around 60% will be producing production code: some of that is writing it
    directly, and some is writing the detailed context, instructions, and guidance that AI coding agents
    need to write it well. Both require the same engineering judgement. The remaining 40% will be split
    between contributing to technical designs, communications, mentoring, and ceremonies such as
    stand-ups, planning, and grooming.
    Building and maintaining backend services on AWS Lambda functions, API Gateway
    endpoints, SQS-based event processing, all defined and deployed through CDK
    Working with PostgreSQL (Aurora Serverless V2) writing performant queries, designing
    schemas, managing migrations, and understanding why your query plan just changed
    Contributing to our Next.js and React applications when the work calls for it this is primarily a
    backend-heavy role, but a small team and the boundaries rigid
    Working with AI coding agents as part of your daily workflow we use these extensively with
    custom guidelines and tooling, and we are actively building our own agents to support the team.
    Contributing to that effort is encouraged.
    Designing and reviewing technical approaches for new features and integrations, particularly
    around our AI-driven capabilities using AWS Bedrock
    Investigating and resolving production issues understanding monitoring and alerting, reading
    logs, tracing problems through distributed systems, and fixing root causes rather than symptoms
    Reviewing pull requests with a focus on correctness, clarity, and consistency not style
    nitpicking, but genuine quality
    Working with the UK-based technical leadership to translate requirements into well-designed,
    well-built solutions
    What we are looking for


    These are genuine requirements, not a wish list. If you don't recognise yourself in the first section,
    this probably isn't the right fit.
    Required:
    Strong hands-on experience building production systems on AWS specifically serverless
    architectures using Lambda, API Gateway, SQS, and CDK for infrastructure-as-code. We are not
    looking for I deployed an EC2 instance once. You should be comfortable designing
    event-driven systems and understand the trade-offs of serverless at scale.
    Solid PostgreSQL skills schema design, query optimisation, indexing strategy, and
    managing data in production. Experience with Aurora Serverless is ideal, but deep relational
    database knowledge is the real requirement.
    A production mindset. You care about error handling, edge cases, monitoring, and operability
    not just shipping features. You've been on-call, or at least you have built systems knowing that
    someone would be. A bug in production should bother you.
    Evidence of individual ownership. Youve personally scoped, built, shipped, and supported
    something meaningful not just contributed to a team effort. You can point to specific decisions
    you made and explained why.
    Clear, structured communication. This is a distributed team across time zones.




    Sourced from naukri

    Section · 02

    Skills

    PostgresqlHealthcare Domainamazon web servicesNode.JsMySQLAPIAlgorithmsMicroservices

    Senior Backend Software Engineer · waiting for your command