Q & A Flashcards

1
Q

Key factors in greenfield web architecture?

A

Modular design, scalable microservices, REST/GraphQL APIs, cloud-native infrastructure, CI/CD, and security-focused architecture.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Key factors in greenfield mobile architecture?

A

Platform-specific vs. cross-platform (React Native, Flutter), offline support, push notifications, API versioning, security protocols. Also CI/CD tools like Expo

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Approach to integrating legacy systems?

A

Use middleware for data transformation, ensure backward compatibility, API gateways, and phased rollout with thorough testing.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Best practices for API integration?

A

Versioning, idempotent operations, OAuth2/JWT for security, rate limiting, caching strategies, and monitoring for performance.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Steps for creating a hiring funnel?

A

Define roles, craft a skill matrix, set up an evaluation process (coding challenges, interviews), and implement a structured onboarding plan.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

How to onboard new developers effectively?

A

Assign mentors, provide clear documentation, set small initial goals, pair programming, and frequent check-ins for early feedback.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Strategies for developer mentorship?

A

Weekly 1:1s, career path development, providing challenging yet achievable tasks, and regular feedback on progress and code quality.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What’s crucial in talent development?

A

Encouraging continuous learning, promoting ownership of features, providing clear growth paths, and creating opportunities for leadership.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

How to pitch technical work to clients?

A

Focus on client pain points, propose phased MVP development, emphasize ROI, showcase relevant case studies, and offer flexible timelines.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Key strategies in client presentations?

A

Tailor language to the audience (technical vs. non-technical), demonstrate quick wins, provide visual aids (mockups, wireframes), and offer clear action plans.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Best way to foster team collaboration?

A

Regular cross-functional meetings, shared design/development tools (Figma, Zeplin), clear communication channels (Slack, Jira), and a culture of feedback.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Methods to align design and development?

A

Early developer involvement in design phases, consistent handoff processes, design tokens for common language, and quick iterative feedback loops.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Best practices for IoT architecture?

A

Focus on edge computing, efficient messaging (MQTT, CoAP), secure communication protocols, low latency, scalable device management, and robust firmware updates.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Key components of web3 architecture?

A

Decentralized storage (IPFS), smart contracts (Ethereum/Solidity), consensus mechanisms (PoW/PoS), security (encryption), and network scalability.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Managing a client project end-to-end?

A

Establish clear deliverables, frequent milestone reviews, use project management tools (Asana, Jira), handle scope carefully, and maintain open communication.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

How to handle scope creep in consultancy?

A

Set clear project boundaries, document changes in a project scope agreement, ensure client approval for additional work, and revise timelines accordingly.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

How to prioritize client work?

A

Understand client business goals, assess project impact and urgency, communicate delays or changes transparently, and balance competing priorities through agile planning.

18
Q

Ensuring quality in a consultancy environment?

A

Implement code reviews, follow industry best practices (TDD, BDD), maintain detailed documentation, and run regular retrospectives for process improvement.

19
Q

How to ensure seamless API integration across teams?

A

Clear API contracts, shared documentation, version control, standardized error handling, and regular syncs with involved teams for any breaking changes.

20
Q

What’s important for team retention and morale?

A

Clear career progression, regular recognition, flexible working conditions, transparent communication, and fostering a culture of learning and inclusivity.

21
Q

What is middleware for data transformation in microservices?

A

Middleware in microservices, often called message brokers (e.g., Kafka, RabbitMQ), handles the transformation, routing, and queuing of messages between services, ensuring data consistency and asynchronicity.

22
Q

What is an API gateway?

A

An API Gateway acts as a single entry point for external consumers of microservices. It handles request routing, authentication, rate limiting, caching, and load balancing. Examples include Kong, NGINX, and AWS API Gateway.

23
Q

Why use middleware in microservices?

A

Middleware decouples services, enabling better scalability, fault tolerance, and resilience. It ensures that microservices can communicate asynchronously, handle different data formats, and avoid direct service-to-service dependency.

24
Q

What is edge computing?

A

Edge computing processes data closer to the data source (e.g., IoT devices) instead of relying on a centralized cloud. This reduces latency, minimizes bandwidth use, and improves response times for real-time applications.

25
Q

What is MQTT in IoT?

A

MQTT (Message Queuing Telemetry Transport) is a lightweight publish/subscribe messaging protocol used in IoT for minimal bandwidth consumption, high scalability, and low-power consumption in constrained environments.

26
Q

What is CoAP in IoT?

A

(Constrained Application Protocol) is a specialized web transfer protocol designed for use with resource-constrained IoT devices, providing a simple way to interact with RESTful APIs in low-power networks.

27
Q

Why is low latency critical in IoT?

A

Low latency ensures real-time processing, which is essential for applications like smart cities, autonomous vehicles, or industrial automation. Delays can result in performance issues or safety risks.

28
Q

What does scalable device management involve?

A

Scalable device management involves handling millions of IoT devices with ease. It requires efficient onboarding, monitoring, software updates, and secure communication protocols to avoid bottlenecks and failure points.

29
Q

What makes a firmware update robust in IoT?

A

A robust firmware update system ensures secure, fail-safe updates with rollback capabilities, minimal downtime, and efficient distribution to avoid bricking devices or disrupting service.

30
Q

What is a project scope agreement?

A

A project scope agreement outlines the deliverables, timelines, responsibilities, and boundaries of a project. It serves as a mutual understanding between a client and service provider to prevent scope creep and ensure clarity.

31
Q

Key elements of a project scope agreement?

A

Include project objectives, deliverables, timeline, responsibilities of each party, acceptance criteria, budget, change management procedures, and terms for additional work.

32
Q

How to manage scope creep?

A

Clearly define the initial scope, create a formal process for scope changes, communicate the impact on budget and timeline, and get client approval before proceeding with any additional work.

33
Q

What is an API contract?

A

An API contract is a formal agreement that specifies how an API will behave, including endpoints, request/response formats, error codes, and security protocols. It acts as a “contract” between the API provider and consumers.

34
Q

What is the role of an API contract in seamless integration?

A

Clear API contracts ensure that all services and clients interact consistently with APIs, preventing breaking changes and enabling independent development by decoupling the consumer from the service provider.

35
Q

Why is versioning important in API contracts?

A

Versioning allows for changes and improvements to be made to an API without breaking existing clients. It supports backward compatibility, ensuring older integrations still work while new features are added.

36
Q

What tools ensure API contract enforcement?

A

Tools like Swagger/OpenAPI and Postman help document and validate API contracts, ensuring compliance and helping teams understand API behavior through automated testing and documentation.

37
Q

What is rate limiting in an API gateway?

A

Rate limiting controls the number of API requests a client can make in a given time period. It protects the API from abuse or overload, ensuring fair usage and preventing service degradation.

38
Q

How does an API gateway improve security?

A

API gateways manage centralized security for all services by enforcing authentication (OAuth, JWT), SSL/TLS encryption, request validation, and traffic filtering before it reaches internal services.

39
Q

What is request routing in an API gateway?

A

Request routing determines how incoming API requests are directed to specific backend services. It enables load balancing, traffic splitting (for A/B testing), and seamless scaling.

40
Q

Why use an API gateway for microservices?

A

An API gateway abstracts and simplifies the complexity of microservices by providing a unified interface for external clients, enabling centralized security, caching, monitoring, and fault tolerance.