<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Software-Engineering on Essays | HungCQ</title>
    <link>https://blog.zenoa.space/tags/software-engineering/</link>
    <description>Recent content in Software-Engineering on Essays | HungCQ</description>
    <generator>Hugo -- 0.147.3</generator>
    <language>en</language>
    <lastBuildDate>Mon, 03 Mar 2025 21:35:00 +0700</lastBuildDate>
    <atom:link href="https://blog.zenoa.space/tags/software-engineering/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Platform or product engineering?</title>
      <link>https://blog.zenoa.space/posts/platform-or-product-engineering/</link>
      <pubDate>Mon, 03 Mar 2025 21:35:00 +0700</pubDate>
      <guid>https://blog.zenoa.space/posts/platform-or-product-engineering/</guid>
      <description>&lt;p&gt;Recently, I interviewed with a self-advertised &amp;ldquo;top&amp;rdquo; company,
with the initial assumption that they were a decent engineering organization.
However, the actual technical interview they conducted proved me totally wrong.&lt;/p&gt;
&lt;p&gt;The interview lasted around 55 minutes,
with around 25 minutes of product discussion and Q&amp;amp;A with a manager whose English was incomprehensible.
But let&amp;rsquo;s just consider that part unfortunate and unimportant,
and focus instead on the actual 30-minute technical discussion,
which I think was insightful in terms of software engineering and product development in general.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Software Engineering: Technical or Organizational?</title>
      <link>https://blog.zenoa.space/posts/software-engineering-technical-or-organizational/</link>
      <pubDate>Sat, 15 Jul 2023 15:05:00 +0700</pubDate>
      <guid>https://blog.zenoa.space/posts/software-engineering-technical-or-organizational/</guid>
      <description>&lt;p&gt;Recently I interviewed with a &amp;ldquo;top&amp;rdquo; Internet company in Vietnam. Top, in terms of salary offered, at least.
But the interview content and process, in my opinion, are by no way at the top.
I wonder how their recruitment and HR departments,
which are willing to spend a good deal of money for headhunting services and salary offering,
put so little thought into preparing the interview content and process.
I can summarize the interview of such single-minded organizations in a single word: technical.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
