KASHII UPDATEZ Everyday Student Requirements & Python Coding Tutorials by Python Kashi
KashiiUpdatez
REQUIREMENT_ID_155 β€’ 3-DAY_ACTIVE_POLICY

Software Engineer - I

Company
Company H1
Type
Opportunity Type Full-Time Job
Salary
Stipend / Salary 5 LPA
Location
Location Remote
Posted Date
Posted Date Yesterday
TypeScript Python Node.js GraphQL Elasticsearch Docker Kubernetes AWS Big Data PySpark Airflow LLMs REST APIs performance optimisation testing
πŸ“–
Data Structures and Algorithms Practice Open Resource β†—
Essential for coding interviews and building efficient search pipelines.
πŸ“–
System Design Fundamentals Open Resource β†—
Prepares you for designing scalable search infrastructure and API services.
πŸ“–
Company‑Specific Interview Prep Open Resource β†—
Provides insights into H1’s interview style and typical questions.
πŸ“–
Coding Challenges Repository Open Resource β†—
Helps sharpen problem‑solving skills for technical rounds.

Bachelor’s degree in Computer Science, Information Technology, or related Engineering discipline; minimum 60% aggregate; no backlog; batch year 2025/2026/2027 (if applicable).

1
Round 1: Technical coding & system design
2
Round 2: Technical deep dive & coding
3
Round 3: HR
H1 is a pioneering health-tech startup that champions the belief that access to reliable healthcare information is a fundamental human right. By leveraging cutting‑edge data science and artificial intelligence, H1 builds a global platform that empowers doctors with real‑time, evidence‑based insights, thereby accelerating equitable drug development and improving patient outcomes worldwide. The company’s mission is to democratise medical knowledge, fostering trust in healthcare systems and ensuring that every medical professional, regardless of geography, can make informed decisions. The Software Engineer – I role sits within the Search Engineering team, a critical pillar that powers H1’s core search infrastructure. As a fresher, you will be immersed in a fast‑paced environment where you will ingest terabytes of medical data into Elasticsearch, design low‑latency APIs, and build end‑to‑end features using Node.js and GraphQL. Your work will directly impact the speed and relevance of search results that doctors rely on daily. Key responsibilities include: 1. Developing and maintaining data ingestion pipelines for large‑scale medical datasets. 2. Building high‑performance REST/GraphQL APIs that serve search queries with sub‑second latency. 3. Designing and implementing indexing strategies in Elasticsearch to optimize search relevance. 4. Collaborating with product managers and data engineers to translate business requirements into scalable technical solutions. 5. Writing unit and integration tests to ensure code quality and reliability. 6. Monitoring system performance, troubleshooting issues, and proposing optimisations. 7. Participating in code reviews and knowledge sharing sessions. 8. Keeping abreast of AI and search technology trends and evaluating their applicability. 9. Contributing to documentation and best‑practice guidelines. 10. Mentoring junior teammates and fostering a culture of continuous learning. Tech stack: TypeScript, Python, Node.js, GraphQL, Elasticsearch, Docker, Kubernetes, AWS, PySpark, Airflow, LLMs. Growth path: Freshers start as Software Engineer – I, then progress to Software Engineer – II, Senior Engineer, Lead Engineer, and eventually Technical Lead or Architect, with opportunities to specialise in AI/ML or data engineering. Why join H1? You will work on mission‑driven technology that directly improves global health outcomes, collaborate with a diverse, high‑performing team, and enjoy a flexible remote work model, generous benefits, and a culture that values innovation, learning, and impact.

H1 β€” QA & Automation Testing Interview Guide

Previously asked questions, exam syllabus, coding benchmarks & round strategy.

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.

Open Resource β†—
COMPANY GUIDE 🎯
H1 Interview Preparation Corner

Comprehensive guide covering typical interview formats, common questions, and preparation tips for H1 and off-campus tech roles.

Open Resource β†—
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.

Open Resource β†—
CODING PRACTICE πŸ’»
Algorithm and Data Structure Problem Set

Practice problems to improve coding proficiency and algorithm problem-solving speed for technical rounds.

Open Resource β†—
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 (TypeScript, Python, Node.js, GraphQL, Elasticsearch, Docker, Kubernetes, AWS, Big Data, PySpark, Airflow, LLMs, REST APIs, performance optimisation, testing) & 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
H1 Core Values, Learning Agility & Offer Terms
Demonstrate passion, strong communication, and readiness for full-time collaboration.
What is the difference between Implicit Wait, Explicit Wait, and Fluent Wait in Selenium? Answer β–Ό
Model Answer: Implicit Wait sets a global timeout for all element lookups. Explicit Wait pauses execution until a specific ExpectedCondition (e.g. elementToBeClickable) is met. Fluent Wait allows defining polling frequency and ignoring specific exceptions like NoSuchElementException.
Explain the Page Object Model (POM) and its advantages in Test Automation. Answer β–Ό
Model Answer: POM is a design pattern that creates an object repository for web UI elements. It separates test scripts from page locators, reducing code duplication and making maintenance easy when UI elements change.
How do you handle dynamic WebElements whose ID changes on page reload? Answer β–Ό
Model Answer: Use dynamic XPath methods like contains(), starts-with(), text(), or XPath axes (ancestor, following-sibling, parent) instead of brittle absolute paths.
What is the difference between @BeforeMethod and @BeforeClass in TestNG? Answer β–Ό
Model Answer: @BeforeClass runs once before the first test method in the current class, while @BeforeMethod executes before each individual test method.
How do you validate REST API response codes and JSON payload using Postman / RestAssured? Answer β–Ό
Model Answer: In RestAssured: given().when().get('/endpoint').then().assertThat().statusCode(200).body('status', equalTo('ACTIVE')).
Why do you want to join H1 as a Software Engineer - I?
Preparation Tip: Highlight H1's market reputation, recent tech innovations, and how your skills in TypeScript directly solve their team's objectives.
Describe a challenging bug or academic project roadblock and how you resolved it.
Preparation Tip: 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?
Preparation Tip: Explain your prioritization strategy, proactive communication with mentors/peers, and agile mindset.

More Fresh Requirements in Software Engineering

View Category Feed β†—
H1
Software Engineer - I
Apply Apply Now β†—
Chat Chat with Kashii