The Software Engineer role at Cogent Infotech is a pivotal position focused on delivering robust technical solutions across a variety of client engagements. As a member of our engineering team, you will be responsible for translating complex business requirements into scalable code, maintaining high-quality software standards, and participating in the full software development lifecycle. This role is critical to our mission of providing high-impact consulting services. You will work within diverse environments, often requiring you to adapt quickly to different tech stacks and project methodologies. Success in this role requires not only a strong grasp of core programming principles but also the agility to learn new frameworks and the professional maturity to collaborate effectively with both internal teams and external client stakeholders. ##### Tip Candidates should be aware that Cogent Infotech operates as a consulting and training-integrated firm. You may be expected to undergo a training period before being placed with clients, and flexibility regarding project assignment and potential relocation is often a component of the role.
Initial Screening
reportedPhone or video call with a recruiter or hiring manager to discuss your background and interest in the position.
What to demonstrate
- Phone or video call with a recruiter or hiring manager to discuss your background and interest in the position
- Depth in Java
How to prepare
- Be able to walk your CV end to end in two minutes, and say why this company specifically.
- Have your salary expectations, notice period and location constraints ready, and ask for the rest of the loop in writing.
Technical Assessment
reportedTechnical interview that may include live coding challenges, multiple-choice questions on core Java, and discussions about past project experiences.
What to demonstrate
- Technical interview that may include live coding challenges, multiple-choice questions on core Java, and discussions about past project experiences
- Depth in Java
How to prepare
- Answer aloud and timed: How do final classes, methods, and variables behave?
- Answer aloud and timed: What is the difference between overloading and overriding?
PracHub editorial advice for the preparation topics above.
Review your resume
Be prepared to explain every project you have listed in detail.
Communication is key
If you don't know an answer, explain your thought process. Interviewers often value how you approach a problem more than the final answer.
Prepare questions
Always have 2–3 thoughtful questions about our team culture, the training process, or the types of projects we support.
Be prompt
Arrive for your scheduled interviews exactly on time or a few minutes early to demonstrate reliability.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
Can you describe the purpose of a finally block in exception handling?
Can you describe the purpose of a finally block in exception handling?
Approach
- Say what the runtime actually does before reasoning about the code.
- Name what is shared across threads and what owns each piece of state.
- Identify the window where an invariant is briefly untrue.
- Distinguish a value from a reference to it, and say which one you handed out.
Follow-up
- What happens if two callers reach this at the same time?
- Where could this allocate more than you expect?
How do you approach writing code to solve simple algorithmic problems?
How do you approach writing code to solve simple algorithmic problems?
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
Track a rolling failure rate per destination for circuit decisions
The egress service delivers about 1,500 webhooks per second across roughly 40,000 destinations, each call bounded by a 10 second timeout. Maintain, per destination, the failure rate over the trailing 60 seconds so a caller can ask before dispatch whether the circuit should open. Attempts arrive as (destination_id, finished_at_ms, outcome). Requirement: amortised O(1) per attempt, with total memory bounded by the destination count rather than by traffic. Give the structure, its exact memory, and the rule that stops a destination with three attempts from opening a circuit.
Approach
- Name the exact-deque version and then reject it as the default. Holding timestamps and advancing a tail pointer past anything older than now minus 60 seconds is a correct two-pointer window at amortised O(1) per attempt, but its memory tracks in-window traffic, so one destination in a retry storm holds hundreds of thousands of entries while thousands of quiet destinations hold none.
- Use a ring of 60 one-second buckets per destination, each bucket a pair of counters for attempts and failures. On an attempt, advance the ring by the elapsed whole seconds, zeroing at most min(elapsed, 60) buckets, then increment the head. That is amortised O(1) with a fixed footprint per destination.
- State the footprint: 60 buckets times two 4-byte counters is 480 bytes of payload per destination, so 40,000 destinations is roughly 20 to 25 MB with per-entry overhead, bounded by the catalogue rather than by the rate. The cost is granularity, since the oldest bucket ages out in whole seconds, which is far tighter than the decision needs.
- Require a minimum sample before the circuit may open. A destination with three attempts and three failures reads as 100 percent and is not evidence; a floor of roughly 20 attempts in the window makes the ratio meaningful, and below that floor use a run of consecutive failures as the trigger instead.
Follow-up
- The fleet is 30 instances and each sees roughly a thirtieth of a destination's traffic. Where does the rate actually live, and what does a per-instance answer get wrong?
- A destination answers in 9.5 seconds and succeeds. It is not failing but it is consuming your per-destination concurrency. What signal should open the circuit here?
How do you construct basic SQL queries to retrieve or manipulate data?
How do you construct basic SQL queries to retrieve or manipulate data?
Approach
- Name the grain you start from and join outward from it.
- Check whether any join is one-to-many before aggregating, or the sums inflate.
- Say which index the query would use, and what makes it unusable.
- Handle the rows that do not match: that is usually the actual question.
Follow-up
- How does the query change if that join becomes one-to-many?
- What happens to this when the table is ten times larger?
Stop tag and share joins from fanning out a page
resource_tag is (resource_id, tag_id) with PK (resource_id, tag_id); resource_share is (resource_id, shared_with_user_id, permission). The tagged-and-shared listing inner-joins resource to both, filters tenant_id, tag_id = ANY($2) and shared_with_user_id = $3, orders by updated_at DESC and takes 50. Pages come back with fewer than 50 distinct resources and the total in the header is far too high. Explain the row multiplication, rewrite both the page query and the count query so each is correct, and name the index each one needs. PostgreSQL 16.
Approach
- Do the arithmetic against the predicates that are actually there. An inner join emits one row per matching child row, and both joins are filtered: tag_id = ANY($2) admits only the requested tags, shared_with_user_id = $3 admits one user's share rows. So a resource holding three of the requested tags and shared with $3 once yields three rows, not one — the multiplier is its count of matching tags times its share rows for that single user, and that second factor is 1 unless the table admits duplicate (resource_id, shared_with_user_id) pairs. LIMIT 50 then limits rows rather than resources, and COUNT(*) counts pairs — the header is the product, not the population.
- Reject DISTINCT as the fix. It deduplicates after the product has been built, so the planner must materialise and sort the fanned-out set before the LIMIT can apply, and it leaves any SUM or AVG in the same select list wrong.
- Rewrite both filters as semi-joins, keeping resource as the only row source: AND EXISTS (SELECT 1 FROM resource_tag rt WHERE rt.resource_id = r.resource_id AND rt.tag_id = ANY($2)) and the same shape against resource_share. A semi-join stops at the first match per resource and preserves the driving index order, so ORDER BY updated_at DESC, resource_id DESC LIMIT 50 still stops after 50 rows.
- Count with the same predicates and no join at all: SELECT count(*) FROM resource r WHERE r.tenant_id = $1 AND r.status = 'active' AND EXISTS (...) AND EXISTS (...). Nothing multiplies a resource, so the number is the population.
Follow-up
- The filter changes from 'any of these tags' to 'all of these tags'. Rewrite it and state what it costs relative to the ANY form.
- A resource can be shared with the same user twice under different permissions. Does your count change, and should it?
What are the primary principles of Object-Oriented Programming (encapsulation, inheritance, polymorphism, and
What are the primary principles of Object-Oriented Programming (encapsulation, inheritance, polymorphism, and abstraction)?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
Can you explain the difference between a List and a Set in Java?
Can you explain the difference between a List and a Set in Java?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
How do final classes, methods, and variables behave?
How do final classes, methods, and variables behave?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
What is the difference between overloading and overriding?
What is the difference between overloading and overriding?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
Can you explain the difference between i++ and ++i?
Can you explain the difference between i++ and ++i?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
What are the core differences between various access specifiers?
What are the core differences between various access specifiers?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
What is the role of dependency injection and how does it improve software architecture?
What is the role of dependency injection and how does it improve software architecture?
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- State the consistency you need, and where you are willing to be stale.
Follow-up
- What breaks first when traffic grows ten times?
- How does this behave when that dependency is down for an hour?
One log partition stops advancing while the others drain
Search results for a subset of tenants are hours stale; the rest are current. The projection consumer reports lag of zero on 15 of 16 partitions and 400,000 on one. Its error rate is flat and its CPU is idle. outbox_event has no pending rows older than a second, so the relay has published everything it holds. Identify the mechanism, give the ordered checks, and state what you do in the first ten minutes versus what you change permanently.
Approach
- Read the lag distribution first. A slow consumer lags everywhere; zero on fifteen partitions and 400,000 on one is not throughput. Idle CPU on the stuck partition means the consumer is not advancing its offset at all, which points at one message it cannot get past rather than at a rate problem.
- Exonerate the producer before touching the consumer. No pending outbox rows older than a second means the relay published, so the event exists in the log. This separates never sent from sent and never applied, which are different code paths and usually different owners.
- Read the message at the stuck offset and the handler's log lines for its event_id. A flat error rate with no progress has two explanations and you must distinguish them: the handler is throwing and the retry loop is swallowing it, or the handler is blocking on something and never returning. Idle CPU with no error lines favours the second.
- Mitigate before diagnosing further. Move the offending event to a dead-letter store and commit the offset past it. Adding consumers does nothing here, because a partition is consumed by exactly one member of the group, and the blast radius is every aggregate hashed to that partition, not only the aggregate that produced the bad event.
Follow-up
- The dead-lettered event carried aggregate_version 7 and the projection had applied 6. What must the replay do differently if 8 and 9 landed in the meantime?
- How do you show staleness to the user while the partition is behind, given the API already returns the projection's watermark?
Built from the rounds and topics Cogent Infotech candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the Cogent Infotech loop
- Write out the reported sequence: Initial Screening, Technical Assessment.
- For each round, write one sentence on what it is judging, from the description above, and mark the one you are least ready for.
Deliverable: A one-page map of the 2 reported rounds, with the weakest marked.
02Work Java
- Spend the session on Java, which Cogent Infotech candidates report being tested on.
- Write one worked example in Java and time yourself on it.
Deliverable: One timed worked example in Java.
03Work Object-Oriented Programming (OOP)
- Spend the session on Object-Oriented Programming (OOP), which Cogent Infotech candidates report being tested on.
- Write one worked example in Object-Oriented Programming (OOP) and time yourself on it.
Deliverable: One timed worked example in Object-Oriented Programming (OOP).
04Work Core Java Fundamentals
- Spend the session on Core Java Fundamentals, which Cogent Infotech candidates report being tested on.
- Write one worked example in Core Java Fundamentals and time yourself on it.
Deliverable: One timed worked example in Core Java Fundamentals.
05Answer out loud: Core Java & Object-Oriented Programming (OOP)
- Answer aloud, timed: What are the primary principles of Object-Oriented Programming (encapsulation, inheritance, polymorphism, and abstraction)?
- Answer aloud, timed: Can you explain the difference between a List and a Set in Java?
Deliverable: Spoken answers to 2 reported Core Java & Object-Oriented Programming (OOP) question(s), under time.
06Answer out loud: Technical Fundamentals & Database
- Answer aloud, timed: How do you construct basic SQL queries to retrieve or manipulate data?
- Answer aloud, timed: Can you explain the difference between i++ and ++i?
Deliverable: Spoken answers to 2 reported Technical Fundamentals & Database question(s), under time.
07Answer out loud: Behavioral & Professional Background
- Answer aloud, timed: Can you describe a significant project from your academic or professional background?
- Answer aloud, timed: How do you handle working in a team versus working independently?
Deliverable: Spoken answers to 2 reported Behavioral & Professional Background question(s), under time.
Expand any day for tasks and deliverables. Your progress is saved on this device.
Behavioural rounds judge the decision you made and what it cost.
Can you describe a significant project from your academic or professional background?
Can you describe a significant project from your academic or professional background?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
How do you handle working in a team versus working independently?
How do you handle working in a team versus working independently?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
What is your process for learning new technologies or frameworks?
What is your process for learning new technologies or frameworks?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
How do you manage your time when facing tight project deadlines?
How do you manage your time when facing tight project deadlines?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
- 01
Can you describe a significant project from your academic or professional background?
- 02
How do you handle working in a team versus working independently?
- 03
What is your process for learning new technologies or frameworks?
- 04
How do you manage your time when facing tight project deadlines?
How long should I prepare for the technical interview?
A week of focused review on Core Java and common coding challenges is generally sufficient. Focus on mastering the basics rather than memorizing complex algorithms.
Cogent Infotech Software Engineer candidate reports ↗Is there a specific dress code or professional standard?
While the interviews are often remote, you should maintain a professional demeanor and appearance, as you are interviewing for a client-facing consulting role.
Cogent Infotech Software Engineer candidate reports ↗What if I am not familiar with a specific technology mentioned in the interview?
Be honest about your experience level. We value the ability to learn and the willingness to undergo our training programs to fill knowledge gaps.
Cogent Infotech Software Engineer candidate reports ↗What is the typical timeline for an offer?
Decisions are often made quickly, sometimes within a few days of your final technical interview.
Cogent Infotech Software Engineer candidate reports ↗What topics does Cogent Infotech test in interviews?
Cogent Infotech interviews most often cover Java, Sales Strategy, Object-Oriented Programming (OOP), Core Java Fundamentals, and Account Executive Role Competencies. The exact emphasis depends on the specific role you apply for.
Cogent Infotech Software Engineer candidate reports ↗Sources & methodology 3 sources ↗
No official company page is cited. Rounds and questions come from candidate reports and PracHub editorial material; each source shows the date it was read.
- 01Cogent Infotech Software Engineer candidate reports ↗
Company-reported rounds, questions and FAQ.
Candidate reports · Accessed 2026-09-22 - 02PracHub Software Engineer practice ↗
PracHub practice material, not company-reported.
PracHub page · Accessed 2026-09-22 - 03PracHub preparation framework ↗
PracHub preparation guidance.
PracHub page · Accessed 2026-09-22
Explore related engineering environments and compare the preparation focus.
Confluent Software Engineer Interview Guide
Concurrency exercises for Confluent candidates: check-then-act races, deadlock from inconsistent lock ordering, and why two individually atomic operations do not compose into an atomic update.
GitHub Software Engineer Interview Questions & Guide 2026
Testing exercises for GitHub software engineer prep: choosing boundary cases over repetition, isolating tests from shared clock and ordering, and treating an intermittent failure as a defect rather than noise.
Zulily Software Engineer Interview Guide
What Zulily asks Software Engineer candidates, from reported rounds and questions.
Zoom Communications Software Engineer Interview Guide
What Zoom Communications asks Software Engineer candidates, from reported rounds and questions.