L #2729
Applications open
Full-Time Job
Software Developer - Confluent
IBM
About the role
Introduction
About The Team
The Connect UI team builds the experiences Confluent Cloud customers use to bring data into and out of Kafka. That covers browsing and setting up fully managed and custom connectors, troubleshooting connector failures with AI assistance, and visualizing how connectors are performing. Connectors are where customers' real-time data enters the platform, so the quality of what we build directly affects how quickly customers get up and running
About The Role
We are looking for a Frontend Software Engineer who's excited to help build engaging, intuitive products for managing and visualizing large-scale, real-time data streams. Data flow is central to how companies operate, and we aim to make that experience simple and attractive. Working with mentorship from senior engineers, you will help develop features across the Connect experience in Confluent Cloud and steadily grow into an owner of parts of the product.
- Our Cloud UI is built with React and TypeScript on our own design system, and connects to multiple REST and GraphQL APIs.
- We test with Jest and React Testing Library (unit) and Playwright (end-to-end).
- We deploy to production daily and can test every commit, including PRs, before it goes live. Feature flags let us release independently of backend teams, and bots keep our dependencies up to date.
- AI-assisted development tools are part of our everyday engineering workflow.
Your Role And Responsibilities
As a Frontend Software Engineer, you will help build client-side features for data-intensive products, working closely with senior engineers, designers and product managers.
You Will
- Help develop new features from user requirements and designs, taking on well-defined tasks within larger features, delivering them on time, refining them based on feedback, and growing the scope you own over time.
- Build UI components and interactions to the design specifications using our design system, and integrate with backend APIs, working with backend engineers to understand API contracts and handle loading, error and empty states well.
- Write clean, readable code with unit and end-to-end tests, and write short design notes for your tasks for peer review.
- Take part in code reviews, both receiving and giving feedback.
- Help investigate and fix bugs and production issues, starting by shadowing the on-call rotation.
- Share your progress clearly in standups and project updates, and raise blockers early.
- Learn Confluent's engineering practices, including release, monitoring and feature flag processes, and how our product works end to end.
Preferred Education
Master's Degree
Required Technical And Professional Expertise
- Experience with 0.6 –1 year of professional experience and a strong foundation in data structures, algorithms and problem-solving
- Strong JavaScript fundamentals, including asynchronous programming (promises, async/await), closures and the DOM, plus solid HTML and CSS skills, including responsive layouts
- A good understanding of React (components, props, state, hooks, and how components re-render) and a basic understanding of frontend architecture: structuring components, managing state, and separating data fetching from UI
- Experience building and bundling a frontend project with Webpack or a similar tool such as Vite, including an understanding of modules, loaders and code splitting
- Comfort debugging with browser developer tools, and familiarity with Git and a pull-request-based workflow
- Curiosity, eagerness to learn and openness to feedback, with good communication and collaboration skills and a team-first mindset
Preferred Technical And Professional Experience
- Awareness of web accessibility and web performance (for example, bundle size and Core Web Vitals)
- Experience with data visualization or charting libraries
- Exposure to AI-powered workflows, agentic AI or LLM-based applications
- Internships, open-source contributions, hackathons or personal projects you've built and shipped
- Interest in data streaming, Kafka or distributed systems (no prior experience needed)
Eligibility & process
Who can apply
Seniority: Mid-Senior level. Employment type: Full-time
Skills & stack
Selection process
Details are shared by the recruiter after shortlisting.
Prep kit
19 resourcesStudy material 4
Aptitude Practice Questions & Mock Tests
Curated logical, quantitative, and verbal reasoning problems for the initial online screening round.
Company-Specific Interview Preparation Corner
Detailed interview experiences, exam formats, and previous test questions for IBM and tech roles.
Technical Placement Question Bank
High-yield coding cheat sheets, core CS fundamentals (OOP, DBMS, OS, Networks), and rapid revision guides.
Algorithm, DSA & Live Code Debugger Practice
Hands-on problem sets to improve coding speed and step-by-step memory debugging.
Company-specific guides 4
APTITUDE & LOGIC
Aptitude Practice Questions & Online Mock Tests
Curated logical, quantitative, and verbal reasoning problems to sharpen reasoning skills required for the initial screening test.
COMPANY GUIDE
IBM Interview Preparation Corner
Comprehensive guide covering typical interview formats, common questions, and preparation tips for IBM and off-campus tech roles.
MOCK TESTS & PAPERS
Comprehensive Interview Prep Resources & Syllabus
Collection of previous year questions, company-specific test patterns, and interview experiences for technical and HR rounds.
CODING PRACTICE
Algorithm and Data Structure Problem Set
Practice problems to improve coding proficiency and algorithm problem-solving speed for technical rounds.
Likely coding questions 4
Round-wise strategy 4
Round 1: Online Assessment (OA)
Aptitude, Quantitative Logic & 2 Coding Problems
Focus on accuracy and speed. Practice arrays, strings, and standard arithmetic puzzles.
Round 2: Technical Interview 1
Core Tech Stack (JavaScript, TypeScript, React, HTML5, CSS3, REST APIs, GraphQL, Git) & Live Code Tracing
Explain your thought process aloud. Analyze time & space complexities before coding.
Round 3: System Design & Problem Solving
Database Schemas, APIs & Architecture Basics
Clarify edge cases, diagram schemas cleanly, and discuss scalability trade-offs.
Round 4: HR & Cultural Fit Discussion
IBM Core Values, Learning Agility & Offer Terms
Demonstrate passion, strong communication, and readiness for full-time collaboration.
Technical questions 4
What is the bias-variance tradeoff and how do you prevent overfitting? Answer
Model answer: High bias leads to underfitting (oversimplified model), high variance leads to overfitting (captures noise). Mitigate using L1/L2 Regularization, Dropout, Cross-Validation, and data augmentation.
Explain the difference between Precision, Recall, and F1-Score. Answer
Model answer: Precision = TP / (TP + FP) (correctness of positive predictions). Recall = TP / (TP + FN) (coverage of actual positives). F1-Score is the harmonic mean of Precision and Recall.
How does Gradient Descent work and what is the role of Learning Rate? Answer
Model answer: It optimizes loss functions by iteratively moving weights in the direction of negative gradient. A large learning rate may overshoot the minimum; a small rate causes slow convergence.
What is the difference between Supervised, Unsupervised, and Self-Supervised learning? Answer
Model answer: Supervised uses labeled data (X -> y). Unsupervised finds hidden patterns in unlabeled data (clustering/PCA). Self-supervised generates labels from input data (e.g. masked language modeling in BERT/Transformers).
Behavioural & HR questions 3
Why do you want to join IBM as a Software Developer - Confluent?
Highlight IBM's market reputation, recent tech innovations, and how your skills in JavaScript directly solve their team's objectives.
Highlight IBM's market reputation, recent tech innovations, and how your skills in JavaScript directly solve their team's objectives.
Describe a challenging bug or academic project roadblock and how you resolved it.
Use the STAR method: Situation (project context), Task (what needed solving), Action (specific tools/logic applied), Result (quantifiable positive outcome).
Use the STAR method: Situation (project context), Task (what needed solving), Action (specific tools/logic applied), Result (quantifiable positive outcome).
How do you handle strict deadlines or sudden scope changes?
Explain your prioritization strategy, proactive communication with mentors/peers, and agile mindset.
Explain your prioritization strategy, proactive communication with mentors/peers, and agile mindset.
Competitive Package
Bengaluru, India
Seniority: Mid-Senior level. Employment t…
